SAP S/4HANA Data Migration Troubleshooting: Resolving the Errors That Delay Go-Live
SAP S/4HANA data migration fails on data more often than tools. Common Migration Cockpit errors, causes and fixes, and how to validate before go-live.

SAP S/4HANA data migration is the transfer of master data and open transactional data from a legacy system, such as SAP ECC or another ERP, into the S/4HANA data model, most often through SAP's Migration Cockpit. When it fails, the cause is usually the data rather than the tool: records that do not fit the new model, mappings left unconfirmed, objects loaded out of order, or checks that compared record counts instead of balances.
This guide maps the common failures to their causes and fixes, explains how the Migration Cockpit works, and sets out a validation method that catches errors in rehearsal instead of at the first period-end close.
Where engini fits: engini is not a migration tool; use SAP's Migration Cockpit for the load. Around the migration, engini's SAP S/4HANA connection reads and writes records through SAP's OData services, in the cloud or on-premises, so you can build reconciliation checks that compare legacy data with what landed in S/4HANA during each rehearsal, and reconnect the CRM, store, bank files and databases that fed the old system. See the SAP S/4HANA connection docs.
Key Takeaways
- Most SAP S/4HANA migration failures come from the data: its quality, its fit with the new data model, and the order it is loaded in.
- SAP's Migration Cockpit, opened from the Migrate Your Data app, loads data through staging tables or directly from an SAP system over an RFC connection.
- A migration object can fail when its predecessor objects were not migrated first, or when the user lacks permission for that type of data.
- In a conversion from SAP ECC, customers and vendors become business partners through Customer-Vendor Integration (CVI), and the migration cannot happen until CVI is complete.
- Matching record counts proves little. Validate structure, references, business rules, balances and processes.
- Every interface that fed the old system has to be rebuilt and tested against S/4HANA before cutover.
What Are the Biggest SAP S/4HANA Data Migration Challenges?
The biggest SAP S/4HANA data migration challenges are a changed data model, legacy data quality, dependencies between objects, custom fields, authorizations, and too few rehearsals. Each one is cheaper to fix in the source system months before cutover than in S/4HANA during it.
| Challenge | What goes wrong | What to do early |
|---|---|---|
| Business partners | Customers and vendors become business partners. In a conversion from ECC, the migration cannot happen until CVI is complete, and duplicate or inconsistent records surface late | Audit customer and vendor data now, and design the CVI approach with finance, procurement and sales |
| The universal journal | Financial accounting and controlling data sit in one table, ACDOCA, the single source of truth for financial data, so FI and CO no longer need reconciling in S/4HANA. Legacy FI and CO data that never agreed has to be resolved before or during the load | Check that FI and CO agree in the source system before extraction |
| Data quality | Duplicates, incomplete records and obsolete records fail validation or load as clutter | Profile and clean in the source; archive what you will not migrate |
| Object dependencies | An object fails because a record it refers to does not exist yet | Build a load sequence from each object's predecessors |
| Custom fields | Fields outside the standard templates arrive empty | Check which objects the Migration Object Modeler can extend, and plan the rest |
| Authorizations | A user can open the cockpit but cannot migrate an object | Assign permission for each type of data before the first mock load |
| Rehearsals | Durations and failures are only discovered at cutover | Run more than one full mock migration with production-like data |
For a finance team's view of the same project, see SAP data migration tools for finance teams.
How the SAP S/4HANA Migration Cockpit Works
The Migration Cockpit is SAP's tool for loading data into S/4HANA: you open it from the Migrate Your Data app on the Fiori launchpad, choose a migration approach, and move each migration object through preparation, mapping, an optional simulation and the migration itself.
SAP's course for S/4HANA Cloud Private Edition describes two approaches:
- Migrate data using staging tables. Staging tables are temporary tables that hold your data before it moves into S/4HANA. You fill them, for example, from SAP's XML or CSV templates.
- Migrate data directly from an SAP system. An RFC connection links a source SAP ERP system on a compatible release to the target, and the source data is converted to the S/4HANA data model automatically.
Each migration object then goes through the same steps:
- Prepare the staging tables, or select the data to transfer.
- Process mapping tasks, where you confirm value mappings and fixed-value mappings between source and target values.
- Simulate the migration. SAP lists this step as optional.
- Migrate the data.
If the Simulate or Migrate step finds errors, you can correct the data and run the step again, for example with a correction file. The Data Migration Status app summarizes the status of every migration object. The Migration Object Modeler lets you customize a small set of released migration objects, which matters when your data has custom fields. SAP documents every available migration object in the SAP Help Portal, and each object's Post-Processing section names the app to use for checking the migrated data.
Tip: run the simulation even though it is optional. It is the cheapest place to find mapping and data errors, before the real migration step runs.
Note: SAP's course material quoted here covers S/4HANA Cloud Private Edition and S/4HANA Cloud. Check the documentation for your own release and edition before you plan the load.
SAP S/4HANA Migration Error Reference
Use this table as a first pass when a migration object fails: find the symptom, check the likely cause, and fix it in the source data or the mapping, not by editing records in the target.
| Symptom | Likely cause | What to check and fix |
|---|---|---|
| Records fail because a referenced customer, vendor, material or account does not exist | A predecessor object was not migrated first | Check the object's predecessors and migrate them first; load organizational data, then master data, then open items |
| A user opens Migrate Your Data but cannot migrate an object | Missing permission for that type of data | Assign the authorization for each type of data the user migrates |
| Values rejected, such as payment terms, plants or tax codes | A mapping task not confirmed, or a source value with no target value | Process the mapping tasks; add the missing configuration or map the value |
| Customer or vendor records fail, or one company appears as several business partners | Duplicate or inconsistent legacy data; CVI not complete in a conversion | Deduplicate and clean before CVI; agree who owns each record |
| Balances in S/4HANA differ from the legacy trial balance | Balances and open items extracted at different cut-off times, or accounts and profit centers mapped wrongly | Extract everything at one cut-off, check the account mapping, and compare balances by company code, account and period |
| Custom fields arrive empty | The field is not part of the migration object's template | Extend the object with the Migration Object Modeler if it is released for that, or plan a separate load for those fields |
| Values rejected or cut short | Source format or length does not match the target: dates, decimals, leading zeros, text length | Profile the source and fix the extraction; validate structure before the staging load |
| Inventory value differs after the load | Quantities and values loaded from sources that were out of step | Reconcile stock quantity and value per plant and material before extraction and after the load |
| The same errors return in every mock load | Fixes made in staging, not in the source | Fix the source data or the extraction rule, so the next extraction is clean |
Data Migration Testing: Validate at Five Levels
Matching record counts between source and target does not prove a migration worked. A load can match every count and still post the wrong profit center, flip a debit to a credit, or convert a currency at the wrong rate. Validate at five levels:
| Level | What it catches | Example check |
|---|---|---|
| 1. Structure | Wrong types, lengths, empty required fields | Every staging row passes format and required-field checks before the load |
| 2. References | Records pointing at master data that does not exist | Every open item's customer, vendor and account exists in S/4HANA |
| 3. Business rules | Valid records that break business logic | Document types, posting keys and tax codes match the agreed mapping |
| 4. Balances | Totals that drift even when counts match | General ledger, receivables aging, payables and stock value agree by company code and period |
| 5. Processes | Data that loads but does not work | A payment run, a billing run and a period-end step complete on migrated data |
Levels 3 to 5 catch the errors that become financial misstatements at the first close. Automate levels 1 to 4 so you can run them after every rehearsal, not once before go-live. For test design beyond migration, see our integration testing guide.
Rehearsals, Cutover and the Interfaces Around S/4HANA
A cutover goes to plan when every step has already been run and timed in a rehearsal with production-like data. Plan more than one full mock migration, and record how long each object takes, how many errors it raised, and what fixed them.
- Load in waves. Load stable master data ahead of the cutover window where you can, and keep the window for open items and the final changes.
- Set go or no-go criteria from the five validation levels, agreed with finance before the weekend, not during it.
- Freeze changes in the source system's master data for the cutover period, with an agreed path for urgent exceptions.
- Rebuild the interfaces. Every system that exchanged data with the old ERP, such as the CRM, the online store, the warehouse system, bank and payment files, and internal databases, must be pointed at S/4HANA and tested in the same rehearsal. An interface tested only after go-live is the next source of reconciliation errors.
For a step-by-step view of the cutover itself, see running an SAP cutover with AI agents.
How engini Helps Around an SAP S/4HANA Migration
engini does not replace the Migration Cockpit. It helps before, during and after the load, wherever S/4HANA has to exchange data with other systems or be checked against them.
- Reconciliation checks in every rehearsal. A workflow in Workflow Studio, engini's visual builder, reads records from S/4HANA through the OData service that exposes them, reads the legacy extract from a database or a CSV file, compares the two, and writes each difference into an engini Table for the team to review. Each run is kept in the workflow's run history, so you can compare rehearsals.
- SAP S/4HANA, both ways. The connection gets, creates, updates and deletes records on any object a selected OData service exposes, reads the service's metadata, and can send a custom request to any endpoint. Fields load per object from the service's metadata. It signs in with OAuth 2 or a user name and password, as your SAP administrator sets it up, and a connection setting chooses cloud, or on-premises and private cloud.
- Systems on your own servers. The on-prem agent reaches databases such as SQL Server, Oracle Database and IBM DB2, and file drops in local folders and network shares, opening only outbound connections, so you open no inbound ports.
- The interfaces after go-live. Reconnect Salesforce or HubSpot, Shopify, bank and payment files over SFTP, and internal databases to S/4HANA. Every integration runs both ways, so invoices and payment status can flow back to the CRM. See the integrations, and for the CRM side, our Salesforce and SAP integration guide.
- Judgment where it helps. Add an AI agent step to a workflow for a task such as grouping reconciliation differences by likely cause, and keep the posting decisions with your team.
- Controls. Roles, single sign-on, separate development, staging and production environments, and an audit log with export and streaming to a SIEM. engini holds SOC 2 Type II and ISO 27001.
When you do not need engini: for the initial load itself, use the Migration Cockpit. If all your data comes from one SAP system that direct transfer covers, and no system outside SAP exchanges data with S/4HANA, SAP's own tools may be all you need. If your interfaces depend on IDocs or RFC calls, check with engini before you plan on it: the documented connection works through SAP's OData services.
Agent gateway
Ship agents into systems you can’t afford to break
Connect AI agents to your ERP, CRM, financial and legacy systems through MCP, SDK, API or canvas, with secure auth, tool permissions and an audit trail built in.
Frequently Asked Questions
What is SAP S/4HANA data migration?
SAP S/4HANA data migration is moving master data and open transactional data from a legacy system into S/4HANA's data model. Most projects use SAP's Migration Cockpit, with staging tables or a direct transfer from an SAP source system, and validate the result before go-live.
What are the biggest SAP S/4HANA migration challenges?
The biggest challenges are data quality, the new data model, object dependencies, custom fields and too few rehearsals. Business partners and the universal journal change how customer, vendor and financial data is stored, so legacy problems surface during the load.
Why did my migration object fail in the SAP S/4HANA Migration Cockpit?
Two common reasons are a predecessor object that was not migrated first and a user without permission for that type of data. Unconfirmed mapping tasks and source values with no target value are the next things to check.
Is simulation required in the SAP S/4HANA Migration Cockpit?
No, SAP lists the simulation step as optional. Running it is still worth the time, because it finds mapping and data errors before the real migration step.
How do you test an SAP S/4HANA data migration?
Test at five levels: structure, references, business rules, balances and processes. Record counts alone miss wrong assignments, sign errors and currency errors, which surface at the first period-end close.
Can engini migrate data into SAP S/4HANA?
engini is not a migration tool, so use SAP's Migration Cockpit for the load. engini helps around it: reconciliation checks between legacy data and S/4HANA during rehearsals, and the interfaces between S/4HANA and your other systems after go-live.
Sources
- SAP Learning: Migrating Data to SAP S/4HANA Cloud Private Edition
- SAP Learning: Introducing the SAP S/4HANA Migration Cockpit
- SAP Learning: Discussing the Concept of the Universal Journal
- SAP News Center: The SAP Migration Mistake Most Companies Make (October 14, 2025)
- engini docs: SAP S/4HANA
- engini docs: On Prem Agent
- engini docs: Workflow Run History