SAP S4 HANA Migration Approach to Cloud
Migrating from On-Premise to SAP S/4 HANA cloud offers many benefits to organizations, mostly due to adopting SAP HANA. This in-memory database accelerates queries and enables powerful analytics using massive external and internal data pools. The common thread through many of these advantages is the increased speed compared to traditional ERP systems based on conventional databases.
Another set of benefits derives from the multi-tenancy of SAP S/4HANA Cloud. It is SaaS based and enables deep integration with various cloud-based technologies like SAP Business Network.
Migration Approach – 1
Database Replication
Process
Actual Migration Technical Steps – Approach 1
(Database Replication Process- Perform Actual Migration, SIT & UAT)
Step 1 – Local Database copy & replication
- Install ABAP AS in MS Azure
- Create a back-up of SAP On-Premise Database & migrate the copy of the back-up into MS Azure
- Connect the back-up with the ABAP AS installed in Azure
- Perform pre & post migration activities and enable Replication between the 2 databases sitting in On-Premise & Azure
- Connect all available interfaces with the new SAP ABAP AS in MS Azure.
Replication will help to move all delta developments done in On-premise SAP Dev. system to move to MS Azure
Migration Approach – 1
Database Replication
Process
Actual Migration Technical Steps – Approach 1
(Database Replication Process- Perform Actual Migration, SIT & UAT)
Step 2 – Perform Data Validation Testing & System Handover to Customer
- Perform Data Validation testing & System Integration testing to test connectivity,data & interfaces
- Once testing is confirmed, a downtime of 4 hours during o-business hours is needed to configure the transport routes
- Stop replication process & decommission the On-Premise SAP ABAP AS system & activate the MS AZURE SAP ABAP landscape during o-business hours
- Perform MS Azure SAP application handover to customer for carrying out their developments
Migration Approach – 2
“Lift & Shift”
Process of Database
Actual Migration Technical Steps- Approach 2
(“Lift & Shift” Process- Perform Actual Migration, SIT & UAT)
Step 1 – Local Database copy & replication
- Install ABAP AS in MS Azure
- Create a back-up of SAP On-Premise Database & retain
- Downtime of 10 hours during off-business hours is needed to “Lift” the database from On-Premise & “Shift” it to MS Azure
- Establish connectivity between the ABAP AS & migrated Database in Azure
- Perform pre & post migration activities in MS Azure
- Connect all available interfaces with the new SAP ABAP AS in MS Azure followed by testing & system handover to customer
Pros & Cons of
Database Replication Process
& “Lift & Shift” Process
Database Replication Process
Pros
- The most recommended way in the industry for its safety measures
- Data management & downtime under consultant’s controls
- This will ensure business continuity during any kind of network or infrastructure disruption in the cloud
Cons
- Time Taking Process as many activities need to be done before the migration taking place
- Little expensive as compared to other approach
“Lift & Shift” Process
Pros
- Simple & quick
- Optimized cost as quicker process
- The database migration per system can happen overnight
Cons
- Too much dependency on network latency & infrastructures provided by the vendors
- Can stuck due to unavailability of vendor or network & business disruption can take place
- This is a network & cloud infra-structure dependent process & any network outage can stop the process completely thus causing business disruption