SAP Data Migration Tools: What Each One Does, and How Finance Teams Prove the Numbers Moved
SAP data migration tools compared: Migration Cockpit, Software Update Manager, SAP LT and Syniti ADM, plus how finance teams prove the migrated numbers.

SAP data migration tools are the SAP products that move data into SAP S/4HANA, and which one you use depends on your transition approach: the SAP S/4HANA Migration Cockpit loads data into a new implementation, the Software Update Manager (SUM) converts an existing SAP ERP system, SAP Landscape Transformation (SAP LT) enables a selective data transition, and SAP Advanced Data Migration and Management by Syniti adds an orchestration and data-quality layer on top for large programs.
For a finance team, the choice of tool matters less than the proof that comes after it. General ledger balances, open receivables and payables, fixed assets and master data have to reconcile between the old system and S/4HANA before anyone signs off on go-live.
Where engini fits: engini is not an SAP migration tool, and the load itself belongs in SAP's tools. engini works around them: its SAP S/4HANA connection reads and writes through SAP's OData services, and its database, file and on-prem connections reach the legacy side, so you can build reconciliation checks that run after every mock load and rebuild the interfaces that fed the old ERP. See the SAP S/4HANA connection docs.
Key Takeaways
- SAP names a different tool for each transition approach: the Migration Cockpit for a new implementation, SUM for a system conversion, and SAP LT for a selective data transition.
- The Migration Cockpit is embedded in SAP S/4HANA at no additional cost and loads data from SAP or non-SAP legacy systems through staging tables, or directly from an SAP ERP system.
- SAP Advanced Data Migration and Management by Syniti is an SAP Solution Extension that orchestrates the work from extraction to reconciliation; SAP says it does not replace SAP's native ETL tools.
- Finance should own the reconciliation criteria: balances, open items and assets agreed by company code and period, at one cut-off.
- AI is useful for reading, comparing and explaining differences; deterministic checks should still decide whether a migration passes.
SAP Data Migration Tools at a Glance
Each SAP data migration tool covers a different part of the move to S/4HANA. This table summarizes what SAP's own course material says each one does.
| Tool | Transition approach | What it does |
|---|---|---|
| SAP S/4HANA Migration Cockpit | New implementation | Loads legacy data into S/4HANA through staging tables, or directly from an SAP ERP system over an RFC connection |
| Migration Object Modeler | With the Migration Cockpit | Changes the structure or mapping of a staging table |
| SAP Data Services or other ETL | With the Migration Cockpit | Fills staging tables from source systems |
| Software Update Manager (SUM), with the Database Migration Option (DMO) | System conversion | Runs the database migration, software update and data conversion of an existing SAP ERP system |
| SAP Landscape Transformation (SAP LT) | Selective data transition | Moves selected configuration, master data, open items and a time slice of closed items |
| SAP Business Transformation Center | Selective data transition | Runs a Lean Selective Data Transition, including closed and historical data |
| SAP Advanced Data Migration and Management by Syniti | Large programs, alongside SAP's tools | Orchestrates extraction, profiling, mapping, enrichment, test loads, loading and reconciliation |
Sources: SAP Learning courses on S/4HANA Cloud Private Edition data migration, transition paths, selective data transition, SAP Business Transformation Center and the agent-led toolchain, read November 2026.
Which SAP Migration Tool Fits Your Transition Approach?
Your transition approach decides the tool, so decide the approach first. SAP describes three main paths to S/4HANA:
- New implementation (greenfield). You install a new S/4HANA system and load your data into it. SAP names the Migration Cockpit as the tool that migrates legacy data into the target system. This is the usual path when the legacy system is not SAP, or when you want to redesign processes.
- System conversion (brownfield). You convert your existing SAP ERP system to S/4HANA. SAP names the Software Update Manager as the tool for the database migration, the software update and the data conversion; the Database Migration Option is an optional feature of SUM.
- Selective data transition. You choose which configuration, master data and transactions move, for example open items plus two years of closed items. SAP says this is enabled through SAP LT, with two common patterns: a shell conversion, where a copy of production without master and transaction data is converted, and mix and match, where a new install receives selected configuration and code. SAP also notes that partners use their own tools here and that SAP does not certify third-party products for selective data transition.
Note: SAP's course material quoted here covers S/4HANA Cloud Private Edition and related courses. Check the documentation for your own release and edition before you plan the project.
The SAP S/4HANA Migration Cockpit
The Migration Cockpit is SAP's standard tool for loading data into a new S/4HANA system, and it is embedded in S/4HANA at no additional cost. You open it from the Migrate Your Data app on the Fiori launchpad, and it supports migration from as many legacy systems, SAP or non-SAP, as you need.
It works in two ways:
- Staging tables. The cockpit generates a staging table for each migration object. You fill it from SAP's XML or CSV templates, which open in Excel, or with ETL code or SAP Data Services.
- Direct transfer. An RFC connection links a source SAP ERP system on a compatible release to the target, and the data is transferred from it directly.
When a staging table does not fit your data, the Migration Object Modeler lets you change its structure or mapping. The Data Migration Status app summarizes the status of every migration object, so the team can see what has loaded and what has failed.
For the errors the cockpit raises and how to fix them, see our SAP S/4HANA data migration troubleshooting guide.
SAP Advanced Data Migration and Management by Syniti
SAP Advanced Data Migration and Management by Syniti is an SAP Solution Extension for the data side of a transformation. SAP's course material describes it as an orchestration and management layer, not a replacement for SAP's native ETL tools, and lists eight steps it covers: extract, assess, design, enrich, transform, simulate, load and reconcile. Business users can enter and cleanse data through web forms, and the reconcile step monitors migration quality and confirms data integrity after the load.
It earns its cost on large programs: many source systems, poor data quality, many business owners who need to sign off on their data, and several waves of loads. A single-company migration from one clean source may not need it.
What Finance Teams Need From an SAP Data Migration
Finance needs proof that every balance, open item and asset arrived intact and in the right place. A migration can load every record without an error and still post a balance to the wrong profit center or carry an open item at the wrong amount, so finance should set its own acceptance checks before the first mock load.
| Finance data | What has to agree | Typical check |
|---|---|---|
| Chart of accounts | Every legacy account maps to one S/4HANA account | Mapping table signed off by the controller before extraction |
| General ledger balances | Trial balance by company code, account and period | Legacy and S/4HANA trial balances compared at one cut-off |
| Open receivables | Customer balances and aging | Totals per customer and per aging bucket |
| Open payables | Vendor balances, aging and bank details | Totals per vendor; bank details checked against the source |
| Fixed assets | Acquisition value and accumulated depreciation | Totals per asset class and company code |
| Customers and vendors | One record per real business partner | Duplicate check before the load, counts and key fields after |
Tip: extract balances and open items at the same cut-off time. Most balance differences that appear in a mock load come from data taken at different moments, not from the tool.
Agree the go or no-go criteria with the controller before the cutover weekend: which differences are acceptable, by amount and by account, and who signs off. Then run the same checks after every rehearsal, not once at the end. For how the same discipline applies to reconciliations after go-live, see automated account reconciliation.
Where AI Helps in SAP Data Migration, and Where It Does Not
AI helps a migration most where people read and compare: profiling messy source data, proposing mappings for a person to confirm, and explaining why two balances differ. It should not decide whether data passes, and it should not load data by driving screens. The load belongs in SAP's tools, and pass or fail belongs to deterministic checks that give the same answer every time.
| Task | Can AI help? | How to use it |
|---|---|---|
| Profiling legacy data | Yes | Find duplicates, odd formats and missing fields, then fix them in the source |
| Proposing field and value mappings | Yes, with review | Treat each proposal as a draft for the data owner to confirm |
| Loading data into S/4HANA | No | Use the Migration Cockpit, SUM or SAP LT |
| Deciding whether a balance agrees | No | Use a fixed comparison with an agreed tolerance |
| Explaining reconciliation differences | Yes | Group differences by likely cause so the team fixes the cause, not each record |
| Reading legacy documents for missing values | Yes, with review | Store what the model read, and check it against the source |
For the wider risks of connecting older finance systems to new ones, see legacy accounting system integration.
How engini Helps Finance Teams Around an SAP Migration
engini does not migrate data into S/4HANA. It helps before, during and after the load, wherever S/4HANA has to be checked against other systems or exchange data with them.
- Reconciliation after every mock load. A workflow in Workflow Studio, engini's visual builder, reads records from S/4HANA through the OData services your SAP administrator selects, reads the legacy extract from a database or a CSV file, compares the two, and writes each difference into an engini Table for the finance team. Each run stays in the workflow's run history, so you can compare one rehearsal with the next.
- The legacy side, wherever it sits. Databases such as SQL Server, Oracle Database and IBM DB2, and file drops in local folders and network shares, through the on-prem agent, which opens only outbound connections, so you open no inbound ports. Extracts can also arrive over SFTP.
- A read-only agent for checking. From the SDK or REST API, give a reconciliation agent a toolset that allows only reads on the S/4HANA connection. engini's server refuses any call outside it, so the agent can compare and explain but cannot change a record.
- Judgment where it helps. An AI agent step can group reconciliation differences by likely cause, such as a wrong account mapping or a different cut-off, and the finance team decides what to fix.
- The interfaces around S/4HANA. Reconnect the CRM, the online store, bank and payment files and internal databases to S/4HANA. Every integration runs both ways, so invoices and payment status can flow back to Salesforce or HubSpot. See our Salesforce and SAP integration guide.
- 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.
What engini does not do: it does not load data into S/4HANA, it has no direct connection to SAP ECC, and SAP's IDoc and RFC interfaces are not documented for its SAP connection, so read the legacy side from extracts or a staging database. For finance processes beyond the migration, see engini for finance.
When you do not need engini: if all your data comes from one SAP system that direct transfer or SUM covers, no system outside SAP exchanges data with S/4HANA, and SAP's post-processing apps or Syniti's reconcile step give finance the checks it needs, SAP's own tools may be all you need.
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 are SAP data migration tools?
SAP data migration tools are the SAP products that move data into SAP S/4HANA: the Migration Cockpit, the Software Update Manager, SAP Landscape Transformation and SAP Advanced Data Migration and Management by Syniti. Each fits a different transition approach.
Which SAP data migration tool should I use?
Use the tool that matches your transition approach. The Migration Cockpit fits a new implementation, the Software Update Manager fits a system conversion, and SAP LT fits a selective data transition; Syniti's product adds orchestration for large programs.
Is the SAP S/4HANA Migration Cockpit free?
Yes, the Migration Cockpit is embedded in SAP S/4HANA at no additional cost. You open it from the Migrate Your Data app and load data through staging tables or directly from an SAP ERP system.
What is SAP Advanced Data Migration?
SAP Advanced Data Migration and Management by Syniti is an SAP Solution Extension that orchestrates migration work. It covers extraction, profiling, mapping, enrichment, test loads, loading and reconciliation, alongside SAP's native ETL tools rather than replacing them.
Can AI agents migrate data into SAP S/4HANA?
AI agents should not run the load; SAP's migration tools should. AI is useful around the load: profiling source data, proposing mappings for review, and explaining reconciliation differences, while fixed checks decide pass or fail.
What is the difference between the Migration Cockpit and SUM?
The Migration Cockpit loads data into a new S/4HANA system, while the Software Update Manager converts an existing SAP ERP system to S/4HANA. The first is for a new implementation; the second is for a system conversion.
Sources
- SAP Learning: Migrating Data to SAP S/4HANA Cloud Private Edition
- SAP Learning: Describing the Customer Transition Paths to SAP S/4HANA Cloud Private Edition
- SAP Learning: Illustrating Selective Data Transition
- SAP Learning: Explaining Data Migration (SAP Business Transformation Center)
- SAP Learning: Describing the Tools of the Agent-led Toolchain
- engini docs: SAP S/4HANA
- engini docs: On Prem Agent
- engini docs: llms.txt