In this video from the SAP PRESS Book Club Q&A with Frank Finkbohner and Boris Rubarth, learn who should be involved in an SAP S/4HANA migration project.
What team members would be involved in the migration? What would their roles be, and if I'm going to put together a team that's going to do this, who would they be?
That depends on the greenfield and the brownfield approach. So, for the greenfield approach, the first thing is that you need to have someone who is familiar with data migration. So you need an owner, let's say a manager normally, or someone who's managing the data migration. He needs to know what he is doing and what tasks you need to execute and what are the most traps you can fall into for the data migration. He has to organize the complete data.
Then the next thing is you need to have some people running the data migration, so you need to have the people doing the extraction on the legacy system side and you need to have the the people who are doing the data run on the target side. But this is not all the things. You need to have the people which know the old system; so that means you need to have the people who are normally entering a sales order in the old system, or something else. You need to have them tell you for example, if you have the purchasing organizations or you have a purchaser that is within the legacy system, 1000-something, then it needs to be mapped to a new key then in the SAP S/4HANA system (or the target system). You need to have someone who is mapping the values.
Don't forget the IT people; you need to have someone in the project that is stopping the backup or doing all the other technical stuff that is needed to run both the legacy system extraction and the target system data load. Nobody else but the people who are doing the data migration should be on the system in the time the data migration runs, just to not break up any things there with people entering sales orders, etc. It seems like a total group effort all the way from IT up.