Comparison

Updated October 25, 2026

· ~1 min read

Rehost vs Replatform (vs Refactor and Replace): Choosing a Modernization Strategy per Application

Modernization
Migration Strategy
7 Rs
Legacy Modernization
Cloud Migration

Modernization programs fail when one strategy is applied to everything. Refactoring an estate of 300 applications takes a decade; rehosting all of them moves the problems along with the servers. The useful question is which strategy fits each application, based on how much it is worth and how often it changes.

AWS's seven Rs are the standard vocabulary. They are also a decision aid, because the cheapest options (retire and retain) are on the list and are usually underused.

The seven Rs

Strategy

What it means

Effort

What changes

Retire

Switch it off

Lowest

Cost and risk disappear

Retain

Leave it where it is, for now

None

Nothing; revisit later

Rehost

Move servers as they are (lift and shift)

Low

Where it runs

Relocate

Move a platform as a whole, such as VMware to Amazon EVS

Low

Where the hypervisor runs

Repurchase

Replace with a SaaS product

Medium

Who runs it; often the process too

Replatform

Move with targeted changes to use managed services

Medium

Operations, some cost

Refactor

Re-architect or rewrite for the cloud

Highest

How it is built and delivered

Examples

Application

Likely strategy

Why

Vendor ERP on Windows Server 2016 and SQL Server 2016

Rehost, upgrading OS and database versions on the way

The vendor controls the code; you control the platform

In-house .NET Framework web app changed monthly

Refactor to .NET 10 on Linux containers

Frequent change, Windows licence savings, AWS Transform reduces the effort

Java batch jobs on a VM with cron

Replatform to scheduled ECS tasks or Lambda

Small change, removes a server to patch

On-premises Exchange

Repurchase as Exchange Online

Commodity; high security risk to self-host

A reporting server nobody has logged into for a year

Retire

Confirm with the owner, snapshot, delete

How to decide, per application

Question 1 of 3

Has anyone used it in the last 90 days?

Our verdict

**Retire** anything unused. In most estates this is 10–20% of applications and the fastest saving there is. **Rehost or relocate** stable applications that rarely change, to get off old infrastructure quickly. **Replatform** where a managed service removes real work: self-managed SQL Server to RDS, Windows to Linux containers, cron boxes to scheduled tasks. **Refactor** the applications that change most often and matter most. That is where speed of delivery pays back. **Repurchase** commodity functions (email, HR, CRM) as SaaS. No strategy is the right one for a whole estate. A typical outcome is a mix, decided application by application.

Related solutions

AWS Architecture Review

A focused, senior-level review of your current AWS architecture, with a prioritized list of what to fix and why.

1 week
$4k–$8k
View

Windows Server, SQL Server and .NET End-of-Support Migration

Get every Windows Server 2012/2016, SQL Server 2016/2017 and .NET Framework or .NET 8 workload onto a supported version before the deadlines, with the licence savings found along the way. Inventory, retire, upgrade or modernize, decided application by application.

3–10 weeks
$15k–$60k
View

VMware Exit to AWS

Move off VMware before the next renewal: most VMs rehosted to right-sized EC2 with AWS Application Migration Service, a time-boxed Amazon EVS landing for what cannot move yet, and the data center contract ended on a date you choose.

4–12 weeks for the first waves
$20k–$80k
View

Get your application portfolio assessed and a migration plan

We work with startups and growing companies on AWS architecture decisions. Tell us about your situation and we will recommend the right approach.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.