Before you can migrate data for a specific object, you need to ensure that the following tasks are completed:
* Predecessor objects have been migrated: Some migration objects depend on other migration objects that need to be migrated first. For example, before you can migrate sales orders, you need to migrate customers, products, and pricing conditions. You can check the dependencies of migration objects in the Migration Cockpit or in the Migration Object Modeler12.
* Permission to migrate the data has been assigned: In addition to having permission to access the Migrate Your Data app, you need permission to migrate each type of data. This is because the Migration Cockpit tool uses the same APIs and technical checks that would be done if you were to create a new data value through the respective application. For example, if you need to create a new bank record in your system, you would use the application, Manage Banks - Master Data. The app would present you with several fields capturing information about the new bank to create the record in your system. Now if you need to create 1,000 banks, it wouldn't be feasible to create each through the Manage Banks - Master Data app one-by-one. Therefore, you need to have the permission to use the Manage Banks - Master Data app in order to migrate bank data using the Migration Cockpit3.
The other tasks are not mandatory before you can migrate data for a specific object. You can select different migration methods for different objects, depending on your source system and data format. You can also have multiple migration projects in progress at the same time, as long as they do not contain the same migration objects4. References = Migration Object Modeler, Migrating Data with the SAP S/4HANA Migration Cockpit, SAP S/4 HANA Data Migration Cockpit: Migrate Your Data App Guide, Migrating Data to SAP S
/4HANA Cloud, Public Edition