Why Your Migration Should Skip Rehosting and Go Straight to Replatforming

You're a cloud architect at a mid-sized logistics firm. Your CEO just said, "Move everything to AWS by Q4." You've got 200 servers, a legacy ERP, a custom tracking app, and a bunch of zombie applications nobody wants to admit exist. What's the fastest path that doesn't blow up the budget or the security team's blood pressure?

Forget lift-and-shift. I'll say it plainly: rehosting is for emergencies, not strategy. The right move, for most of your portfolio, is replatforming—and the data backs it up. In a Red Hat survey, replatforming was the most common migration approach at 20%, with other strategies ranging between 10% and 19%. And 47% of organizations plan to skip rehosting entirely and go straight to replatforming (Red Hat). That's not a fringe opinion; that's the mainstream.

Assess: Don't Guess What You're Moving

Before you touch anything, you need a full inventory. Microsoft Learn's Azure migration framework starts with Assess: create a full inventory and dependency map of servers, services, and apps, and estimate cost savings using the Azure Total Cost of Ownership (TCO) Calculator. You can't replatform what you don't know exists. Dependency mapping is non-negotiable—miss a connection between the ERP and the tracking app, and you'll have a outage on day one.

But don't stop at inventory. Classify every workload. AWS defines 'zombie applications' as those with average CPU and memory usage below 5 percent and 'idle applications' as those with 5-20 percent usage over 90 days; both, plus applications with no inbound connection in the last 90 days, are candidates for the retire strategy. Yeah, that's a third of your portfolio that can just die. Retire them now. That's free savings.

Pick Your Lane: Replatform vs. Rehost vs. Refactor

Here's the decision. Rehost moves apps as-is, no code changes. It's fast, but you get no cloud-native benefits—you're just renting the same tin. Replatform makes minor optimizations, like swapping your self-managed database for a managed one, without touching the core architecture (DigitalOcean). Refactor re-architects everything into microservices or serverless—most benefit, most effort (DigitalOcean).

For a 200-server estate, refactor is a death sentence. AWS explicitly says refactor is not recommended for large migrations because it modernizes during the migration, which is the most complex strategy to manage across many applications (AWS Prescriptive Guidance). So you're left with rehost or replatform. Replatform wins because it captures cloud value without the rewrite.

The sweet spot is replatforming your custom tracking app: move it to containers with AWS App2Container, or swap your SQL Server to Amazon RDS. That's a concrete example: your ERP's SQL Server database becomes Amazon RDS for SQL Server, a replatform move that AWS explicitly lists (AWS Prescriptive Guidance). You keep the app's architecture, but you offload patching, backups, and scaling to AWS. That's not a lift-and-shift; that's a tinker that pays off.

Optimize: Don't Let Spend Run Wild

Migrating is only half the battle. Flexera's 2025 report found 84% of organizations say managing cloud spend is their top challenge, and cloud budgets exceeded limits by 17% (Flexera 2025). That's not a cost problem; it's a strategy problem. If you replatform, you can right-size from day one. Azure Migrate assessments cover Azure readiness, right-sizing of Azure VM sizes and SQL configuration, and Azure cost estimation (Azure Migrate). That's how you avoid the 29% waste that Flexera 2026 found on IaaS and PaaS—the first increase after five years of decline (Flexera 2026).

And don't forget the FinOps piece. Flexera 2026 reports 63% of organizations now have a dedicated FinOps team, and 71% have a Cloud Center of Excellence (Flexera 2026). If you don't have one, start one. The goal is to measure value delivered to business units—64% of orgs do that now, up 12 points year over year (Flexera 2026). That's how you justify the replatforming effort to your CFO.

The Takeaway

Stop treating rehosting as the default. It's the lazy option that leaves you with a cloud bill and no cloud benefits. Replatforming is the pragmatic middle path: it's the most common migration approach, it's what nearly half of your peers plan to do, and it sets you up for cost control. Assess your portfolio, retire the zombies, replatform the real workloads, and refactor only the crown jewels. Your CEO gets the cloud, your security team gets managed services, and your budget survives contact with the cloud.

Sources

• DigitalOcean - https://www.digitalocean.com/resources/articles/cloud-migration-strategy
• Red Hat - https://www.redhat.com/en/blog/how-should-you-modernize-your-applications
• Microsoft Learn - https://learn.microsoft.com/en-us/training/modules/design-migrations/3-describe-azure-migration-framework
• AWS Prescriptive Guidance - https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/migration-strategies.html
• Flexera 2025 - https://www.flexera.com/about-us/press-center/new-flexera-report-finds-84-percent-of-organizations-struggle-to-manage-cloud-spend
• Flexera 2026 - https://www.flexera.com/blog/finops/the-new-era-of-cloud-what-2026-data-tells-us-about-spend-scale-and-strategy/