Create one or more projects for Migration Cockpit for several rollouts

[Ebba]

Hi,

I am working on an implementation project for S4/HANA Public cloud, where we have several sites and rollouts. The project is expected to take about 2 years to complete, and we will migrate their current data from ECC using migration cockpit, staging tables one by one in each rollout.

We planned to create a new project in Migration Cockpit for each rollout, considering all the upgrades that occur at regular intervals of objects and to be able to separate the data that will be migrated to each site. Is creating a new project for each rollout recommended, or should we have one migration project for all rollouts?

We have discovered that we get errors when we want to migrate extended objects (supplier, customer), as the sites have common suppliers/customers and the general data for these is in the other migration project. We get errors that say the supplier does not exist (CNV_DMC_SIN no. 619).

Thanks in advance!

BR,
Ebba

[Vincent_Zhu]

Hello Ebba,

It's not necessary to create only one migration project for all your rollouts, especially the rollouts will take 2 years to complete. The migration object templates will probably change during the 2 years, then you will have to update the templates, which makes you difficult to maintain and track the status.

So, you can create separate migration project for each rollout. And you can even create several migration projects during one rollout. The field mappings are based on project level, meaning you don't need to maintain the field mapping again within the same project. If you create a new migration project, you need to maintain the field mapping. That's the main difference.

Thanks

Vincent