With the recent trend in digital economy, customers have started focusing in building the core Domain Business capabilities and explore new innovations in this space with reduced cost of ownership.
This brings the focus to efficiently manage the IT infra structure & technology stack which is anyway not the core skill the customer team will have. Many a times customers ask Why should we invest on hardware assets, build capability in managing such assets which is not our primary business KPI. Other challenge which adds to this complexity is in infra area like hardware obsolescence, license, Data center exit, real estate etc.,
To optimize the TCO, there are multiple avenues to reach the target state by migrating the SAP workloads to public/private cloud along with optional transformation initiatives included like migrating to HANA(SoH) etc., considering end of maintenance support in 2025.In some specific scenarios customers think in this direction though their primary intention is not to migrate the systems to cloud. However some drivers like Data center exit, hardware obsolescence etc., make customer to plan for such initiatives.
One of the prime focus for any customer is, to build the strategy around this to make sure that overall process is smooth & hassle free with no Business impact.
Key success criteria in any migration project is how well the overall design methodology adapted for the migration considering the Business & technical dependencies, system sequencing or wave planning etc., This defines which SAP system falls under which specific wave considering the dependencies and how many such waves are required to migrate the system to cloud.
Refer my below link which is published at SDN on wave planning which narrates key design principles & grouping methodology to be considered during this exercise.
I hope these insights are useful, do contact us to build the strategic roadmap for such initiatives.