AWS Migration Strategies: The 6 R's Explained for CLF-C02

AWS migration strategies, known as the 6 R's, provide frameworks for moving workloads to the cloud. These include Rehosting (lift-and-shift), Replatforming (lift-and-reshape), Refactoring (re-architecting), Relocating (hypervisor-level move), Repurchasing (switching to SaaS), and Retaining (keeping on-prem). Choosing the right one depends on business goals, budget, and required cloud-native benefits.

What is Rehosting and why is it called 'Lift-and-Shift'?

Rehosting is the most straightforward migration strategy, often referred to as 'lift-and-shift.' In this scenario, you move your applications and data from an on-premises environment to the AWS Cloud without making any changes to the application code or architecture. You are essentially taking a virtual machine from your own data center and dropping it into an Amazon EC2 instance.

This approach is ideal when you have a tight deadline or a mandate to exit a physical data center quickly. Because you aren't rewriting code, the risk of introducing new bugs is low, and the migration speed is high. However, the trade-off is that you don't take full advantage of cloud-native features like auto-scaling or managed databases. For the CLF-C02 exam, if you see a scenario emphasizing 'speed' and 'minimal changes,' Rehosting is almost always your answer.

How does Replatforming differ from Rehosting?

If Rehosting is 'lift-and-shift,' Replatforming is 'lift-and-reshape.' Here, you aren't changing the core architecture of the application, but you are swapping out a few components to take advantage of cloud efficiencies. A classic example is moving a self-managed SQL database running on a virtual machine to Amazon RDS (Relational Database Service).

By doing this, you reduce the operational burden of patching and backups without having to rewrite the entire application. You get a 'win' in terms of performance and management overhead without the massive time investment required for a full rewrite. When studying for the Cloud Practitioner exam, look for keywords like 'optimizing' or 'managed services' without a complete overhaul of the application logic. This is the middle ground between the speed of rehosting and the power of refactoring.

When should you choose Refactoring over other strategies?

Refactoring, or re-architecting, is the most intensive migration strategy. This involves reimagining how the application is architected and developing it using cloud-native features from the ground up. Instead of a monolithic application on a server, you might break it into microservices using AWS Lambda for serverless computing or Amazon ECS for containerization.

While this requires the most effort and investment, it yields the highest ROI in terms of scalability, reliability, and cost-efficiency. You are no longer just 'running in the cloud'; you are 'built for the cloud.' On the exam, Refactoring is the correct choice when the business goal is 'maximum scalability' or 'leveraging serverless architectures.' It is the most expensive path upfront but the cheapest to operate at scale over time.

What are Relocate, Repurchase, and Retain?

The remaining three R's cover specific business needs. Relocating is a specialized move, typically involving VMware Cloud on AWS, where you move your VMware virtual machines to AWS without changing the hypervisor. It's essentially a 'lift-and-shift' for VMware environments that avoids the need for complex conversion tools.

Repurchasing involves abandoning your legacy software entirely and switching to a different product, typically a Software-as-a-Service (SaaS) offering. A common example is moving from a locally hosted email server to Salesforce or Microsoft 365. Finally, Retaining is the decision to keep a workload on-premises. This usually happens due to strict compliance requirements, legacy dependencies that cannot be moved, or because the app is slated for decommissioning soon.

Understanding these distinctions is key for the CLF-C02. If the scenario mentions 'switching to a SaaS model,' think Repurchase. If it mentions 'compliance' or 'cannot be moved,' think Retain.

How do you match business goals to the right migration strategy?

Choosing a strategy isn't about which one is 'best' technically, but which one aligns with the business's current constraints. If the primary goal is a rapid data center exit to save on lease costs, Rehosting is the winner. If the goal is to reduce the administrative burden of database management, Replatforming is the way to go.

If the organization wants to pivot its entire business model to be more agile and scalable, Refactoring is necessary. We always recommend students create a simple decision matrix: Speed $\rightarrow$ Rehost; Efficiency $\rightarrow$ Replatform; Transformation $\rightarrow$ Refactor. By mapping the 'business driver' to the 'technical action,' you can eliminate wrong answers on the exam quickly. Remember, AWS wants you to show that you understand the trade-off between the time spent migrating and the long-term benefits gained.

How can you spot the correct migration answer on the CLF-C02 exam?

The CLF-C02 exam often uses specific 'trigger words' to guide you toward the right migration strategy. 'Minimal effort' or 'fastest' almost always points to Rehosting. 'Managed services' or 'optimization' points to Replatforming. 'Cloud-native,' 'Serverless,' or 'Microservices' are dead giveaways for Refactoring.

To truly master these concepts, you need to see them applied across hundreds of different scenarios. This is why we built Cert Sensei to provide 1,000 expert-curated AWS Cloud Practitioner practice questions. Instead of just telling you if an answer is right or wrong, we provide detailed expert reasoning for every single choice. Our domain-level analytics will show you exactly where you're struggling—whether it's Migration strategies or the Shared Responsibility Model—so you can stop wasting time on what you already know and focus on your weak points.

❓ Frequently Asked Questions