# Migration Phases

Migration phases are the stages used to assess readiness, prepare a cloud foundation, and move workloads into a validated operating environment.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/migration-phases

> A phased migration turns a large cloud adoption effort into manageable activities with measurable outcomes and decision points. It helps teams identify dependencies, address organizational and technical gaps, and reduce disruption while moving workloads and establishing cloud operations.

Practice exams covering Migration Phases: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner).

## 5 key aspects of Migration Phases

Migration phases connect business readiness, cloud foundations, controlled execution, and ongoing improvement through measurable outcomes and feedback.

1. **Readiness and business assessment**: Define business outcomes, inventory the application portfolio, and identify technical and organizational gaps. Use cost and dependency information to determine whether the proposed migration scope is realistic.
2. **Foundation and team mobilization**: Prepare identity, networking, security, account governance, and operational procedures before scaling migration activity. Pilot workloads help validate both the environment and the team's ability to operate it.
3. **Dependency-aware migration waves**: Group workloads into controlled batches based on dependencies, risk, and business schedules. Moving tightly coupled components together can prevent latency and connectivity problems during transition.
4. **Validated cutover and recovery**: Define acceptance tests, data synchronization requirements, downtime limits, and rollback conditions before switching production traffic. Successful replication alone does not prove that an application is ready for production.
5. **Iterative modernization and operations**: Use lessons from each wave to refine later migration plans, then optimize workloads after stabilization. Modernization is a workload-specific decision, while monitoring, security, recovery, and cost management remain ongoing responsibilities.

## Cloud services for Migration Phases

During mobilization, AWS Control Tower can establish the governed account environment that will host migrated workloads. AWS Application Migration Service supports server replication and test launches, while AWS Database Migration Service handles supported database migrations and AWS DataSync transfers file or object data. These tools address different workload components and require coordinated scheduling rather than acting as a single migration workflow. Amazon CloudWatch supplies operational signals during testing, cutover, and stabilization. Together, these services support phased execution, but business assessment, dependency analysis, acceptance decisions, and rollback planning remain team responsibilities.

- **[AWS Application Migration Service](https://blowstack.com/tools/cloud-services-hub/aws-application-migration-service)**: Supports server rehosting by replicating source servers to AWS and enabling test and cutover launches. It helps execute migration waves, but teams must still plan application validation, dependencies, and operational acceptance.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: Helps establish and govern a multi-account AWS landing zone during mobilization. It provides a foundation for account provisioning and governance controls rather than migrating application workloads itself.
- **[AWS DataSync](https://blowstack.com/tools/cloud-services-hub/aws-datasync)**: Automates data transfers between supported storage systems, including transfers from on-premises storage to AWS. Teams can use it for initial file or object data movement and subsequent transfers, with final synchronization coordinated around application writes.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Provides metrics, logs, alarms, and dashboards for testing and post-cutover monitoring. Teams can compare observed performance with acceptance criteria and detect problems during stabilization.

## Migration Phases exam questions

Real practice exam questions on Migration Phases, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A manufacturer has approved the business case for moving 30 applications to AWS. It has completed an application inventory and identified readiness gaps. The assessment found that the company does not yet have a shared AWS account structure, centralized access controls, or network connectivity for the applications. Which next step best follows the AWS migration phases?

**Correct answer:** Enter the mobilize phase and establish the shared cloud foundation needed to support application migrations.

**Explanation:** During mobilize, organizations address readiness gaps and establish a cloud foundation, commonly including account structure, identity controls, networking, logging, and security policies. This prepares the company to migrate workloads at scale.

## Practice Migration Phases in a full exam

Questions on Migration Phases in each practice exam, with every answer option and an explanation for each:

- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 1 question

## What is Migration Phases

Migration phases organize the work required to move applications, data, and operational responsibilities to the cloud. They cover more than copying servers: a successful migration also requires business justification, security controls, staff readiness, testing, and operational ownership. AWS commonly describes this journey through three phases: assess, mobilize, and migrate and modernize. These phases provide a planning structure rather than a rigid sequence that every workload must complete simultaneously.

During assess, an organization establishes why it is migrating and whether it is ready. Teams inventory workloads, identify application dependencies, examine licensing and compliance requirements, and compare current costs with projected cloud costs. They also assess skills, governance, and operating practices. Practical outputs include a business case, an initial application portfolio, readiness gaps, and measurable goals such as leaving a data center before a lease expires. A cost comparison should account for migration effort, network connectivity, support, and temporary operation of both environments.

During mobilize, teams address the gaps identified in assessment and build the foundation for migration at scale. This commonly includes a landing zone with account structure, identity controls, networking, logging, security policies, and cost allocation. Teams establish operating procedures, train staff, refine dependency information, and test their approach with initial workloads. Migration waves group applications into manageable batches, usually taking dependencies and business constraints into account. For example, an application server and its database might need to move together to avoid unacceptable network latency.

During migrate and modernize, teams execute workload migration plans, test functionality and performance, synchronize data, and perform controlled cutovers. A cutover plan should define acceptable downtime, success criteria, responsibilities, and rollback conditions. After migration, teams monitor the workload, verify backups and recovery procedures, optimize resources, and retire the old environment only after acceptance and retention requirements are satisfied. Modernization can occur during migration or later; redesigning every application before moving it is not mandatory.

The phases describe when and how migration work is organized, whereas migration strategies describe what happens to each workload. The commonly tested seven strategies are rehost, relocate, replatform, repurchase, refactor or re-architect, retain, and retire. Rehosting may support a tight exit deadline but preserve inefficient sizing or operational patterns. Refactoring can improve architectural fit but usually requires more development and testing. Retaining or retiring an application can be a valid portfolio decision rather than a failed migration.

A common misconception is that each phase ends permanently before the next begins. In practice, discoveries during a pilot or migration wave can change the business case, dependency map, or target design. Another misconception is that technical cutover completes cloud adoption: security, governance, financial management, and operations continue afterward. For exam questions, distinguish these migration phases from the AWS Cloud Adoption Framework transformation phases of envision, align, launch, and scale, which describe a broader organizational transformation journey.

## Learn Migration Phases in lessons

2 short lessons on Migration Phases in 1 certification course.

- CLF-C02: Migration Phases: the phased migration journey (Premium), https://app.blowstack.com/lessons/migration-phases-the-phased-migration-journey-clf-c02
- CLF-C02: Migration Phases vs. AWS Cloud Adoption Framework transformation phases (Premium), https://app.blowstack.com/lessons/migration-phases-vs-aws-cloud-adoption-framework-transformation-phases-clf-c02
