Deri menjelaskan mengenai proses melakukan migrasi dari SAP on-prem ke cloud. Pemaparan materi juga mencakup mengenai tahapan-tahapan migrasi, aktivitas-aktivitas prioritas dalam melakukan migrasi, serta manfaat yang didapatkan ketika seluruh tahapan migrasi ke cloud selesai dilaksanakan.

1. SAP
Migration on-Premise to Cloud
Deri Permana
27 February 2020

2. Migration on-Premise to Cloud
• Introductions
• Migration versus ImplementationTerminology
• Key Challenges
• Migration Methodology
• SAP Migration Key Activities
• Key Benefits of Cloud Services
• Next Steps
Discussion topics:

3. Migration on-Premise to Cloud
Introductions
Why?

4. Migration on-Premise to Cloud
SAP Migration versus ImplementationsTerminology
SAP Migration
• Typically ERP classic running on various database (Oracle, DB2, HANA, MAXDB, Etc.)
• Data is migrated by means of system copy (Heterogenous or Homogenous)
• Upgrade-migration or Conversion to S/4HANA is possible but not Recommend if we
used standard delivery from SAP due to long downtime Over WAN, Recommend
used LT or third Party (not free)
• Brownfield Sizing
SAP New Implementation
• Source system is Non-SAP system while target is S/4HANA
• Data from source to target is migrated by means of data conversion (download,
Cleansing and upload)
• Greenfield Sizing
SAP Re-Implementation
• Source system is running on ERP classic version while target is S/4HANA
• Data from source to target is migrated by means of data conversion (Using HANA
Migration Cockpit, third party or standard)
• Brownfield Sizing

5. Migration on-Premise to Cloud
Key Challenges
Find the cloud provider with one solution (IAS,PAS, SAAS)
The Following key challenges apply for SAP migration to cloud from on-Premise
Adopt SAP migration methodologies
• Heterogenous migration of SAP systems (OS/DB Migration)
• Homogenous migration using (VM Level, Database Backup tools, Replication)
Minimal outage window for SAP systems (NZDT)
• Standard Heterogenous migration of SAP systems requires longer downtime
• Database Size of SAP system and Network Bandwidth between on-premise and cloud
provider influence the migration time.
Choose a single cloud or go with multi cloud
• The downside to this approach is vendor lock in. Once you’ve updated your
application to work with only that one provider, moving your application to a different
provider could require just as much effort as the original cloud migration. Additionally,
having a single cloud provider might negatively impact your ability to negotiate
important terms—such as pricing and SLAs—with the cloud provider.
8
7
6
5
4
3
2
1
Application consulting
Application Managed Services
SAP standard operations (Basis)
Database services
OS services
Infrastructure operations
Hardware and setup
Data centres
9 Strategic consulting / Advisory
Technical
Services
Platform
Services
AMS &
Consulting
SAP landscapeComplexity
• Many SAP Products which are tightly coupled such as BW-ERP, ERP-CRM and ERP-PI
etc.
• Other on-going SAP Projects running together with cloud SAP migration.
• A lot of integration to legacy system (SAP or non-SAP)

6. Migration on-Premise to Cloud
Migration Methodology
1
Assessment
2
Design 3
Proof Of
Concept
4 5
Migrate Non-
Mission Critical
Systems
6
Migrate
Business Critical
systems
Post Go Live
Support
Complete study of current
condition such as :
• SAP system
landscape
• Backup and Recovery
mechanism
• SAP security
architecture
• Disaster and
Recovery Solution
• Analyze SAP satellite
system more deep
using EWA report
• Review operational
activities etc.
• Review for DB
upgrade
• Analyze SAP
Migration Approach
This phase, migration
approach will be decided
and SAP systems design
will be finalized
• Sizing
• Review parameter
and configuration
recommendation
from SAP for OS, DB
and SAP
• Backup and Recovery
approach
• Design Security
approach
• Design migration
approach for non
critical and critical
systems
This phase, SAP system
are build based on design
document.
• Build POC Environment
for critical application
and validate the
functionality
• Perform functional,
integration testing.
• Create migration
cutover plan for each
SAP instance.
• Perform BASIS test
script
• Setup and test backup
recovery
• Setup and test DR
solution.
This phase, SAP systems
for DEV and Test will be
done including:
• Freeze for any develop
and changes
• Execute migration step
• Reconfigure the new
landscape architecture
• Execute Post Migration
activities include
technical and
functional test
• Create initial backup
This phase, cutover
activities will done
including:
• Prepare cutover
checklist
• Finalize test scenario
that will be done
during cutover
• Execute migration
steps (SAP systems
downtime)
• Reconfigure the new
landscape architecture
• Execute Post Migration
activities include
technical and
functional test
• Go or no-Go decision
• Create initial backup.
This phase, the Business
critical systems has go live
and need monitored
closely :
• Collecting performance
statistic report for
baselining (3 or 6
month)
• Arrange with SAP
Global support to get
the migration
verification check

7. Migration on-Premise to Cloud
SummaryOf SAP Migration KeyActivities
• Finalize migration approach weather we choose (Heterogenous, Homogenous or fresh installation from the scratch)
• Always create migration plan for each system even the system run on non-critical or critical system.
• Always create the fallback plan in case we have to go back to on-premise system.
• Always create full Database backup include logs transaction.
• All the activities should be documented before and after the changes.
• Identify the location of SAP users , especially for SAP Users Accessing SAP systems from remote area.
• Change the connectivity from IP to hostname also include for the develop team change from IP to hostname (interfacing)
• Change the connectivity managed by DNS if possible.
• Minimize the version changes SAP, DB or OS version.
• Always create sandbox system to test the migration process, the goal is to get (bug fixing, duration etc.)

8. Migration on-Premise to Cloud
Key Benefits of Cloud Services
• Efficiency / cost reduction
By using cloud infrastructure, you don't have to spend huge amounts of money on purchasing and maintaining equipment. This drastically reduces
capex costs. You don’t have to invest in hardware, facilities, utilities, or building out a large datacentre to grow your business. You do not even need
large IT teams to handle your cloud datacentre operations, as you can enjoy the expertise of your cloud provider’s staff.
• Data Security
Cloud offers many advanced security features that guarantee that data is securely stored and handled.
• Scalability
Cloud based solutions are ideal for businesses with growing or fluctuating bandwidth demands. If your business demands increase, you can easily
increase your cloud capacity without having to invest in physical infrastructure. This level of agility can give businesses using cloud computing a real
advantage over competitors.
• Disaster and Recovery
Cloud-based services provide quick data recovery for all kinds of emergency scenarios -- from natural disasters to power outages.
• Resource and Support
Resource based on role, capabilities and responsible and with knowledge updated the new technology.
Since the customer only hold the SLA from the Cloud provider, the customer will be focused on business continuity.

9. Migration on-Premise to Cloud
Next Steps
deri.permana@yahoo.co.id
WhatsApp: +628111 01 2902
Cloud.datacomm.co.id

10. Thanks