# The 7 Rs of Cloud Migration, Explained in Plain English

> Retire, retain, rehost, relocate, repurchase, replatform and refactor: what each means, when it fits, and a simple way to decide for every app you run.

- Page: https://devopstechlab.com/resources/blog/seven-rs
- Last updated: 2026-11-14
- Contact: sales@devopstechlab.com · +91 90670 77200 (call or WhatsApp) · Monday to Friday, 10 AM to 7 PM IST
- This is a plain-text copy of the page above for AI tools. The page itself is the reference.

---
1. [Home](https://devopstechlab.com/)
2. [Resources](https://devopstechlab.com/resources/)
3. [Blog](https://devopstechlab.com/resources/blog/)
4. Migration

Migration

# The 7 Rs of cloud migration, decided app by app

Not everything should move the same way. Some apps should be switched off, some lifted as they are, some rebuilt. Here are the seven options in plain words, and how to choose for each app.

By [Janak Thakkar](https://devopstechlab.com/about/) 9 December 2025 5 min read

1. 1 Retire
2. 2 Retain
3. 3 Rehost
4. 4 Relocate
5. 5 Repurchase
6. 6 Replatform
7. 7 Refactor

In short

Choose one of the 7 Rs for each app rather than one route for the whole migration. Retire what nobody uses, retain what must stay on site, repurchase where a subscription does the job, and relocate large VMware groups. Refactor apps that must scale or change often, replatform where a managed service saves work, and rehost the rest.

Official references: [AWS Migration Acceleration Program](https://aws.amazon.com/migration-acceleration-program/) · [Azure migration planning guide](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/migrate/plan-migration)

ISO 27001 · SOC 2 · Working with companies across India and abroad from Ahmedabad, in IST

In this article

“Moving to the cloud” sounds like one decision. In practice it is one decision per app. The accounting software, the file server, the company website and the old intranet each have a different best route, and treating them all the same is how migrations go over budget.

The cloud industry uses “the 7 Rs” to name the options. Here they are without the jargon, in order from least change to most.

## The seven options

| R | In plain words | How much changes |
| --- | --- | --- |
| **Retire** | Switch it off | Nothing moves |
| **Retain** | Keep it where it is, for now | Nothing moves yet |
| **Rehost** | Lift and shift: move the server as it is | Very little |
| **Relocate** | Move a whole VMware platform as it is | Very little |
| **Repurchase** | Replace it with a subscription service | The software changes |
| **Replatform** | Lift and tune: move, then swap a part for a managed service | Some |
| **Refactor** | Rebuild it for the cloud | A lot |

## Retire: switch it off

Most server rooms have systems nobody uses: an old intranet, a reporting server for a team that no longer exists, a test machine from three years ago. Retiring them is the cheapest migration there is. Keep a backup of the data, agree a date, and turn them off.

## Retain: keep it where it is, for now

Some things shouldn’t move yet: a machine controlling equipment on the factory floor, a door attendance system wired into the building, or an app the vendor will only support on site. Retaining is a decision, not a failure. Note why, and look again in a year.

## Rehost: lift and shift

Copy the server into the cloud as a virtual machine and run it there unchanged. It is the fastest way to empty a server room and the least risky for the people using the app. The downside: you carry over its inefficiencies, so plan to right-size it after the move. Tally on a cloud server is a typical rehost.

## Relocate: move the VMware platform

If you run VMware, you can move whole groups of VMs to a VMware environment hosted by the cloud provider, without converting each one. It is the quickest route for large VMware estates, especially when a renewal deadline is close.

## Repurchase: switch to a subscription

Instead of moving the software, replace it with a service that does the same job. The classic example is an office mail server replaced by a subscription email service. You stop running and patching the software; you start paying per user.

## Replatform: lift and tune

Move the app, but swap one part for something the cloud runs for you. The most common case: the app stays as it is, but its database moves to a managed database service, so backups, patching and failover are handled. A little more work than rehosting, and usually worth it.

## Refactor: rebuild for the cloud

Change the app itself so it can scale up and down, run in containers or use cloud services directly. It takes the most time and money, and pays off for apps that are core to your business and changing often, such as a customer portal or your own software product.

Decide for one app

### Is anyone still using it?

## Deciding app by app

Ask these questions in order for each app. The first “yes” usually gives you the answer:

1. **Is anyone still using it?** No: **retire** .
2. **Does it have to stay on site** (hardware, vendor support, rules)? Yes: **retain** .
3. **Is there a good subscription service that does the same job?** Yes: consider **repurchase** .
4. **Is it part of a large VMware group you want to move together?** Yes: **relocate** .
5. **Does it need to scale or change often?** Yes: consider **refactor** .
6. **Would a managed database or similar service save real work?** Yes: **replatform** . Otherwise: **rehost** .

## Common apps and our usual call

| What you run | Usual route |
| --- | --- |
| Tally or similar accounting software | Rehost to a cloud server |
| Office file server | Replatform to a managed file service, or repurchase if you use a suite with file storage |
| Office mail server | Repurchase: subscription email |
| Database server | Replatform to a managed database |
| Company website | Rehost or replatform |
| VMware cluster | Relocate, then rehost or replatform app by app over time |
| Customer portal or your own product | Replatform now, refactor later |
| Old intranet nobody opens | Retire |
| Door attendance or factory systems | Retain |

These are starting points, not rules. The right answer depends on how the app is built and what it is worth to the business.

## Mixing the Rs in one migration

A real migration almost always uses several Rs at once. Picture a company with 16 systems in its server room. After an assessment, the picture often looks something like this:

- 3 are **retired** , because nobody has opened them in a year.
- 2 are **retained** on site, because they control equipment.
- 2 are **repurchased** : mail and file sharing move to subscription services.
- 2 are **replatformed** : their databases move to a managed service.
- 7 are **rehosted** as they are.

Only 7 of the 16 move as servers or virtual machines. That is why counting servers alone gives the wrong budget, and why the decision has to be made app by app. (This is an illustration, not a client example.)

The 16-system example: only 7 move as servers or VMs

*3 retired* *2 retained* *2 repurchased* *2 replatformed* *7 rehosted*

## Then plan the waves

Once each app has its R, group them into waves. Start with the least critical and simplest, so the team learns the process on systems that can afford a hiccup. Move the core business systems in later waves, each with a tested way back and a switch-over window outside working hours.

**A note on names.** AWS uses these seven. Microsoft’s Cloud Adoption Framework uses a slightly different list (including rearchitect, replace and rebuild), and you may also hear “the 6 Rs”. The ideas are the same.

## Where DevOps TechLab fits

We have run more than 165 migration projects and moved over 275 workloads, from a single Tally server in a few days to whole server rooms in about three months. Our free migration assessment gives every app you run an R, with the reason, so you know what moves how before anything is touched.

## Questions people ask

What are the 7 Rs of cloud migration?

Retire, retain, rehost, relocate, repurchase, replatform and refactor. They are the options for what to do with each app when you move to the cloud.

What is the difference between rehost and replatform?

Rehost moves a server as it is. Replatform moves it and swaps one part, often the database, for a service the cloud provider runs for you.

Is lift and shift a bad idea?

No. It is often the fastest and safest first step. Plan to right-size servers after the move so you don’t carry over waste.

Should every app be refactored?

No. Refactoring costs the most and suits apps that are core to the business and change often. Most apps do well with rehost or replatform.

How long does a migration take?

It depends on how many apps and which routes they take. Ours range from 3 days for a single server to about 3 months for a whole server room.

**Written by Janak Thakkar, Founder, DevOps TechLab**

Our engineers work on AWS, Azure and Google Cloud for Indian businesses every day. Have a question about this post? Ask the person who works on it.

Ask an engineer

### Want an R for every app you run?

Book a free migration assessment. You get a report that gives each app its route, with the reason and a wave plan.

#### Sources

1. [AWS Migration Acceleration Program](https://aws.amazon.com/migration-acceleration-program/)

[Next post · AI **Copilot in Microsoft 365 or Gemini in Google Workspace: what each does for a team** Head to head design · 5 min read](https://devopstechlab.com/resources/blog/copilot-or-gemini)

## Keep reading

[AI **Answering questions from your own documents on AWS, Azure or Google Cloud**](https://devopstechlab.com/resources/blog/ask-your-documents) [Google Cloud **Google Cloud for teams already on Google Workspace: where to start**](https://devopstechlab.com/resources/blog/gcp-for-workspace-teams) [Azure **One login for Microsoft 365 and Azure with Microsoft Entra ID**](https://devopstechlab.com/resources/blog/entra-id-one-login)

Keep exploring

## Next steps for your migration

- [Service **Cloud migration services** Servers, apps and databases moved to AWS, Azure or Google Cloud in planned waves.](https://devopstechlab.com/solutions/cloud-migration/)
- [Guide **AWS MAP and cloud migration funding** What AWS, Microsoft and Google pay for, and how to qualify.](https://devopstechlab.com/resources/blog/migration-funding)
- [Case study **AWS to Azure migration case study** Gamerji moved in 3 weeks and cut its monthly cloud bill by 36%.](https://devopstechlab.com/resources/cases/gamerji)
- [Case study **AWS migration case study** Devine Globe: from managed hosting to a production-ready AWS setup.](https://devopstechlab.com/resources/cases/devine-globe)

Talk to an engineer

## Start with a 20-minute review. Leave with a plan.

An engineer looks at your current setup, points out what’s costing you money or risk, and tells you what we’d fix first. No sales deck, no obligation to go ahead.

[Sales and general enquiries **janak@devopstechlab.com**](mailto:janak@devopstechlab.com) [Call us **+91 90670 77200**](tel:+919067077200)

Every month you wait, the bill grows, the audit gets harder and the AI project waits another quarter.
