# Assess phase
<a name="assess"></a>

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

The assess phase focuses on the evaluation and discovery of your current infrastructure, processes, organizational structure, and requirements for your SAP workloads. This phase often begins as a part of the cloud provider selection process. 

The assess phase consists of these steps:

1. When you have selected AWS as a cloud provider, in the preliminary stages of your project, AWS Professional Services verifies all SAP systems and SAP landscapes that are in scope for migration. The goal is to make sure that all data points are valid and to fill in any gaps. 

1. The project team prepares a detailed inventory of integrations, batch jobs, and satellite systems that are part of the SAP system landscape, and determines the versions of operating systems, databases, and SAP and non-SAP applications. This includes all compatibility, support, licensing, and compliance requirements. It also includes technical requirements such as the current and projected size of databases, network capacity, required compute performance, and high availability (HA) and disaster recovery (DR) requirements for each application.

1. Organizational aspects are assessed. These include your SAP Center of Excellence and the technical, organizational, and project management capabilities (both in-house and partner-assisted) that would be needed to support migration efforts and to maintain regular operations in parallel with migration. This assessment also includes the operation calendar of the SAP application estate, regular maintenance procedures, backups, and security checks.

1. Business aspects, such as restricted dates, financial closings, peak trading times, and transaction periods, are taken into account. Business inputs on critical topics, such as business continuity, legal and regulatory compliance, data privacy, data residency, and security, are considered.


****  

| 
| 
| **Objectives** | **Activities** | 
| --- |--- |
|   Transfer knowledge to your teams on migrating to AWS and operating SAP workloads on AWS   Assess the current SAP architecture, and create an inventory of the current SAP system landscape and ongoing and planned projects   Define future migration and architecture objectives   Define the conceptual future-state architecture   Assess the potential infrastructure and total cost of ownership (TCO) benefits   |   Present and discuss options for migrating SAP workloads to AWS, modernization concepts, and examples   Create an inventory of the current SAP application estate and architecture, and planned customer projects   Explore migration and modernization strategies and tactics   Define the conceptual future-state architecture, and, if required, TCO calculations   Outline a landing zone (that is, a cloud foundation)   | 
| **Inputs** | **Outputs** | 
| --- |--- |
|   Presentations, workshops, and round tables   Documentation on the current SAP landscape, SAP applications, databases, operating systems, sizing, and similar technical specifications   Draft migration and architecture objectives such as recovery point objective (RPO), recovery time objective (RTO), HA and DR requirements   AWS best practices and examples   |   Presentation that focuses on SAP on AWS, including high-level migration and architectural concepts, references, and examples   Migration objectives, tactics, and strategy document   Conceptual architecture document   Draft landing zone   | 

The following illustration provides a simplified example of an SAP on AWS Discovery Workshop that is delivered as a part of the assess phase. Note the active participation of both your teams and AWS Professional Services, with separate agenda items.

 ![\[Simplified example of an SAP on AWS Discovery Workshop\]](http://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-sap-migration/images/sap-migration-discovery-workshop.png)