6.1 The 7 Rs of Cloud Migration

Key Takeaways

  • The 7 Rs are migration strategies: Retire, Retain, Relocate, Rehost (lift-and-shift), Replatform (lift-tinker-and-shift), Repurchase (drop-and-shop), and Refactor (re-architect).
  • Rehost (lift-and-shift) is the fastest migration approach — move applications as-is to EC2 without code changes.
  • Replatform makes minor optimizations during migration (e.g., moving from self-managed MySQL to RDS) without changing core architecture.
  • Refactor/Re-architect offers the most long-term benefit by redesigning applications to be cloud-native (serverless, microservices) but takes the most time.
  • AWS Application Migration Service (MGN) automates lift-and-shift migrations to AWS with minimal downtime.
Last updated: March 2026

The 7 Rs of Cloud Migration

Quick Answer: The 7 Rs are migration strategies ordered from simplest to most transformative: Retire (decommission), Retain (keep on-premises), Relocate (move to VMware Cloud on AWS), Rehost (lift-and-shift to EC2), Replatform (move with minor optimizations), Repurchase (switch to SaaS), Refactor (re-architect for cloud-native).

The 7 Migration Strategies

StrategyDescriptionEffortBenefitExample
RetireDecommission applications no longer neededLowestCost reductionLegacy app with no users
RetainKeep on-premises (not ready to migrate)LowNone (deferred)App with complex dependencies
RelocateMove to VMware Cloud on AWSLowSame VMware toolsVMware-based workloads
RehostLift-and-shift to EC2 (no changes)Low-MedQuick migrationWeb server → EC2
ReplatformLift-tinker-and-shift (minor optimizations)MediumSome cloud benefitsMySQL → RDS, Java app → Beanstalk
RepurchaseReplace with SaaS productMediumReduced opsOn-prem CRM → Salesforce
RefactorRe-architect for cloud-nativeHighestMaximum cloud benefitMonolith → microservices + Lambda

When to Use Each Strategy

ScenarioBest Strategy
"Migrate 500 servers to AWS as fast as possible"Rehost (lift-and-shift)
"Move our database to a managed service"Replatform (to RDS/Aurora)
"We want to go serverless"Refactor
"This app is no longer used"Retire
"Too complex to migrate right now"Retain
"Replace our email server"Repurchase (to Amazon WorkMail or Office 365)

AWS Migration Services

ServicePurpose
AWS Migration HubCentral tracking for all migration activities
AWS Application Migration Service (MGN)Automated lift-and-shift for servers
AWS Database Migration Service (DMS)Migrate databases with minimal downtime
AWS Schema Conversion Tool (SCT)Convert database schemas between engines
AWS DataSyncTransfer data between on-premises and AWS storage
AWS Snow FamilyPhysical devices for large data transfers
AWS Transfer FamilySFTP/FTPS/FTP service backed by S3/EFS

AWS Application Migration Service (MGN)

FeatureDetail
TypeAutomated lift-and-shift
HowContinuous block-level replication from source to AWS
CutoverNon-disruptive cutover with minimal downtime
SupportedPhysical, virtual, and cloud servers
TargetEC2 instances
TestingLaunch test instances without affecting source

AWS Database Migration Service (DMS)

FeatureDetail
TypeDatabase migration (homogeneous and heterogeneous)
SourceOn-premises, EC2, RDS, Aurora, S3, and more
TargetRDS, Aurora, DynamoDB, S3, Redshift, and more
ReplicationContinuous data replication (CDC) for minimal downtime
HomogeneousSame engine (MySQL → MySQL) — no SCT needed
HeterogeneousDifferent engine (Oracle → PostgreSQL) — use SCT first

On the Exam: "Migrate an Oracle database to Aurora PostgreSQL" → SCT to convert the schema + DMS for data migration. "Migrate MySQL to RDS MySQL" → DMS only (homogeneous).

Test Your Knowledge

A company needs to migrate 200 servers to AWS as quickly as possible with minimal changes. Which migration strategy should they use?

A
B
C
D
Test Your Knowledge

A company wants to migrate an Oracle database to Amazon Aurora PostgreSQL. Which AWS services should they use?

A
B
C
D