Structured pre-project diligence: Z-* custom inventory, BAdI/user-exit count, ECC module footprint, country e-invoicing flows, PI/PO integration estate, support-contract status, database platform, Fusion architecture preview.
The cost of getting scope and budget wrong on an ECC migration runs to seven figures and twelve months of slippage. The cost of a proper assessment is a fraction of a percent of project cost — and it's where the major decisions actually get made.
Sap ecc migration assessment is where the migration is won or lost — not because the build phases don't matter, but because every build-phase surprise is a known-unknown the assessment failed to surface. The Z-* custom estate that nobody catalogued. The BAdI implementations that drove a material slice of operational behaviour. The non-leading ledger that controllership forgot to mention. The PI/PO Integrated Configuration nobody owns. The country e-invoicing flow that has a regulatory deadline three weeks before cutover. Each of these is recoverable in assessment for hours of work; each costs weeks of programme delay if it surfaces during build.
Syntra ETL runs sap ecc migration assessment as a 3–5 week structured engagement. Week 1: read-only connection to ECC, discovery engine crawls the ABAP Dictionary, BAdI registry, user-exit catalog, custom-report repository, PI/PO ICO inventory, country e-invoicing flow catalog. Week 2: Z-* classification workshop with FI/MM/SD/CO/HR/PP/QM leads. Week 3: Fusion-side architecture preview — COA design, organisational structure, ledger map. Weeks 4–5: integration estate sizing, support-contract review, business case modelling, risk register, executive deliverables.
The deliverables hand to CIO, CFO, controllership, IT steering and external audit. They form the basis of the go/no-go decision, and they sit at the front of the cutover evidence binder — three years from now, the assessment is the document that explains every design choice the auditor questions.
Each is a separate evidence track that lands in the deliverables — none are skipped.
Active modules and submodules (FI / CO / MM / SD / PP / QM / PM / PS / HR), usage profile per module, business-criticality classification, volume metrics per table.
Every Z-* table, every Z append on standard tables, every BAdI implementation, every user exit, every custom ABAP report — typically 800–4,000 objects classified.
Every active Integrated Configuration enumerated, sized, classified by criticality, with Fusion-target recommendation (OIC flow, REST API, retire).
Company codes, legal entities, country-specific e-invoicing flows (Italian SDI, French Chorus Pro, Polish KSeF, Mexican CFDI, Brazilian SPED), VAT registration footprint.
Leading ledger 0L plus every non-leading ledger (IFRS / HGB / US-GAAP), local + group + hard currency configuration per company code, fiscal-variant assignment.
Database platform (Oracle / HANA / DB2 / SQL Server / MaxDB), version, edition, sizing. ABAP Basis level. Extraction-mode feasibility (direct-DB / BAPI / IDoc / ABAP CDS / SLT).
Current support contract type, mainstream vs extended status, contract end date, customer-specific-maintenance feasibility, total annual support baseline.
Pillars in scope, organisational structure, six-segment COA design, calendar map, ledger map, country-specific configuration — sketched before commit.
3–5 weeks elapsed, mostly automated discovery plus targeted workshops with FI/MM/SD/CO/HR domain leads.
Read-only ECC connection established (RFC display-only or direct-DB read-only). Discovery engine runs ABAP Dictionary crawl, BAdI registry scan, user-exit catalog scan, custom-report inventory, PI/PO ICO export, country e-invoicing flow detection. Raw inventory produced.
FI/CO lead, MM/Procurement lead, SD/OM lead, HR/HCM lead, PP/Manufacturing lead walk the Z-* inventory. Each Z-* object classified: collapse to Fusion / replace with Fusion native / retire. Decisions captured and signed.
Every active Integrated Configuration reviewed with integration architect. Each gets a Fusion target recommendation (OIC flow, REST API, third-party iPaaS, retire). Effort estimate per integration.
Six-segment COA designed from ECC SKB1 + KOSTL + PRCTR + SEGMENT structure. Organisational structure designed from ECC company-code + sales-org + plant map. Ledger map designed from ECC leading + non-leading ledgers. Calendar map and currency map designed.
Support-cliff exposure quantified. HANA licence trajectory modelled. RISE alternative cost modelled. Fusion subscription costed. Migration budget envelope sized. Top 10 risks costed and mitigated.
Five executive deliverables packaged for steering committee. CIO/CFO/controllership/IT-steering/external-audit briefings. Go/no-go decision supported by signed evidence pack.
A real assessment moves the project's risk profile from 'unknown unknowns dominate' to 'sized knowns dominate' — that's the value.
Z-* estate, BAdI count, country e-invoicing flows, PI/PO ICOs all known and signed before build commits. No mid-build scope shocks.
Every line item sized from evidence: Z-* labour from object count, integration labour from ICO count, country labour from jurisdiction count. CFO defends the number.
Six phases timed from your specific volume profile, customisation footprint and country footprint. 9–14 months for full pillar — based on your reality, not a brochure.
Assessment evidence pack sits at the front of the cutover binder. Wirtschaftsprüfer and external audit have the rationale for every design choice — three years later.
Dec 2027 / 2030 support-cliff exposure costed. HANA licence trajectory costed. RISE alternative costed. The CFO has the comparator the go/no-go requires.
Fusion-side architecture sketched in week 3 — six-segment COA, org structure, ledger map. Not principles in a PowerPoint. The architecture review starts here, not in build month 4.
A sap ecc migration assessment is the structured pre-project diligence that establishes scope, complexity, risk, timeline and budget for an ECC-to-Fusion programme — completed before any irrevocable commitment. Syntra ETL runs it in 3–5 weeks. Output covers: ECC modules and submodules in scope (FI / CO / MM / SD / PP / QM / PM / PS / HR with usage profile per module), Z-* custom inventory (every Z-* table, append structure, BAdI, user-exit, ABAP report enumerated and classified), volume profile per table (BKPF/BSEG row counts per fiscal year, KNA1/LFA1/MARA cardinality, MSEG goods-movement velocity), country / legal-entity / company-code map, parallel-currency and multi-ledger configuration, PI/PO integration estate, country e-invoicing flows, support contract status (mainstream vs extended), database platform, ABAP basis stack level, and the Fusion-side target architecture (pillars in scope, organisational design, COA design preview).
The discovery engine connects to ECC in read-only mode (RFC user with display-only authorisations or direct-DB read-only) and crawls: DD02L (table directory) for every Z-* table; DD03L (table-field directory) for every Z-* column on standard SAP tables (Z appends to BSEG, KNA1, LFA1, MARA, EKKO, VBAK and dozens of others); the BAdI registry (SBADI, BADI_REG) for every active BAdI implementation; the user-exit catalog (MODSAP, MODACT) for SMOD/CMOD enhancements; the custom-report repository (TADIR with object type PROG, FUGR, CLAS for Z* names); Sapscript and Smartform inventory; and the SE38/SE80 ABAP source where customer-namespace code lives. Every object is enumerated, sized (row count per Z table, line-count per Z program), classified by reporting/operational/analytical materiality and assigned a recommended routing (collapse / replace / retire). A mature ECC tenant typically inventories 800–4,000 custom objects — the sap ecc migration assessment surfaces them before scope and budget are set.
BAdIs (Business Add-Ins, the modern enhancement framework) and user exits (older customer-exits and SAP enhancement points) are the places where customer-specific business logic sits inside otherwise-standard SAP transactions. A high BAdI/user-exit count means the live ECC system runs many customisations that have to be replicated, replaced or retired on the Fusion side. Sap ecc migration assessment classifies each: business-critical (must replicate in Fusion via configuration, OIC integration or extension), redundant under Fusion native (Fusion's native capability subsumes the customisation — retire), partially redundant (Fusion covers 70% — configure the rest). A mature ECC tenant typically has 100–600 BAdI/user-exit implementations; 40–60% retire as redundant during Fusion conversion. The remaining 40–60% drive a meaningful slice of the Fusion configuration and OIC integration effort — sized in the assessment, not surprises during build.
SAP ECC mainstream support ends December 2027. Customers can extend to December 2030 by paying a 2% maintenance uplift annually (the SAP Extended Maintenance contract). Beyond 2030, customer-specific maintenance is available on bespoke commercial terms — at significant cost. Sap ecc migration assessment includes a support-status review: current support contract type, contract end date, extended-maintenance election status, customer-specific maintenance feasibility for the customer's footprint, total support spend per year baseline. This feeds the migration timeline urgency calculation: customers without extended maintenance need to cut before Dec 2027; customers with extended maintenance have headroom to 2030 but at a 2% premium; customers beyond 2030 face escalating support cost. The assessment quantifies the cost of inaction — a number that typically dwarfs the migration budget itself.
Yes — and it materially affects extraction strategy. ECC runs on Oracle DB (the original ECC database, still common in Oracle-leaning customers), SAP HANA (the SAP-recommended modern path), IBM DB2 LUW, IBM DB2 for z/OS (mainframe), Microsoft SQL Server, or SAP MaxDB. Sap ecc migration assessment captures the platform, version, edition, sizing and licence cost. Extraction implications: Oracle DB and HANA allow Syntra ETL's direct-DB read-only extractor (fastest path), SQL Server and DB2 LUW likewise, DB2 z/OS requires Connect-style routing, MaxDB requires SLT replication. Licence implications matter for the business case — Oracle DB licences and HANA licences are large recurring costs that drop out post-migration, and the savings (typically 6 to 7 figures annually for mid-market) are a major line item in the Fusion business case.
SAP Process Integration (PI/PO, formerly XI) sits between ECC and dozens of downstream systems — bank statement consumers, EDI partners, tax engines, e-invoicing platforms, warehouse management, MES, BI tools. Migrating ECC to Fusion means every active PI/PO Integrated Configuration (ICO) needs a Fusion-side equivalent on cutover day. Sap ecc migration assessment connects to PI/PO (or extracts the ICO catalogue export) and enumerates: every active ICO with source and target systems, payload schema, transformation logic, business criticality, volume per day, error rate baseline. Output: a sized integration inventory typically showing 30–200 active ICOs in a mature ECC tenant. Each ICO gets a Fusion target recommendation (Oracle Integration Cloud flow, REST API integration, OIC adapter, third-party iPaaS, or retire). The PI/PO decommissioning workstream is sized from this — typically a parallel 4–8-month effort to the data migration.
The Fusion-side preview is the half of the assessment that turns the ECC scope into a target architecture sketch before the project commits to it. For each in-scope ECC module, the preview specifies: the corresponding Fusion pillar (FI/CO → ERP Financials, MM → ERP Procurement + Inventory, SD → ERP Order Management + Receivables, HR → HCM, PP → SCM Manufacturing), the organisational structure (Enterprise → Divisions → Business Units → Inventory Orgs based on the ECC company code / sales-org / plant map), the COA design (six-segment Fusion COA derived from the ECC SKB1 + KOSTL + PRCTR + SEGMENT structure), the calendar map (one Fusion accounting calendar per ECC fiscal-variant), the currency map (Fusion ledgers per ECC ledger × parallel-currency configuration). Customers regularly find this preview is where the biggest architecture decisions actually get made — typically a month earlier than on consultant-led programmes.
Five executive deliverables. (1) Sized scope document — modules, country/entity map, volume profile, Z-* inventory headline. (2) Timeline and resource plan — 9–14 months for full-pillar conversion, broken into the six standard phases. (3) Budget envelope — Syntra ETL platform fee, OIC integration build, Fusion subscription, Fusion implementation labour, parallel-run cost, decommissioning cost. (4) Risk register — sequenced by likelihood × impact, with the top 10 risks costed and mitigated. (5) Cost-of-inaction analysis — 2027/2030 support cliff exposure, HANA licence trajectory, RISE subscription comparison, business case ROI versus deferral. The deliverables go to CIO, CFO, controllership, IT steering, and external audit — and form the basis of the migration go/no-go decision.
30-minute discovery call. We'll scope the assessment for your ECC footprint, walk through the deliverables, and propose a kickoff date within 3 weeks. The assessment costs less than a single delayed cutover week.