Chapters0/41 ▾
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
Chapter 2 · Lesson 4 of 5
Migration strategies: the 7 Rs
1 min read
AWS Prescriptive Guidance lists seven migration strategies. Exam questions describe what happens to one application and ask which strategy it is. Focus on how much the application changes and whether the business still needs it.
| Strategy | What happens |
|---|---|
| Rehost (lift and shift) | Servers move to AWS unchanged |
| Relocate | A whole platform moves in bulk to the cloud version of the same platform |
| Replatform (lift and reshape) | Some optimization, such as a managed database, with no redesign |
| Refactor (re-architect) | Redesign for cloud-native features; the most complex and costly path |
| Repurchase (drop and shop) | Replace with a different product, often SaaS |
| Retain | Keep it where it is for now, for example because of data residency |
| Retire | Shut it down because it no longer has business value |
Example: a clinic moves its self-managed MySQL database from a rack server to Amazon RDS for MySQL and leaves the application code alone. Adopting a managed service without a redesign makes this replatform, not rehost.
If the clinic instead dropped its licensed scheduling software for a SaaS product from another vendor, that would be repurchase. If it kept a records system on site because of a residency rule and planned to revisit later, that would be retain, not retire, since the system still has business value.
Check yourself
1. To cut database administration work, a company moves its self-managed SQL Server database to Amazon RDS for SQL Server. The core application code stays unchanged and nothing is redesigned. Which migration strategy is this?
2. A company decides to stop running its licensed on-premises customer management system and move its users to a software as a service (SaaS) product from a different vendor. Which migration strategy is this?
Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) exam guide, AWS Well-Architected Framework, An Overview of the AWS Cloud Adoption Framework
AWS Cloud Practitioner cheat sheet: every key fact on one page →