What Is Cloud Migration? Types, Steps and the 7 Rs Guide

Cloud migration phases and strategies, from AWS.

Fact-checked Reviewed by Meera Krishnan Updated November 17, 2026 Based on 3 sources
Summary

What is cloud migration? AWS defines it as moving data, applications and IT resources from on-premises data centers to a cloud provider's infrastructure. Done with a planned strategy, AWS says it is a structured and nondisruptive shift. AWS splits the work into three stages: assess, mobilize, and migrate and modernize.

What Is Cloud Migration?

What is cloud migration in practice? It covers moving a database, an application, a whole data center or workloads between cloud providers. Each move has its own risks, so a plan comes first. A cloud migration strategy gives the business case, the scope and the best method for each component, such as an internal application or a development environment. AWS lists these benefits:

  • Cost efficiency: lower spending on hardware, power and cooling, plus pay-for-use pricing.
  • Scalability: resources adjust to demand without costly infrastructure upgrades.
  • Security: providers invest in encryption, MFA, audits and backup, but you stay responsible for configuration and access controls.
  • Performance: newer hardware and distributed data centers can reduce latency.

Types of Cloud Migration

AWS describes five types: database migration, application migration, hybrid migration, data center migration and cloud-to-cloud migration. Hybrid migration runs some workloads in the cloud and keeps others on-premises, often as a step toward a full move. Cloud-to-cloud migration moves workloads between providers for cost, performance, regulatory or service reasons, and you must manage transfer speed, downtime and vendor lock-in.

Cloud Migration Steps

AWS uses three phases for its cloud migration steps. Each phase builds on the one before it.

  1. Assess: define business goals, understand technical requirements, estimate costs and savings, and rank applications by value and complexity. For small businesses, AWS suggests taking inventory of servers, applications and dependencies.
  2. Mobilize: build a core cloud team, create a plan with timelines and milestones, set up a secure environment and run pilot applications. AWS also mentions designing a landing zone, defining success metrics and grouping applications into migration waves.
  3. Migrate and modernize: scale up using lessons from the pilots, optimize for cloud-native features, monitor performance, security and cost, and keep improving.

The 7 Rs of Cloud Migration

AWS Prescriptive Guidance names seven strategies for moving applications:

  • Retire: decommission applications you no longer need.
  • Retain: keep an application where it is for now, for example because of data residency rules.
  • Rehost: "lift and shift" the stack without changes.
  • Relocate: move to a cloud version of the same platform, such as another VPC or account.
  • Repurchase: replace the application with a SaaS or newer product.
  • Replatform: move and make targeted optimizations.
  • Refactor or re-architect: redesign the application for cloud-native features.

For large migrations, the guide recommends rehost, relocate, replatform and retire, and it advises against refactoring during the migration itself. Refactoring is the most complex and costly option. Rehost suits large numbers of machines because it avoids compatibility work and long cutover windows.

Which Deployment Model Should You Use?

The small business guide lists three models. Public gives on-demand capacity with no hardware purchases and suits businesses where cash flow and speed matter. Private suits businesses with dedicated infrastructure or strict data placement needs, but you take on more management work. Hybrid keeps systems that cannot move yet on-premises while new workloads run in AWS, which avoids a big-bang cutover. Your choice sets the scope of networking, identity, backup and compliance work before the first workload moves. For the assess phase, AWS names Migration Evaluator for a directional business case and AWS Migration Hub for discovery, dependency mapping and tracking.

Cloud Migration Checklist

The AWS cloud migration plan for small businesses adds practical checks. Use this cloud migration checklist as a starting point:

  • Define goals and inventory your applications, workloads and data.
  • Estimate costs and prioritize workloads by value and complexity.
  • Run at least one test cutover and keep a rollback path.
  • Schedule the cutover during a low-traffic window.
  • Tag resources and enable budget alerts from day one.
  • Track cutover time, error budget and cost change per wave.

AWS also lists common challenges: interdependent systems that can break if moved separately, large data transfers that take time, and teams that lack cloud skills. To compare vendors who can help, see our list of the top cloud migration service providers. If you are new to the basics, read what is cloud storage and how it works.

What Do These Sources Not Say?

The AWS pages describe migration to AWS, so they do not compare other providers. AWS reports that small business customers average 31% cost savings after migrating, but this is its own claim and the page gives no independent check. The small business page does not state pricing for the assessment tools. None of the pages give a standard timeline for a migration.

Frequently Asked Questions

What is cloud migration in simple words?

It is moving data, applications and IT resources from on-premises data centers to a cloud provider.

How many stages does AWS use?

Three: assess, mobilize, and migrate and modernize.

What are the 7 Rs?

Retire, retain, rehost, relocate, repurchase, replatform, and refactor or re-architect.

What is rehosting?

It is also called "lift and shift": moving the application stack to AWS without changing it.

Why run a pilot first?

AWS lists pilot migrations as part of mobilize, so you can test the process and apply the lessons at scale.

Does the cloud remove security work?

No. Providers invest in protections, but you remain responsible for configuration and access controls.

Key Takeaways

  • What is cloud migration? Moving workloads from on-premises to a cloud provider, with a plan.
  • Follow three phases: assess, mobilize, and migrate and modernize.
  • Pick a strategy per application from the 7 Rs, and avoid refactoring mid-migration at scale.
  • Test a cutover, keep a rollback path and track cost and errors for every wave.

Sources and References

Facts follow AWS documentation.

  1. What is Cloud Migration?, AWS aws.amazon.com
  2. About the migration strategies, AWS Prescriptive Guidance docs.aws.amazon.com
  3. How to create a cloud migration plan for SMBs on any budget, AWS aws.amazon.com