This is in continuation to my previous blog post on “Strategy definition in SAP workload migration to cloud”.
During the journey of migrating SAP workloads to the cloud, critical factors to validate the SAP workloads migration is by waves or big-bang?
There is a need to validate the strategy in terms-of overall cost, business dependency, timelines, etc.
Following are the parameters to evaluate which will help to evaluate the decision:
- Project Cost – This is one of the critical parameters to consider in many migration projects. There is always need to optimize the cost considering dependencies. Higher the number of waves, cost of the project goes up. This parameter needs to be evaluated from overall program perspective.
- Learnings – This gives opportunity to implement previous learnings in subsequent waves. Generally higher the waves better the leanings
- Dependency on Technical and Business Systems – Good practice to start with technical systems first, so that the impact to business is minimal. This parameter needs to be considered while defining the waves. Sometimes there may be a mix of systems depending on number of systems to migrate and available window
- Ease of Decommissioning – The system needs to be available after migrating the workloads to target for specific period depending on audit, statutory guidelines etc.. This needs to be aligned while planning along with client stakeholders
- Dependency Across the Systems – Some systems will be on cloud while others will be on source data center during the period of migration. Business dependency needs to be analyzed
- Infra-related Drivers – Drivers like data center exit may force the customer to opt for big-bang approach in case the time available is too short to migrate by waves
- Testing – This effort will be higher depending on number of waves and scope for testing etc.. This needs to be considered while designing the waves. Typical question asked by test leads is “Do we have enough SMEs available to test?”
- Projects in Pipeline – Project complexity goes up with higher number of waves in terms of testing, soft and hard freeze etc.
- Non-SAP Workloads – Non-SAP workloads needs alignment with SAP systems as some systems are tightly integrated. This needs to be carefully considered while planning
I hope these insights are useful, do contact us to design optimal waves while migrating the work loads.