Skip to content
Draft: this topic has not been reviewed yet. Check facts against the linked AWS documentation before relying on them.

Moving to AWS — the Cloud Adoption Framework and the 7 Rs

Difficulty
Confidence

Moving to the cloud is not just copying servers. It changes how teams work, how money is spent and how risk is managed. AWS gives two tools for thinking about it:

  • The AWS Cloud Adoption Framework (AWS CAF) for the organization as a whole.
  • The 7 Rs for deciding what happens to each individual application.

The AWS Cloud Adoption Framework (AWS CAF)

AWS CAF collects AWS’s experience from many migrations into best practices. It starts with the business outcomes a cloud move should bring:

  • Reduced business risk, for example through better reliability and security.
  • Improved environmental, social and governance (ESG) performance, for example by using energy-efficient infrastructure.
  • Increased revenue, from launching new products and reaching new markets faster.
  • Increased operational efficiency, by spending less effort on routine IT work.

It then groups the abilities an organization needs into six perspectives. Three are about the business and three are technical.

Perspective Focus Typical owners
Business Make sure cloud investments serve business goals CEO, CFO, COO, CIO, CTO
People Culture, organization structure, leadership, skills and training HR, leaders, cloud teams
Governance Manage the benefits and risks of cloud programs; budgets and portfolio Program managers, risk and finance owners
Platform Build a scalable, reliable cloud platform, including hybrid setups CTO, architects, engineers
Security Confidentiality, integrity and availability of data and workloads CISO, security engineers
Operations Run and support cloud services at the agreed level Infrastructure and operations leaders

A memory aid: Business, People, Governance are the business side; Platform, Security, Operations are the technical side.

The 7 Rs: what to do with each application

Every application in a migration gets one strategy.

Not movedRetireTurn it offRetainKeep it for nowMoved to AWSRehostLift and shiftRelocateMove platformRepurchaseSwitch to SaaSReplatformSmall tweaksRefactorRedesignLeast change, fastestMost change, most cloud benefit
Retire and retain decide what not to move. The other five run from least change (rehost) to most change (refactor).
Strategy What happens Example
Retire Switch it off. It has no business value left An old reporting tool nobody opens
Retain Keep it where it is for now; revisit later A system with recently bought hardware, or one that is not ready to move
Rehost (“lift and shift”) Move servers to AWS as they are Copy virtual machines to EC2 with AWS Application Migration Service
Relocate Move a whole platform without changing the apps on it Move VMware-based workloads to a VMware environment running on AWS
Repurchase Replace with a different product, often software as a service (SaaS) Swap an on-premises CRM for a SaaS CRM
Replatform (“lift, tinker and shift”) Make small changes to benefit from managed services Move a self-run MySQL server to Amazon RDS
Refactor or re-architect Redesign the application to be cloud-native Split a large app into serverless functions and managed services

Which is most common? In large migrations, teams usually rehost, replatform, relocate or retire first, because those are fast. Refactoring brings the most cloud benefit but takes the most effort, so it is often done after the move.

Services that help you migrate

Step Service What it does
Discover AWS Application Discovery Service Collects data about your on-premises servers and how they depend on each other
Build the business case Migration Evaluator Projects what your workloads would cost on AWS
Track AWS Migration Hub Shows migration progress across tools in one place
Move servers AWS Application Migration Service Replicates servers to EC2 so you can switch over with minimal downtime (rehost)
Move databases AWS Database Migration Service (AWS DMS) Copies data into AWS while the source stays in use, and keeps replicating changes until you switch over
Convert schemas AWS Schema Conversion Tool (AWS SCT) Converts the database schema and code when the target engine is different, such as Oracle to PostgreSQL

Database replication is a key idea: with DMS, the old database keeps running and changes keep flowing to the new one, so the final switch takes minutes instead of a long outage.

Where to get help

  • AWS Prescriptive Guidance: tested strategies, guides and patterns for migrations.
  • AWS Professional Services and AWS Partners: experts who plan and carry out migrations.
  • AWS Migration Acceleration Program (MAP): a program of methods, tools and funding support for large migrations.

Putting it together: a retailer’s migration

A retailer with 200 applications plans its move:

  1. Discover: Application Discovery Service maps servers and dependencies.
  2. Decide: 20 old apps are retired, a payroll system is repurchased as SaaS, and most apps are rehosted with Application Migration Service.
  3. Databases: the main Oracle database is replatformed to Amazon Aurora PostgreSQL, using SCT to convert the schema and DMS to copy and replicate the data.
  4. Later: the online shop is refactored to serverless after the move, once the team has cloud experience.

Common mix-ups

  • Rehost vs replatform. Rehost changes nothing; replatform makes small changes, such as moving to a managed database.
  • Repurchase vs refactor. Repurchase buys a different product; refactor rewrites your own.
  • DMS vs SCT. DMS moves the data; SCT converts the schema when engines differ. Same-engine moves need only DMS.

Check yourself

A company wants to move servers to AWS as quickly as possible, with no code changes. Which strategy is that?

Rehost (lift and shift), typically with AWS Application Migration Service.

A team moves its self-managed SQL Server database to Amazon RDS without changing the application. Which R is this?

Replatform. The app is unchanged, but it now uses a managed database service.

Which three AWS CAF perspectives are business-focused?

Business, People and Governance. Platform, Security and Operations are the technical ones.

How can a database stay in use while it is being migrated to AWS?

Use AWS DMS with ongoing replication: the source keeps working while changes are copied to the target until you switch over.

Key takeaways

  • AWS CAF frames the organizational change: four business outcomes and six perspectives.
  • The 7 Rs: retire, retain, rehost, relocate, repurchase, replatform, refactor.
  • Migration services cover discovery, server moves (Application Migration Service), database moves (DMS) and schema conversion (SCT).

Cloud Study Lab is an independent study site. It is not affiliated with or endorsed by Amazon Web Services. AWS and the names of AWS certifications are trademarks of Amazon.com, Inc. or its affiliates.