Choose a cloud migration service provider after you plan the move. AWS lists 7 migration strategies called the 7 Rs. Microsoft lists 5 migration steps. Plan, prepare, execute, optimize and decommission. Check your team skills before you hire a partner. Agree a rollback plan in writing first.
Companies hire a cloud migration service provider to move servers, applications and data to the cloud. Results depend on the plan you agree before the move starts.
Facts follow AWS Prescriptive Guidance and the Microsoft Cloud Adoption Framework. No vendor ranking appears here because neither source ranks providers.
Which Migration Strategy should You Choose?
AWS states that a migration strategy is the approach used to move a workload to the cloud. AWS lists seven strategies called the 7 Rs.
| Strategy | Meaning from AWS |
|---|---|
| Retire | Decommission or archive the application. |
| Retain | Leave the application in the source environment. |
| Rehost | Lift and shift without any change to the application. |
| Relocate | Move servers or instances to a cloud version of the platform without application changes. |
| Repurchase | Replace the application with a different product. |
| Replatform | Move with some optimization, for example a managed service. |
| Refactor | Change the architecture to use cloud native features. |
AWS states that refactoring is the most complex and costly strategy. AWS advises large migrations to rehost, relocate or replatform first and modernize afterward.
What Steps does a Cloud Migration Follow?
Microsoft describes five steps for moving workloads to Azure.
- Plan migration builds a deployment sequence from strategy.
- Prepare workloads readies every system for the move.
- Execute migration moves the workloads.
- Optimize in cloud tunes the moved workloads.
- Decommission source retires the old environment.
What should You Ask a Migration Provider?
Microsoft lists planning areas that make good questions for any provider.
- Readiness. Microsoft advises a skills assessment. It advises you to bring in Microsoft or a partner when your team lacks cloud migration experience.
- Data path. Microsoft lists ExpressRoute, VPN, Azure Data Box and the public internet as choices based on availability, security and data volume.
- Sequence. Map dependencies between workloads and group them into waves. Microsoft advises you to migrate development, staging and QA environments before production.
- Method. Use downtime migration for workloads that tolerate planned outages. Use near zero downtime migration for critical workloads.
- Rollback. Microsoft states that you should set rollback criteria before any migration. Test the rollback in a staging environment.
- Approval. Obtain written stakeholder approval for the plan and the rollback procedures.
What do These Sources Not Say?
- Neither source names or ranks migration providers.
- Neither source gives prices.
- Microsoft steps apply to Azure. AWS strategies apply to AWS.
Related reading: cloud versus on premise and the benefits of moving your business to the cloud.
Frequently Asked Questions
How do I Choose a Cloud Migration Service Provider?
Plan first. Check your team skills and agree a data path. Agree a migration sequence and require a tested rollback plan in writing.
What are the 7 Rs of Cloud Migration?
AWS lists Retire, Retain, Rehost, Relocate, Repurchase, Replatform and Refactor.
Which Strategy is Best for a Large Migration?
AWS advises large migrations to rehost, relocate or replatform first. It states that refactoring is the most complex and costly strategy.
Should I Hire a Partner?
Microsoft advises you to bring in Microsoft or a Microsoft partner when your team lacks cloud migration experience.
Does Microsoft Rank Migration Providers?
No. Microsoft describes a method and does not rank providers.
Key Takeaways
- AWS lists seven migration strategies.
- Microsoft lists five migration steps.
- Check team skills before you hire a partner.
- Test your rollback plan before the move.
- Neither source ranks providers.
Sources and References
Facts follow AWS and Microsoft documentation.
- Migration strategies (AWS Prescriptive Guidance) docs.aws.amazon.com
- Migrate methodology (Microsoft Cloud Adoption Framework) learn.microsoft.com