Microsoft's Cloud Adoption Framework gives a cloud migration checklist built around five steps: plan the migration, prepare workloads, execute the migration, optimize in the cloud and decommission the source. Its pages add checklists for assessment, planning, cutover, validation and rollback. This page follows Microsoft's guidance, which is written for moving workloads to Azure.
What Microsoft's Cloud Migration Checklist Covers
Microsoft's Plan your migration page lists the five steps and says it covers step one. A migration plan sets the order, timing and approach for moving workloads. Its prerequisites are a migration adoption plan and an Azure landing zone. Microsoft's migrate overview describes four stages instead: prepare, assess, deploy and release. The two pages count the stages differently.
Assess Each Workload First
Microsoft's assessment page says the assessment gives full visibility into every component, dependency and requirement before the move. For each workload, the page lists:
- Architecture: use discovery tools such as Azure Migrate, then have owners validate the findings. Microsoft warns that tools can miss undocumented dependencies.
- Performance baseline: CPU, memory, disk I/O, network throughput and response times.
- Security and identity: accounts, keys, encryption and firewall rules.
- Dependencies, compliance needs, application code, databases and ISV software compatibility.
- A risk register with owners and deadlines.
Plan the Migration
The plan page lists these checks.
- Review your team's Azure and cutover experience, and bring in Microsoft or a partner if skills are missing.
- Choose a data path: ExpressRoute, VPN, Azure Data Box for large offline transfers, or public internet for nonsensitive data only.
- Map dependencies, then group workloads that share databases, APIs or authentication.
- Start with simpler, lower-risk workloads, and migrate nonproduction environments before production.
- Set start and end dates with buffer time, and avoid critical business periods.
- Choose a method per workload: downtime migration, or near-zero downtime with continuous replication.
- Define rollback, with thresholds for what counts as a failed deployment.
Use Azure Migrate With Your Cloud Migration Checklist
Microsoft's Azure Migrate overview says the service helps you decide on, plan and carry out a migration. It assesses Azure readiness and hosting cost, and supports servers, databases, web apps and virtual desktops. It also supports large offline moves with Azure Data Box. The page names the service Azure Catalyst, formerly Azure Migrate.
Plan Migration Waves for Your Cloud Migration Checklist
Microsoft's wave planning page says waves divide a large project into smaller groups of workloads that move together. Each finished wave shows performance needs and dependency problems. Microsoft says to use those lessons on the remaining workloads, and to write down what worked and what did not.
Prepare Workloads
Microsoft's prepare workloads page says workloads must be cloud-ready before migration. It says to deploy all workload components in a test environment and validate that the environment is complete before production cutover. It also says to use your Azure architecture plan and your workload assessment to guide preparation.
Execute the Cutover
Microsoft's execute migration page starts with stakeholders. Share a schedule with timing, expected service impact, responsibilities and contingency plans. Keep technical staff on call for the whole window. Hold a readiness review with every support team. Then use a change freeze on source systems. For near-zero downtime, Microsoft says do not proceed until replication lag is zero. For planned downtime, stop all writes first, migrate and validate the data, then redirect traffic.
Validate and Keep a Fallback
After cutover, Microsoft says to check data integrity with checksums or hashes, run end-to-end functional tests and monitor for 24 to 48 hours. Declare success only after application owners and business stakeholders confirm the workload works. Keep the source environment available, so you can revert DNS records and restore earlier settings if a critical issue cannot be fixed in time.
Related Guides From Us
These are our own guides, not Microsoft's. See what is cloud migration, cloud migration strategies and the 6 Rs, SharePoint Online migration checklist and top cloud migration service providers.
This Order Is Ours: A Short Checklist
This order is ours, not Microsoft's. It condenses the pages above into a short cloud migration checklist.
- Assess each workload and record its dependencies.
- Fill team skill gaps before the plan is final.
- Pick a data path and a method per workload.
- Define rollback and get written approval.
- Test in a nonproduction environment first.
- Freeze changes, cut over, then validate.
- Keep the source until the workload is stable.
What Do These Sources Not Say?
- The migrate overview counts four stages and the plan page counts five.
- The execute page does not cover decommissioning. The plan page lists it as step five.
- Microsoft's pages assume Azure. The overview calls the approach vendor-neutral, but the checklists name Azure tools.
- They give no time or cost estimates for a typical migration.
- They do not say which Azure plan or subscription type you need.
- No page we read gives one printable cloud migration checklist. The checklists sit across several articles.
Frequently Asked Questions
What are the five steps in Microsoft's migration process?
Plan migration, prepare workloads, execute migration, optimize in the cloud and decommission the source.
Should I migrate production first?
No. Microsoft says to migrate nonproduction environments before production.
How do I choose a data transfer path?
Microsoft says to use ExpressRoute when available, a VPN when it is not, and Data Box for large offline transfers.
What counts as a successful migration?
Microsoft says success is declared only after application owners and business stakeholders confirm the workload works.
Do I need a rollback plan?
Yes. Microsoft says to define what a failed deployment looks like and to test rollback steps in staging.
How long should I monitor after cutover?
Microsoft says to monitor access patterns, performance and error rates for 24 to 48 hours.
Key Takeaways
- Assess dependencies before you group workloads.
- Move nonproduction environments before production.
- Define and test rollback before cutover.
- Keep the source environment until the workload is stable.
Sources and References
Facts follow Microsoft Learn.
- Plan your migration learn.microsoft.com
- Migrate overview learn.microsoft.com
- Assess your workloads for cloud migration learn.microsoft.com
- Prepare workloads for cloud migration to Azure learn.microsoft.com
- Azure Migrate overview learn.microsoft.com
- Migration wave planning learn.microsoft.com
- Execute migration to cloud learn.microsoft.com