Implementing a new ERP system involves more than simply installing and configuring the software. Existing business data must also be transferred reliably to the new system environment. Migrating customers, suppliers, materials, inventory, and open business transactions presents companies with both organizational and technical challenges.
The SAP Migration Cockpit supports structured data migration to SAP S/4HANA. Using predefined migration objects, companies can prepare, map, validate, and transfer their data to the target system. The tool plays a particularly important role when implementing SAP Cloud ERP.
But how does the SAP S/4HANA Migration Cockpit work? What are the differences between staging tables and direct transfer? Which permissions are required, and how can common migration errors be avoided?
This article explains the key features and provides a step-by-step guide and practical example to help companies understand what matters when migrating data to SAP S/4HANA.
SAP Migration Cockpit at a Glance
The SAP Migration Cockpit is an integrated SAP S/4HANA tool designed for the initial migration of selected business data. It is accessed through the SAP Fiori app “Migrate Your Data” and supports two main migration approaches: migration using staging tables and direct transfer from supported SAP source systems.
Predefined migration objects, data mapping, simulations, and error analysis functions enable a structured data transfer. However, the tool does not replace business data cleansing or a complete system conversion.

Table of Contents
- What Is the SAP Migration Cockpit?
- What Role Does SAP Migration Cockpit Play in SAP Cloud ERP?
- What Data Can Be Migrated with SAP Migration Cockpit?
- How Does the SAP Migration Cockpit Work?
- SAP Migration Cockpit: Step-by-Step Guide to Data Migration
- SAP Migration Cockpit Roles: Which Roles and Authorizations Are Required?
- SAP Master Data Migration: What Should Companies Consider?
- Practical Example: Data Migration with SAP Migration Cockpit
- SAP Migration Cockpit: Common Errors and Solutions
- SAP Migration Cockpit: Benefits and Limitations at a Glance
- Best Practices for Successful SAP Data Migration
- What Effort and Costs Are Involved in SAP Data Migration?
- Conclusion: Using SAP Migration Cockpit for Structured Data Migration
- FAQs About SAP Migration Cockpit
What Is the SAP Migration Cockpit?
The SAP Migration Cockpit is an SAP application used to transfer selected business data from existing SAP or non-SAP systems to SAP S/4HANA.
It primarily supports companies during the initial data migration when implementing a new ERP system. SAP provides standardized migration objects that define the relevant data structures and processing steps for different business areas.
Instead of developing individual import programs for every dataset, companies can use supported standard migration procedures. The application enables users to prepare source data, map values, simulate migrations, and monitor processing results.
In current SAP S/4HANA systems, the tool is accessed through the SAP Fiori app “Migrate Your Data – Migration Cockpit” (app ID F3473). Migration teams can use this application to manage projects, select migration objects, and monitor the status of data transfers.
The term SAP Data Migration Cockpit is often used as a synonym. It generally refers to the SAP S/4HANA Migration Cockpit rather than a separate product.
SAP Migration Cockpit vs. LTMC and LSMW: What Are the Differences?
When researching SAP data migration, companies frequently encounter the terms LSMW, LTMC, and LTMOM.
LSMW (Legacy System Migration Workbench) originates from older SAP ERP environments. SAP does not recommend using it for data migration to SAP S/4HANA, as older transfer technologies are not necessarily compatible with the new data structures.
LTMC was the previous entry point for the SAP S/4HANA Migration Cockpit. In current releases, this user interface has been replaced by the SAP Fiori app “Migrate Your Data”.
LTMOM refers to the SAP S/4HANA Migration Object Modeler. This tool allows supported migration objects to be adapted within the available extension options. In SAP S/4HANA Private Edition or on-premise environments, transaction LTMOM can be used for this purpose. In the Public Edition, corresponding modeling applications are available.
What Role Does SAP Migration Cockpit Play in SAP Cloud ERP?
When implementing SAP Cloud ERP, companies must determine which data from existing ERP systems or other applications should be transferred to the new environment.
Simply copying existing information is not sufficient. The data must match the configuration, organizational structures, and intended business processes of the target system.
The SAP Migration Cockpit supports this initial data migration. It is particularly relevant for new implementations in which a new SAP system must be populated with the required business data.
In SAP Cloud ERP Public Edition, technically known as SAP S/4HANA Cloud Public Edition, migration is performed using SAP-supported procedures and migration objects. In SAP Cloud ERP Private or SAP S/4HANA On-Premise, the available objects, extension options, and technical requirements may differ.
An important distinction is the difference between a new implementation and a system conversion. While a new implementation involves transferring selected data into a newly configured target system, a system conversion follows a different technical transformation approach.
The Migration Cockpit does not replace a system conversion.
We explain the differences between Greenfield, Brownfield, and Selective Data Transition in our article S/4 Transition: Brownfield vs. Greenfield vs. SDT.
What Data Can Be Migrated with SAP Migration Cockpit?
The SAP Migration Cockpit supports the migration of different types of business data. The specific information that can be transferred depends on the SAP release and the available migration objects.
Typical data categories include master data, selected inventory data, balances, and open business transactions.
Examples include business partners, customers, suppliers, material master data, inventory, and certain open financial items.
What Are SAP Migration Objects?
Migration objects form the technical foundation of data migration.
A migration object defines the data structures and processing rules required for a specific business data area. SAP provides predefined objects for this purpose.
Dependencies often exist between different objects. For example, certain master data must already be available before related business transactions can be successfully transferred.
The migration sequence is therefore important and should be determined based on the documented object dependencies.
Not all historical data can be transferred using the Migration Cockpit. The tool primarily focuses on the data required for the initial operation of the target system and does not support the complete transfer of all historical transaction data.
Companies should therefore decide early which data is required for go-live and which information may continue to be provided through a legacy system or an archiving solution.
SAP documents the currently available objects in its Migration Object Overview.
How Does the SAP Migration Cockpit Work?
The SAP S/4HANA Migration Cockpit supports two main approaches to data migration: migration using staging tables and direct transfer from supported SAP source systems.
Both approaches use predefined migration objects. However, they differ in how the source data is provided.
Data Migration Using Staging Tables
With staging-based migration, source data is first transferred into designated intermediate tables.
These staging tables are generated based on the selected migration objects and provide the technical foundation for the subsequent transfer to the target system.
Different options are available for populating the tables.
For example, companies can use XML templates provided by SAP. Depending on the product version and migration approach, additional supported file formats may be available. The files are populated with the required data and then uploaded through the Migration Cockpit.
Alternatively, the staging tables can be populated using suitable data transfer tools, such as SAP Data Services, provided the necessary technical requirements are met.
This approach is particularly suitable for heterogeneous system landscapes where information from multiple source systems must be consolidated.
For example, a company might prepare product information from an existing ERP system and additional data from another application before transferring it to SAP Cloud ERP.
However, staging tables do not replace business data cleansing. The information must still be sufficiently validated and aligned with the required target structures before processing.
Direct Transfer from an SAP System
With direct transfer, the SAP Migration Cockpit connects the target system to a supported SAP source system.
The relevant data is identified and prepared for migration using the available migration objects and selection criteria.
This approach can be useful when a suitable SAP source landscape already exists.
One advantage is that not all source data must first be manually transferred into migration template files.
However, direct transfer does not mean that data can automatically be migrated from any SAP system.
Supported source systems, migration objects, and technical requirements are limited. Depending on the scenario, communication connections must be configured and the necessary authorizations must be provided.
Data quality, mapping, and business validation also remain essential components of direct transfer.
Staging Tables vs. Direct Transfer
| Criterion | Staging Tables | Direct Transfer |
|---|---|---|
| Data source | SAP and non-SAP systems | Supported SAP source systems |
| Data provision | Template files or data transfer tools | Direct connection to the source system |
| Intermediate storage | Central element of the approach | Optional, depending on the scenario |
| Typical use case | Heterogeneous data sources | Supported SAP-to-SAP migration |
| Data mapping | Required mappings must be maintained | Required mappings must be maintained |
| Requirements | Suitable migration objects and data formats | Additional supported source systems and connections |
The most suitable approach depends on the existing system landscape and specific migration requirements.
The key consideration is whether the data can be transferred reliably and transparently using the supported tools.
SAP Migration Cockpit: Step-by-Step Guide to Data Migration
Successful data migration begins long before the actual import. The following steps illustrate the typical process of an initial data migration to SAP Cloud ERP.
Step 1 – Define the Data Scope and Migration Strategy
First, companies must determine which data is required for productive operations.
This may include business partners, material master data, inventory, and selected open business transactions.
At the same time, it should be decided which historical information will not be transferred to the new system.
The relevant migration objects and their business dependencies must then be reviewed.
Decisions regarding the migration scope should be made together with the responsible business departments.
Step 2 – Analyze and Cleanse Source Data
The next step involves examining the existing datasets.
Common issues include duplicate business partners, outdated addresses, inconsistent numbering systems, and missing mandatory information.
Such errors should be identified and corrected before the data transfer whenever possible.
It is important to distinguish between technical data preparation and business data cleansing.
IT teams can extract data and adapt formats, for example. However, the business departments must determine whether information is still required and whether it is factually correct.
Step 3 – Create a Migration Project in SAP Fiori
After preparation, the “Migrate Your Data” application is opened through the SAP Fiori Launchpad.
A migration project is created, and the appropriate transfer approach is selected.
The required migration objects are then added.
Depending on the approach, further settings may be necessary, such as connecting to a supported source system or preparing staging tables.
The specifications for the particular SAP system landscape must also be taken into account.
Step 4 – Provide the Source Data
In staging-based migration, the data is provided in the required structure.
SAP migration template files can be used for this purpose.
The source data must be transferred into the appropriate fields, taking mandatory information, data types, and formatting requirements into account.
The files are then uploaded, and the data is made available in the staging tables.
With direct transfer, the data is selected through the supported SAP source system instead.
Step 5 – Complete Data Mapping Tasks
Data mapping is one of the most important steps in the SAP Data Migration Cockpit.
During this step, values from the source system are assigned to the corresponding target values.
This is necessary, for example, when payment terms, organizational units, or other identifiers are named differently in the legacy system and the target system.
The Migration Cockpit supports functions such as value mapping and fixed-value mapping.
Value mapping assigns source values to their corresponding target values. Fixed values can be used to define specific predefined target values.
Mapping rules must be carefully reviewed because incorrect assignments can negatively affect subsequent business processes.
Step 6 – Simulate the Data Migration
Before transferring the data, the migration can be simulated.
The SAP Migration Cockpit checks the intended processing without creating business data in the target system.
During the simulation, missing mandatory fields, invalid values, or unresolved dependencies can be identified.
If errors occur, the affected datasets or mapping rules must be corrected.
The simulation should then be repeated.
A successful simulation reduces technical uncertainty but does not replace subsequent business validation.
Step 7 – Migrate Data and Verify the Results
Once preparation is complete, the actual data migration can be started.
The Migration Cockpit transfers the data to the SAP S/4HANA target system using the selected migration objects.
Progress and processing results can be monitored using the available monitoring functions.
After completion, the expected and successfully migrated datasets should be compared.
The responsible business departments must also verify that the migrated data is correct and can be used in the intended business processes.
Step 8 – Prepare Test Migrations and Go-Live
Before go-live, the complete migration process should be tested several times under conditions that are as realistic as possible.
Data volumes, processing times, object dependencies, and required approvals should all be reviewed.
An agreed cutover plan defines when data processing in the legacy system ends and when the final migration begins.
Procedures for handling last-minute changes and technical errors must also be established.
SAP Cloud ALM may be relevant for overall project and test management. However, the actual data migration continues to be performed using the Migration Cockpit.
SAP Migration Cockpit Roles: Which Roles and Authorizations Are Required?
Appropriate roles and authorizations are required to access the SAP Migration Cockpit and perform data migration activities.
It is important to distinguish between accessing the application, migrating specific business objects, and modifying migration objects.
Authorizations in SAP Cloud ERP Public Edition
The business role SAP_BR_CONFIG_EXPERT_DATA_MIG is particularly relevant for using the “Migrate Your Data” application.
This role represents “Configuration Expert – Data Migration”.
Users also need authorizations for the respective migration objects and business areas.
General access to the Migration Cockpit does not automatically mean that users are authorized to migrate all available data objects.
Additional roles may be required to use the Migration Object Modeler.
For staging-based migration, SAP identifies the business role SAP_BR_ADMINISTRATOR, for example. For corresponding modeling functions in the direct transfer approach, the role SAP_BR_BPC_EXPERT is relevant.
The specific authorizations must be checked against the SAP release and migration scenario being used.
Roles in SAP S/4HANA Private Edition and On-Premise
Additional backend authorizations may be required in SAP Cloud ERP Private and SAP S/4HANA On-Premise.
| SAP Role | Typical Function |
|---|---|
SAP_BR_CONFIG_EXPERT_DATA_MIG | Access to the SAP Fiori application |
SAP_CA_DMC_MC_USER | Performing migration tasks in the backend |
SAP_CA_DMC_MC_DEVELOPER | Using the Migration Object Modeler (LTMOM) |
For direct transfer, additional authorizations may be required for technical users in the source system.
Not every role is needed in every migration scenario. Companies should therefore assign permissions according to actual responsibilities.
Our article on Authorization Concepts in SAP Cloud ERP Public provides further information about the general authorization model.
SAP Master Data Migration: What Should Companies Consider?
SAP master data migration is a central component of many ERP implementations.
Master data is used across numerous business processes and influences purchasing, sales, inventory management, production, and finance.
Incorrect data can therefore cause problems even after a technically successful migration.
Migrating Business Partners, Customers, and Suppliers
The business partner concept plays a central role in SAP S/4HANA.
Existing customer and supplier information must be transferred to the designated data structures.
Business partner roles, organizational assignments, and required mandatory information must be considered.
Duplicate or outdated business partners should be cleansed before migration whenever possible.
Migrating Material Master Data and Inventory
For manufacturing and trading companies, migrating material master data is particularly important.
In addition to basic material information, units of measure, material groups, valuation data, and organizational assignments may be relevant.
When multiple source systems are involved, different numbering systems or classifications may need to be harmonized.
Dependencies between material master data and inventory must also be considered when determining the migration sequence.
Reconciling Financial Data
Depending on the supported migration object, open items or certain balances may be transferred.
The organizational and accounting structures of the target system must be considered.
After migration, appropriate reconciliations must be performed to ensure that the financial data is traceable and accurate.
Further information about financial processes is available on our SAP ERP Cloud Financials page.
Practical Example: Data Migration with SAP Migration Cockpit
A medium-sized manufacturing company is planning to implement SAP Cloud ERP.
Its existing ERP solution contains customer and supplier records, material master data, and inventory information. Over the years, different numbering systems have been introduced, and some records contain incomplete information.
The following simplified, fictional example shows how staging-based data migration could be performed.
Data Preparation and Mapping
First, the existing datasets are analyzed and cleansed.
The migration team then checks which migration objects are available in the target system and which data structures are required.
The prepared information is transferred into the designated migration templates.
Next, certain values from the source system must be assigned to their corresponding target values.
The following table illustrates typical mapping tasks. The identifiers are examples only.
| Data Area | Source Value | Example Target Value | Validation |
|---|---|---|---|
| Payment terms | D30 | Z030 | Is the payment term available and functionally appropriate? |
| Plant | 01 | 1000 | Is the target plant configured correctly? |
| Material group | OLD_ELECTRONICS | ELECTRONICS | Does the mapping match the target classification? |
| Business partner | Duplicate supplier records | Cleansed business partner | Are all required roles and data available? |
When mapping payment terms, for example, the team must verify which target value corresponds to the identifier used in the legacy system.
A similar name is not sufficient. The payment terms must also be equivalent from a business perspective.
Mapping rules are therefore reviewed together with the responsible business departments.
Simulation and Data Transfer
Once the data has been provided, the migration is simulated.
In this example, the system identifies missing mandatory information and an invalid mapping assignment.
The migration team analyzes the messages, corrects the affected data, and runs the simulation again.
The data is then migrated into the test system.
Business departments verify that business partners and materials have been created correctly and can be used in the intended business processes.
Only after successful testing and the necessary approvals is the production migration prepared.
The example illustrates that the value of the SAP Migration Cockpit goes beyond importing data. It lies in the combination of structured processing, mapping, validation, and quality assurance.
SAP Migration Cockpit: Common Errors and Solutions
Errors can occur during data migration even with careful preparation.
The SAP Migration Cockpit provides messages and monitoring functions that help identify and analyze problems.
The following table outlines common causes and recommended corrective actions.
| Error | Possible Cause | Recommended Solution |
|---|---|---|
| Migration file is rejected | Invalid format or modified template structure | Check the SAP template and file format |
| Mandatory field is missing | Incomplete source data | Complete the affected data |
| Mapping task remains open | Source value has no valid target assignment | Complete the mapping |
| Record cannot be migrated | Dependent master data is missing | Check object dependencies and migration sequence |
| Invalid target value | Missing configuration or invalid mapping | Verify target configuration and mapping |
| SAP Fiori app is not visible | Missing role or access prerequisite | Check roles and app availability |
| Migrated data is functionally incorrect | Incorrect assignment or insufficient validation | Perform business validation and apply an appropriate correction |
Correcting Incorrect Data with Correction Files
For certain staging-based migration scenarios, SAP provides correction files.
If errors occur during simulation or migration, affected migration object instances with an error status can be made available in a correction file.
The file can be downloaded, modified, and uploaded again.
This means that companies do not necessarily need to reprocess all the data originally provided.
The exact options depend on the migration approach and the status of the affected records. Data that has already been successfully migrated cannot be modified arbitrarily through the Migration Cockpit.
SAP describes the procedure in its documentation on correction files.
Analyzing Migration Errors Systematically
A structured troubleshooting process begins by assigning each error message to the affected migration object and dataset.
The next step is to determine whether the cause lies in the source data, mapping, target configuration, or missing authorizations.
This distinction is important because different errors require different corrective measures.
After applying a correction, the affected processing step should be checked again. In larger projects, recurring error causes should also be documented.
SAP Migration Cockpit: Benefits and Limitations at a Glance
The SAP Migration Cockpit provides companies with a standardized foundation for initial data migration to SAP S/4HANA.
One major advantage is the availability of predefined SAP migration objects. For supported data areas, companies do not need to develop all import logic individually.
The guided processing steps offer further benefits. Data provision, mapping, simulation, and migration can be performed within one integrated tool. Monitoring functions also support the analysis of technical processing results.
However, the Migration Cockpit has clear limitations.
Not all data structures and business transactions are supported by standard migration objects. Individual requirements may involve additional preparation, extensions, or supplementary tools.
Furthermore, the Migration Cockpit is primarily designed for initial data migration. Other suitable data management and integration methods must be evaluated for continuous synchronization between systems or regular changes to existing business data.
Companies should therefore clarify at an early stage which requirements can be covered by the standard tool and which data requires additional solutions.
Best Practices for Successful SAP Data Migration
Successful data migration begins with clearly defined responsibilities and an early analysis of existing data.
Before migration, companies should determine which information is needed, which data must be cleansed, and which business dependencies exist.
Repeated test migrations using representative datasets help identify technical issues, incorrect mappings, and unrealistic schedules at an early stage.
The results should be validated not only from a technical perspective but also by the responsible business departments.
For go-live, an agreed cutover plan should document the migration sequence, responsibilities, required approvals, and procedures for handling errors.
The key is to treat data migration not as an isolated technical task but as an integral part of the entire ERP implementation project.
What Effort and Costs Are Involved in SAP Data Migration?
The effort required for data migration depends heavily on the existing system landscape.
A relatively straightforward migration of standardized master data from a consistent source system differs significantly from a migration involving several legacy systems and complex data structures.
The SAP Migration Cockpit can reduce the need for individually developed import programs through its standardized functions. However, this does not mean that data migration itself is free of charge or requires no additional effort.
Project costs arise primarily from data analysis, cleansing, technical preparation, test migrations, and business quality assurance. Complex requirements may involve additional tools or external services.
Companies should therefore not assess the effort solely based on the number of records to be migrated. Data quality, object dependencies, and necessary transformation rules are equally important.
An early test migration using representative datasets can help estimate the required effort more realistically.
Conclusion: Using SAP Migration Cockpit for Structured Data Migration
The SAP Migration Cockpit is an important tool for the initial migration of selected business data to SAP S/4HANA and SAP Cloud ERP.
With staging tables, direct transfer, predefined migration objects, and functions for mapping, simulation, and error analysis, it supports companies throughout essential stages of data migration.
However, successful implementation depends on more than technical data transfer. High data quality, clear responsibilities, and repeatable testing procedures are essential.
Companies should therefore consider the SAP Migration Cockpit as part of a comprehensive migration strategy.
A data migration process that is planned early and validated from a business perspective provides an important foundation for a reliable SAP Cloud ERP go-live.
FAQs About SAP Migration Cockpit
What Is SAP Migration Cockpit in Simple Terms?
The SAP Migration Cockpit is an SAP tool for the initial migration of selected business data to SAP S/4HANA. It uses predefined migration objects and supports activities such as data mapping, simulation, and monitoring migration progress.
How Do You Open the SAP S/4HANA Migration Cockpit?
In current SAP S/4HANA systems, users access the tool through the SAP Fiori app “Migrate Your Data – Migration Cockpit”. The appropriate user roles and authorizations are required.
Where Can I Find SAP Migration Cockpit Templates?
Templates for staging-based migration can be accessed or downloaded within the relevant migration project through the “Migrate Your Data” application. The supported file formats depend on the migration approach and SAP release.
What Is the Difference Between Staging Tables and Direct Transfer?
With staging-based migration, data is first provided in intermediate tables. With direct transfer, data is selected through a connection to a supported SAP source system.
Which SAP Migration Cockpit Roles Are Required?
In SAP Cloud ERP Public Edition, the business role SAP_BR_CONFIG_EXPERT_DATA_MIG is particularly relevant. Additional authorizations are required for the respective migration objects. Further roles may be necessary for the Migration Object Modeler.
Why Is the “Migrate Your Data” App Not Visible?
One possible cause is missing roles or business catalogs. Other requirements related to the system landscape may also be relevant. Role assignments, authorizations, and app availability should therefore be checked.
Can Data from Non-SAP Systems Be Migrated?
Yes. Data from non-SAP systems can also be provided using the staging-based approach, provided it is prepared in the required format and suitable migration objects are available.
What Is the Difference Between LTMC and LTMOM?
LTMC was the previous entry point for the Migration Cockpit. Current releases use the SAP Fiori app “Migrate Your Data”. LTMOM, on the other hand, refers to the Migration Object Modeler, which supports permitted adjustments to migration objects.
How Can SAP Migration Cockpit Errors Be Resolved?
Typical errors result from missing mandatory fields, invalid values, incomplete mapping tasks, or unresolved dependencies. Error messages should be analyzed, and the affected data or settings should be corrected. Correction files are available for certain staging-based scenarios.
Can SAP Migration Cockpit Update Existing Data?
The Migration Cockpit is primarily intended for initial data migration. Other suitable functions and interfaces should be used for regular updates or continuous synchronization of existing business data.
Prepare Your SAP Data Migration with Expert Support
Are you planning a data migration as part of your SAP Cloud ERP implementation and looking for a structured approach to transferring existing business data into your new system environment? Fink IT-Solutions supports you in evaluating your current situation and planning your SAP Cloud ERP implementation.