Best Practices for Data Migration in a Carve-Out from S/4HANA On-Prem to S/4HANA Cloud

[YannickB]

Hello SAP Community, 

I’m currently working with a customer who is performing a carve-out, moving from their legacy S/4HANA On-Premise system to S/4HANA Cloud, Public Edition. As part of this project, they are facing challenges in identifying the relevant data tables for migration and pinpointing where exactly the necessary data resides in their existing system. I’d like to reach out to this community for any best practices or lessons learned from similar carve-out scenarios.

• The new system will be based on S/4HANA Cloud, public edition, so we are focusing on a clean and efficient transition.
• The legacy system is S/4HANA On-Premise, with years of data accumulated. The customer is unsure about the best approach to identify and extract only the necessary data for migration. 

Challenges:

1. 
   1. Identifying relevant tables: The customer is unsure about which tables to migrate and how to locate the key tables in their On-Premise system.
   2. Data relevance: There’s some confusion around how to extract **only the relevant data**, without transferring unnecessary historical data.
   3. Table mapping for migration tools: Aligning On-Prem tables with SAP Migration Cockpit templates and the standard migration objects available for the Cloud edition has also proven to be challenging.

Key Questions:

• What best practices exist for identifying and mapping the critical tables in S/4HANA On-Prem for a carve-out scenario?
• Are there any efficient methodologies or tools that can help pinpoint relevant data and ensure it aligns with the S/4HANA Cloud public edition data structure?
• How do you ensure the customer extracts only the required data, avoiding clutter or excessive historical records? 

I’d appreciate any advice, strategies, or best practices that you have found effective in your own experience—particularly in scenarios where S/4HANA On-Prem is being transitioned to the public Cloud edition. We want to ensure that our data migration is as clean and efficient as possible.

Thanks in advance for your input!

Best regards,
Yannick

[Jeroen_Zijderveld]

Hi Yannick,

To make this transitions more easy we've created a set of extraction programs that pulls the data out of ECC into the Excel/XML format to is required by the data migration cockpit (DMC). These programs allow selection of the data to overcome the problem of moving all ancient data and only select the relevant, active data. 

Because the output can be uploaded into DMC without any manual adjustments this ensures a fast and repeatable data migration process.

let me know if you need more info on this,

best regards,

Jeroen

[Daphne_Mengwein]

Hello @YannickB , looks like your question was answered. Please accept or re-open if you need any more information. Thanks!