# Migrate phase
<a name="migrate"></a>

 ![\[Migrate phase in rehosting SAP workloads on AWS\]](http://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-sap-migration/images/sap-migration-migrate.png) 

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 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](https://aws.amazon.com/blogs/awsforsap/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** | 
| --- |--- |
|   Migrate SAP workloads to AWS   Deploy automated IaC systems   Put basic operational procedures in place   Cut over to SAP on AWS and go live   Run the SAP on AWS go-live assessment   Go live with operations   |   Run IaC systems and set up the architecture on AWS   Set up migration tools   Automate provisioning of the operating system, file systems, and databases   Migrate SAP workloads   Perform testing, defect resolution, and basic performance-tuning   Automate operational procedures such as backups, automatic scaling, and monitoring   Cut over and go live   | 
| **Inputs** | **Outputs** | 
| --- |--- |
|   Outputs from the mobilize phase   AWS best practices for migration   Migration tools   |   Report on enabled AWS services   Report on running SAP workloads on AWS   Report on open and resolved defects   Test reports   Cutover report   | 

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.

 ![\[Simplified example of go-live phases in a migration project\]](http://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-sap-migration/images/sap-migration-go-live.png) 

For more information about this phase, read how the UK energy company Centrica [migrated their multibillion dollar enterprise](https://aws.amazon.com/partners/success/centrica-capgemini/) with the assistance of AWS Professional Services, as part of their digital transformation.

You can also read how [Moderna Therapeutics used AWS for its SAP workloads](https://aws.amazon.com/solutions/case-studies/moderna-therapeutics/) to deliver mRNA drugs faster and at lower cost. Moderna received help from AWS Professional Services consultants with life sciences expertise to build a fully validated SAP environment in the AWS Cloud.