Strategy for Cloud Architects
Cloud strategy covers how an organisation moves to and spreads across clouds. Migration planning assesses applications and picks an approach such as rehost, replatform or refactor, sequences waves and manages risk, while multi-cloud decisions weigh resilience and portability against added complexity and skills.
Stage: Cost and Migration · Part of the Cloud Architect roadmap · Last reviewed 19 November 2026
What to learn in Strategy
- Classify applications with the rehost, replatform, refactor, retire and retain options
- Build a migration plan with dependencies and cut-over steps
- Estimate the benefits and risks of a multi-cloud approach
- Identify vendor lock-in risks and how to limit them
- Define success metrics for a migration
Strategy interview questions
What is the difference between rehosting and refactoring?
Rehosting, or lift and shift, moves an application to the cloud with few changes, which is quick but gains little. Refactoring redesigns it to use cloud-native services, which takes more effort but improves scalability and cost over time.
Is multi-cloud always the better choice?
No. It can reduce dependence on one vendor and meet regional or regulatory needs, but it raises operational complexity, cost and skill demands, and often limits use of provider-specific services. Many teams are better served by one cloud done well.
Where Strategy fits in the Cloud Architect roadmap
Strategy belongs to the Cost and Migration stage (advanced level). Make it practical.
Other units in this stage
Back to the full Cloud Architect roadmap