Migration of significantly high volumes

[SAPSupport]

What are the relevant considerations when it comes to the migration of high volumes of data, for example, a project and/or migration objects with millions of instances?

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

In a nutshell, all the necessary details can be found in the following SAP notes:

2719524 - SAP S/4HANA Migration Cockpit: XML template size limits
3065607 - Performance tips & tricks for SAP S/4HANA Migration Cockpit: Migrate Data Using Staging Tables
2733253 - FAQ for SAP S/4HANA migration cockpit. Migration approach: Transfer / Migrate data using staging tables
3066336 - Modifying Data Transfer Jobs to improve the data transfer performance of the SAP S/4HANA Migration Cockpit - Migrate Data Using Staging Tables

A few highlights from the above mentioned notes:

1. Files cannot have more than 160MB, as per SAP note 2719524. This SAP note also recommends a nice tool that can split huge files in smaller ones, under the limit of 160MB.
2. Avoid using migration projects and objects in parallel, as per SAP note 3065607.
3. Define the appropriate number of batch processes for optimal parallel processing (within the same object) as per notes 3065607 and 3066336 and 2733253 (topic #10).

Other than that, it follow the flow of a regular migration. Of course, respecting each project's proportion.