# Mobilize phase


 ![\[Mobilize phase in SAP migrations to AWS\]](http://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-sap-migration/images/sap-migration-mobilize.png) 

The mobilize phase focuses on refining and blueprinting your target SAP on AWS architecture, supporting the implementation of proof of concept (PoC) projects, and defining migration tooling and planning. This phase builds the foundation for the migration process. It specifies detailed, non-functional requirements, SAP on AWS architecture, landing zone, details of the migration approach, and the refined migration plan. In this phase, the majority of the migration team will be onboarded and briefed for the migration project. The preparation for the migration of SAP workloads will be finalized, to ensure a successful start to the next phase (migration).

The mobilize phase consists of these steps:

1. Plan and implement the PoC based on clearly defined customer criteria.

1. Mobilize and onboard the project team.

1. Refine and completely specify non-functional requirements for SAP on AWS workloads.

1. Map new and existing SAP workloads to a new AWS infrastructure.

1. Design SAP on AWS architecture by following the principles discussed in [SAP Lens – AWS Well-Architected Framework](https://docs.aws.amazon.com/wellarchitected/latest/sap-lens/sap-lens.html).

1. Design and build a new (or refine an existing) landing zone that’s compliant with SAP workload requirements.

1. Complete the detailed project plan.

1. Prepare the code required for AWS infrastructure provisioning and SAP initial installations.

1. Prepare and set up the required migration and conversion tools.


****  

| 
| 
| **Objectives** | **Activities** | 
| --- |--- |
|   Produce a blueprint for a detailed, future-state architecture of SAP workloads in AWS   Produce a detailed migration plan   Finalize the landing zone   Mobilize and organize migration teams in your organization, at AWS, and at the partner organization)   |   Refine detailed customer requirements   Map existing SAP workloads to AWS services   Define required tooling and integrations   Produce a detailed, future-state architecture and define transition states   Produce a detailed migration plan; define roles and responsibilities   Onboard the project team   | 
| **Inputs** | **Outputs** | 
| --- |--- |
|   Outputs from the assessment phase   Detailed requirements for DR, HA, security, key operational procedures, performance, software versions (operating systems, databases, SAP and non-SAP systems), and integrations   AWS best practices for migrating and running SAP workloads on AWS   |   Detailed migration plan and responsible, accountable, consulted, informed (RACI) matrix   Detailed requirements for DR, HA, security, separations, DevOps, performance, software versions, and similar considerations   Detailed technical approach and tooling requirements for migration   Detailed future-state SAP architecture blueprint   Landing zone   Infrastructure as code (IaC)   | 

To see how Covestro, one of the leading suppliers of premium polymers, chose AWS Professional Services to support their cloud migration and to create a platform architecture that met their needs, see the case study [Covestro uses AWS to Transform Operations and Drive Manufacturing Innovation](https://aws.amazon.com/solutions/case-studies/covestro-case-study/). Covestro moved more than 500 business applications and 1,000 servers from its data centers to an AWS landing zone.

The following illustration provides a simplified example of a typical SAP mobilization project team.

 ![\[Simplified example of an SAP project team\]](http://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-sap-migration/images/sap-migration-teams.png)