Is rehosting always the fastest option?

Often yes, because it minimises code changes. But rehosting can also carry old problems into AWS — outdated architecture, manual processes or cost inefficiencies — so it's not always the best long-term choice.

When is refactoring worth the extra effort?

When the current architecture is limiting growth, causing outages, slowing releases, or restricting scale. Refactoring takes more planning but unlocks the most long-term value.

Can we mix strategies across one migration?

Yes — most realistic migrations do. Some workloads get rehosted, others replatformed, a few refactored, and some retired entirely. The right mix comes from the assessment.

Migration Strategy

AWS Rehost vs Refactor: which migration strategy is right?

Not every workload needs a rebuild. Not every workload should be lifted and shifted. The right choice depends on risk, cost, urgency, technical debt and future growth plans.

Book an AWS migration assessment

Rehost, replatform or refactor?

Route	What it means	Best when	Watch out for
Rehost	Move existing workloads with minimal change	Speed matters, architecture is stable, low appetite for change	Can carry old problems into AWS
Replatform	Make targeted changes during migration	You want quick wins without a full rebuild	Scope can creep if not controlled
Refactor	Redesign or rebuild parts of the application	Scalability, resilience or release speed needs improving	More time, cost and technical planning

When rehost makes sense

The right choice when the business needs to move quickly, the current application is relatively stable, and the immediate goal is to exit a data centre, hosting contract or unsupported infrastructure.

Tight migration deadline
Limited code change appetite
Legacy infrastructure exit
Clear application boundaries
Short-term platform move before later optimisation

When refactor makes sense

Better when the existing architecture is holding the business back. Supports scalability, resilience, deployment speed and operational maturity — but needs stronger planning and engineering input.

SaaS platform needs scale
Current architecture creates outages
Release cycles are too slow
Database or app design is limiting growth
Business wants long-term cloud-native value

Middle option

The middle option — replatform

Replatforming is often the most practical route for SaaS and B2B software teams. It avoids a full rebuild but still improves the workload during migration — using AWS managed services, better deployment patterns, improved monitoring or more suitable infrastructure choices.

SaaS AWS migration Migration process

FAQs

Frequently asked questions

Planning an AWS migration?

Start with a practical assessment before committing to a full migration project. IG CloudOps will help you understand what should move, what should change, what could go wrong, and what the next step should be.

Book an AWS migration assessment