- The Migration Cockpit comes with predefined migration objects that include the target system’s checks. Current releases offer two approaches: staging tables and direct transfer from an SAP system.
- Files are no longer a separate approach. XML or CSV templates fill the staging tables.
- According to SAP Note 2287723, LSMW is not recommended for data migration to S/4HANA, and its use is the customer’s responsibility.
- Test migrations (mock migrations) usually fail because of the sequence, late cleansing, missing reconciliation, and unclear data ownership.
The Migration Cockpit: the standard
For common business objects, the Migration Cockpit provides ready-made migration objects. They range from business partner and material master to purchasing info records, stock, open purchase orders, and fixed assets. Each object contains the fields and checks that the target system requires.
As of S/4HANA 2020, you work in the Fiori app Migrate Your Data. It offers two migration approaches. Since S/4HANA 2021, the former transaction LTMC, with its own file approach, no longer accepts new projects.
| Approach | How the data gets in | Fits when | Watch out for |
|---|---|---|---|
| Staging tables, filled via template | Download the XML or CSV template per object, fill it in, and upload it | Volumes are manageable, or the business prepares the data itself | Templates have a fixed structure per object; maintain value mappings in the cockpit |
| Staging tables, filled via database tool | The data is written directly into the tables, for example with an ETL tool such as SAP Data Services | Volumes are large, and test migrations are repeated often | Document and version the transformation logic outside SAP |
| Direct transfer from an SAP system | The cockpit reads from the SAP ERP source system via an RFC connection | The legacy system is SAP ERP, and selected data is to move into a new system | Check the object scope per release; the source system needs a suitable release level |
If an object lacks a custom field, adjust it in the Migration Object Modeler (transaction LTMOM). There you can also create your own objects, for example based on a BAPI.
LSMW in S/4HANA: available, but not recommended
The Legacy System Migration Workbench was the workhorse for data migration in SAP ECC for years. It still exists in S/4HANA, but not in SAP S/4HANA Cloud Public Edition. SAP Note 2287723 states that using it for data migration is not recommended and is the customer’s responsibility.
The reason is the new data model. Many transactions and interfaces that LSMW projects relied on no longer exist in that form. Suppliers and customers are maintained as business partners, and Fiori user interfaces cannot be recorded like SAP GUI transactions.
One example is asset accounting. There, batch input only creates master records; you post the transfer values with a dedicated transaction or via a BAPI.
Where LSMW still helps:
- In the ECC legacy system, to fill in fields before the migration, flag duplicates for deletion, or correct classifications.
- In ECC systems that are not being converted yet, for mass changes and partial data loads.
If you still use it in S/4HANA for small mass changes, you bear the risk yourself. In that case, check every recording in the test system and reconcile the result.
The tools compared
| Tool | Use | Strengths | Limits |
|---|---|---|---|
| Migration Cockpit | Data migration to S/4HANA | Ready-made objects, checks of the target system, repeatable runs | Not every special field is covered; adjustments in the Migration Object Modeler take experience |
| LSMW | Cleansing and mass changes in the ECC legacy system | Quick to set up, often familiar in-house | Not recommended for data migration to S/4HANA, not available in the Public Edition |
| BAPIs and small programs | Gaps without a standard object, such as special cases or rework | Full control, easy to test | Need development, testing, and documentation |
| Specialized tools from SAP and partners | Selective data transition, consolidations | Transfer with history, selection by company code or time period | License and consulting effort; plan for it early |
For us, choosing the tool is a question per object, not a matter of principle. On request, we work with the Migration Cockpit, LSMW, and BAPIs ourselves.
Why test migrations really fail
Test migrations usually fail at four points that have little to do with the tool.
- The sequence is wrong. Purchasing info records need suppliers and materials; stock needs storage locations and valuation data. An object list with dependencies belongs at the start.
- Cleansing starts too late. Duplicate suppliers and customers often only surface when they are merged into business partners. If they only show up in a late test migration, cleansing costs weeks.
- Nobody reconciles. An error-free run does not mean that quantities and values are right. Without a reconciliation log per object, that remains an assumption.
- Data ownership is missing. Each data area needs a person in the business who sets the rules and approves the results.
Finding the right tool per object
- Check the standard object in the Migration Cockpit for your release
- Note custom fields and special logic, and plan the adjustment in the Migration Object Modeler
- For large volumes and many test migrations, fill the staging tables with a database tool
- If the legacy system is SAP ERP, consider direct transfer
- For gaps without an object, define a BAPI or a custom object, with testing and documentation
- Plan cleansing in the legacy system, where LSMW remains a good tool
- Define a reconciliation log per object before the first run starts
How we help
We work with you to define the object list, sequence, and cleansing rules, and we run the test migrations through to the dress rehearsal. The first step is an analysis of the migration objects.