SAP ECC
Carry forward what S/4HANA needs. Preserve the rest. Retire ECC before the maintenance deadline.
SAP ECC migrations move balances, open items and master data. They do not move a decade of document-level history, and the ECC landscape usually stays up to serve it — carrying its own licence, database, hardware and Basis support cost long after S/4HANA is live.
An S/4HANA conversion or greenfield build takes balances, open items and master data. Line-item history from closed periods, completed purchasing and sales documents, retired assets and archived HR records stay in ECC because the Universal Journal and Business Partner models do not accept them in their original form.
The ECC landscape then stays up for statutory retention, tax audit, comparatives and the occasional document retrieval — with its database licence, its hardware or cloud footprint, its non-production copies and its Basis support all still being paid for.
A Legacy Exit extracts ECC document-level history and its attachments into DataVault, reconciles totals back to source, provides searchable access and export through DataLens, and lets the ECC landscape be decommissioned.
Two flows, run by the same platform. What the new application needs is migrated. Everything else is preserved and made accessible, which is what allows the old environment to be switched off.
ECC scope is normally defined by module and by fiscal year, against your statutory retention requirements.
BKPF and BSEG document headers and line items, GL accounts, balances by period and fiscal-year close positions.
Cost centres, internal orders, profit centres and the cost postings against them.
Purchase requisitions, purchase orders, goods receipts, invoice receipts and vendor history.
Sales orders, deliveries, billing documents and customer history.
Asset master records, acquisitions, retirements and depreciation history.
Material documents, stock movements and valuation history.
Infotype history, organisational assignment, payroll results and year-end records where HR ran in ECC.
DMS and ArchiveLink content — scanned invoices, contracts and correspondence — linked to source documents.
CDHDR and CDPOS change history that gives archived documents their audit value.
The parts of this platform that decide whether a retirement succeeds or stalls.
Nobody signs off a decommissioning on the basis that the archive looks right. Each extract is reconciled back to SAP ECC and the evidence is retained as part of the decommissioning pack.
Illustrative figures shown to explain how reconciliation evidence is presented. They are not drawn from a specific customer engagement.
A single-module ECC archive scoped to a defined fiscal-year range is typically weeks after discovery. Multi-module, multi-company-code landscapes with ArchiveLink content run longer, and discovery sets the duration before implementation is committed.
Work is delivered as fixed-scope packages priced against the scope established in a Legacy Exit Discovery. Projects typically start from £25K. UK public-sector buyers can call the work off through G-Cloud 15.
Published SyntraETL engagements on the same architecture. Every figure below comes from the referenced case study rather than from a marketing claim.
Finance, procurement and master data migrated out of SAP ECC with source-to-target reconciliation at every cycle.
Read the case study →A government body migrated Oracle EBS financials to Oracle Fusion with a controlled, repeatable and reconciled migration process.
Read the case study →Historical records retained in a searchable archive so the source environment could be reduced.
Read the case study →A Legacy Exit Assessment establishes which ECC modules and which years are genuinely required, what the landscape costs today, and what a scoped retirement would take ahead of your maintenance deadline.