Migrate phase
The migrate phase focuses on moving SAP workloads at scale and ensuring that the SAP on
AWS infrastructure goes live successfully. To ensure this, the project uses IaC technologies
such as AWS CloudFormation to automate SAP provisioning. If you want to use open-source tools, you can read
about the SAP repositories built by AWS Professional Services teams that specialize in SAP
migrations, as described in the blog post Automating SAP
installation with open-source tools
The project team automates the infrastructure build and provisions the key AWS components in the cloud. You can test the newly provisioned systems and redirect interfaces to new targets while the project team assists in building the AWS infrastructure and resolving SAP-related issues. You can also plan and perform cutover activities while the project team assists in cutting over to the AWS infrastructure and handling SAP tasks, potential risks, and issues. Your data is migrated by using the tools and methods that were defined in the mobilize phase. For production systems, a mock cutover is performed, tested, and fine-tuned. Finally, detailed reporting is provided so you can evaluate critical infrastructure, key performance indicators (KPIs) for the project, and milestones. At a macro level, the migrate phase is completed in a number of waves, as described previously in the overview.
Objectives | Activities |
---|---|
|
|
Inputs |
Outputs |
|
|
The following diagram provides a simplified example of the migrate phase (in green) as part of the full migration process. It shows the SAP production systems being migrated in two waves.
For more information about this phase, read how the UK energy company Centrica migrated their multibillion
dollar enterprise
You can also read how Moderna Therapeutics used AWS for its SAP workloads