

How to migrate from SAP ECC to SAP S/4HANA
To migrate a client from SAP ECC to SAP S/4HANA with superglue's AI agent, connect the client's SAP ECC system, and give superglue access to the client's SAP S/4HANA account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs trial loads that reconcile to the cent before cutover. You review, decide and sign off with the client.
SAP ends mainstream maintenance for SAP ERP 6.0 with enhancement packages 6 to 8 at the end of 2027, and paid extended maintenance runs to the end of 2030, so most ECC clients plan their move now. This guide covers a new implementation of SAP S/4HANA, where selected data moves from ECC. A new implementation is the only path into SAP S/4HANA Cloud Public Edition. For Private Edition or on premise, the client can also choose a system conversion or a selective data transition.
What are the steps to migrate from SAP ECC to SAP S/4HANA?
Migrating from SAP ECC to SAP S/4HANA takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run trial loads and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect SAP ECC and SAP S/4HANA
Connect SAP ECC read-only through the services the client's SAP team exposes, such as OData on SAP Gateway, or upload the extracts the team runs. superglue writes nothing. The client then gives superglue access to SAP S/4HANA.
- 02
Assess the SAP ECC data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the SAP ECC specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial loads
superglue loads the SAP S/4HANA quality or test system and compares it with SAP ECC: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. superglue explains every difference, and you repeat the trial load until a full run reconciles with no new differences. The last run is a timed rehearsal of the cutover.
- 06
Cut over
At cutover, the client stops entry in SAP ECC, and superglue loads the open items with the same steps as the trial loads. After the client closes the last period in SAP ECC, superglue loads the final balances, and you sign the reconciliation with the client.
How do you get the data out of SAP ECC?
- ECC has no general-purpose OData API for finance and master data. OData exists only for specific Fiori apps or for services built on SAP Gateway. The client's SAP team exposes the tables superglue needs to a technical user, or runs the extracts, and the superglue gateway reaches the system on the client's network.
- Ask which company codes, plants and sales organizations are in scope, because one ECC system often runs several countries.
- Ask which years were archived. Archived documents are no longer in the database, so those years move as balances.
On-premise clients install the superglue gateway once: Connecting to on-prem systems
What needs to be configured in SAP S/4HANA?
In SAP S/4HANA Cloud Public Edition, the client sets up a communication user and the communication arrangements for the APIs superglue uses. On premise, the client activates the OData services for a technical user. In SAP S/4HANA Cloud Public Edition, the implementation team sets the organizational structure in Central Business Configuration, and superglue prepares and checks the values. superglue then loads the data through the Migration Cockpit, in the quality or test system first, in this order:
- 01
Group currency, the fiscal year variant and the company codes with their currencies. In the public cloud, the fiscal year variant cannot change after the primary finance settings are saved.
- 02
The chart of accounts. In the public cloud, every company code shares one operating chart of accounts, YCOA. The team adapts it with the client's own accounts, and a country chart can hold local account numbers.
- 03
Profit centers, cost centers and segments for reporting.
- 04
Business partner settings, house banks, payment terms and tax codes.
- 05
Business partners and products, then the G/L balances and open items at the migration key date.
What moves from SAP ECC to SAP S/4HANA?
| In SAP ECC | In SAP S/4HANA |
|---|---|
| G/L accounts per chart of accounts and company code | G/L accounts |
| Cost centers, profit centers and business areas | Profit centers, cost centers and segments |
| Customers | Business partners in the customer role |
| WBS elements in Project System | Projects |
| Vendors | Business partners in the supplier role |
| Materials | Products |
| House banks and bank accounts | House banks and bank accounts |
Open items
Open receivables and payables items, open sales and purchase orders, and stock per plant and storage location with its valuation.
Open items load through the Migration Cockpit as receivables and payables open items at the migration key date, with their original due dates, so the aging in SAP S/4HANA matches on day one.
History
ECC keeps G/L balances per period and every document that was not archived. superglue reads the balances for the years the client wants to keep and reports which years were archived.
History loads as monthly G/L balances for earlier periods through the historical balance migration object, for reporting only, and older detail stays in an archive the client keeps.
Which decisions do you make when you migrate from SAP ECC to SAP S/4HANA?
- 01
Which ECC records move?
A new implementation moves only the records the business still uses, and the old system or an archive keeps the rest.
superglue recommends customers, vendors and materials with activity in the last two years, plus every record with an open item or open order.
- 02
Do the ECC cost centers and profit centers stay?
SAP S/4HANA uses the same cost center and profit center objects, and with document splitting the universal journal fills the profit center on receivables, payables and tax lines too.
superglue keeps the cost centers and profit centers the client still reports on, and proposes a profit center for each cost center without one.
- 03
How many company codes does the client need?
A company code is a legal entity in SAP S/4HANA, with its own currency and books, and it belongs to one country.
superglue recommends one company code for each legal company in SAP ECC.
- 04
Which migration key date does the client use?
The migration key date sets the posting date for the balances and open items of each company code. Fixed assets have their own transfer date.
superglue recommends the last day of a closed period, so the opening balances match an approved trial balance.
- 05
How much history moves?
Most clients need the open items plus one to three years of monthly balances in SAP S/4HANA, at least the current and the prior fiscal year for comparison, and older years as yearly balances. The client keeps the older detail in an archive.
superglue recommends two years of monthly balances per account, and full transaction detail only where the client needs to look into single transactions.
What are the common challenges when you migrate from SAP ECC to SAP S/4HANA?
The client's SAP team sets the pace
ECC has no standard API for finance and master data, so every extract and every technical user goes through the client's SAP team. Their queue often decides when the assessment can start, so request access in the first week.
Years of unused records
ECC systems that run for 15 years or more hold many customers, vendors and materials nobody uses. Agree a cut-off with the client, such as no activity in two years. superglue lists the records without activity, so only live data moves.
Custom fields and tables hold business data
Most ECC systems have Z fields and Z tables that hold data the business relies on. superglue lists every custom field that holds data, so the client decides which ones come back in the new system.
Classic G/L lines have no profit center
Systems on the classic general ledger or without document splitting post many lines without a profit center or segment. superglue derives them from the cost center and the account, and lists the lines it cannot derive.
Business areas need a new home
SAP S/4HANA Cloud Public Edition has no business areas, and on premise they get no new development. Reports built on business areas move to profit centers or segments, so agree the new structure with the controller before the mapping starts.
Valuation classes decide the stock accounts
In ECC, the valuation class on each material and the account determination decide which G/L accounts stock and cost of goods sold post to. superglue reads the account determination and proposes the same posting setup in the new system, so stock postings stay the same.
Rehearse every load in the test system
In SAP S/4HANA Cloud Public Edition, the Migration Cockpit cannot delete or reverse migrated data, and it does not load the same record twice. Rehearse each load in the quality or test system, set up the migration project again in production, because projects do not transport between systems, and load production once the reconciliation is signed.
Customers and vendors become one business partner
SAP S/4HANA keeps a company once as a business partner with a customer role, a supplier role or both. Agree with the client how duplicates across the old customer and vendor lists merge, because the address and bank details are kept once.
Every line needs its profit center
SAP S/4HANA keeps G/L, controlling and asset postings in one journal. Document splitting puts a profit center and a segment on each line, and lines on cost accounts also carry a cost object such as a cost center. Agree the profit center and cost center design before balances move, because the migrated balances carry them.
Plan fixed assets as their own stream
The trial balance brings the cost and the accumulated depreciation, but the asset register needs each asset with its in-service date, useful life and depreciation to date, and tax books need their own values. Agree early where the register lives after go-live, and reconcile it to the asset accounts.
superglue also runs the rest of the SAP S/4HANA project. See the SAP S/4HANA implementation
Frequently asked questions
Which data moves from SAP ECC to SAP S/4HANA?
The chart of accounts, customers, vendors and items, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in SAP S/4HANA.
Does superglue run an SAP system conversion?
No. A system conversion turns the ECC system into SAP S/4HANA in place, with SAP's tools. superglue runs the new implementation: it moves the master data, the open items and the balances into a clean SAP S/4HANA system.
Does superglue write to SAP S/4HANA without my approval?
No. superglue only reads SAP ECC. Before any write to SAP S/4HANA, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against SAP ECC: the trial balance per period, the open receivables and payables per customer and vendor, the uncleared bank items, and the inventory value. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Northwind Outdoor Supply, a sample client.
Start your SAP ECC to SAP S/4HANA migration
Sign up and connect the client's systems, or let superglue set up Northwind Outdoor Supply, a sample client, to see a full migration run first.