SAP on AWS migration overview - AWS Prescriptive Guidance

SAP on AWS migration overview

The AWS migration approach for SAP workloads consists of four phases: assess, mobilize, migrate, and optimize. The methodology has been tailored to meet AWS customers’ needs and contains specific actions with predefined inputs and outputs. The following diagram illustrates these phases, which are discussed in detail in subsequent sections.

        AWS migration phases for SAP workloads

Targeted business outcomes

By working back from your specific requirements, and by customizing the methodology, you can refine the migration strategy, business case, scope, sequencing of SAP workloads, and scheduling of the work that is required in order to successfully complete your SAP migration objectives.

We recommend using automation and infrastructure as code (IaC) for SAP deployments on AWS to enable the requisite speed and consistency to support a mass migration at scale. The latest tools and techniques are described in technical detail in the documents and blog posts listed in the Resources section. AWS is consistently advancing and improving its services, techniques, and methodologies to offer you more benefits and options for meeting your business objectives, so we recommend that you always check the AWS website for the latest information.

As you migrate your SAP workloads, you should also work closely with your non-SAP migration teams to align the migration of applications that are integrated into SAP, and to minimize downtime and potential business disruption. Treat each cluster of coupled applications as a project with dedicated teams. You can divide each cluster of SAP applications into sequential waves, so each cluster can be delivered with a high degree of parallelism, as discussed in the next section. This approach helps you meet your migration schedule and ensures that time to value is minimal, your business case is maximized, and you can gain benefits as early as possible. The objective is to make your business more effective by increasing agility, availability, and resilience while reducing the costs of both operations and infrastructure. Moving your SAP workloads to the cloud also enables you to innovate, drive your digital S/4HANA transformation, and enable data analytics. The following diagram illustrates these business outcomes.

          Targeted business outcomes for SAP migrations

For more information, find out how Engie used AWS Professional Services and AWS Partners in their SAP migration, as part of a wider digital SAP S/4HANA transformation of their financial processes.

Parallel migration waves

If you have a large and highly complex SAP application estate, AWS often proposes a migration that is split into distinct waves and coordinated with separate migration teams. The goal is to maintain the acceleration, momentum, and consistency of the migration effort while concurrently keeping each wave a manageable size from a resource and complexity perspective. The following chart illustrates a highly parallelized migration phase that is based on the geographical clustering of SAP workloads.

          Parallel migration waves in SAP migrations

You can fine-tune this approach by factoring in your business objectives, worldwide and business division operating calendars, business cycle, the state of your current infrastructure, and the availability and capacity of your own and AWS Partner resources.