Stop Lift-and-Shifting: How to Cut Cloud Migration Costs with the Right R

Who This Is For

If you're staring down a cloud migration and your CFO is already asking about the bill, this is for you. We're going to walk through the practical decisions that separate a migration that saves money from one that bleeds it. As practitioners, we've seen the same pattern: teams rush to lift-and-shift because it feels fast and safe, then spend the next two years paying for resources they don't need. That's wrong. The cheapest migration isn't the one with the least effort upfront—it's the one that aligns with what the application actually needs to run efficiently in the cloud. Let's get into it.

Step 1: Kill the Zombies Before You Move Anything

Before you even think about rehosting, replatforming, or refactoring, do a brutal inventory. AWS defines 'zombie applications' as those with average CPU and memory usage below 5 percent over 90 days, and 'idle applications' as those with 5-20 percent usage over the same period. Both are prime candidates for retirement. In our experience, most organizations discover at least a handful of these—apps that nobody uses but that still consume licenses, power, and eventually cloud resources. The act of retiring them is the cheapest possible migration: it costs nothing and saves money immediately. AWS explicitly includes 'retire' as one of its 7 Rs for a reason. So before you migrate anything, hunt down the zombies. It's the easiest cost win you'll ever get.

Step 2: Match the Strategy to the App, Not the Other Way Around

Once the zombies are gone, you have to decide what to do with the survivors. The classic mistake is defaulting to rehost (lift-and-shift) because it's the fastest path. But rehosting an app that needs constant scaling is like moving a dinosaur into a petting zoo—it doesn't adapt. Replatforming, which makes minor optimizations like moving to a managed database, is often a sweet spot. In a Red Hat survey, replatforming was the most common 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. That's telling. For most apps, replatforming delivers cloud benefits without the pain of a full rewrite. Refactoring, on the other hand, is the most complex and costly strategy—AWS cautions against it for large migrations because it modernizes during the move. So our rule of thumb: rehost only for short-lived or simple workloads, replatform for the majority, and refactor only when the app is critical and you have the appetite.

Step 3: Use the 7 Rs as a Cost Filter

AWS defines seven strategies: Retire, Retain, Rehost, Relocate, Repurchase, Replatform, and Refactor. Each has a different cost profile. Let's compare them in terms of effort and potential savings.

As the table shows, rehost is cheap to start but often costs more in the long run because you're not using cloud-native features like auto-scaling or serverless. Replatform and refactor offer better savings but require more effort. The key is to match the strategy to the app's actual needs—and to be honest about which apps are worth the investment.

Step 4: Build a FinOps Team Before You Flip the Switch

Once you start migrating, costs can spiral. Flexera's 2025 report found that 84% of organizations struggle to manage cloud spend—it's the top challenge. And wasted spend on IaaS and PaaS rose to 29% in 2026, the first increase after five years of decline. That's a lot of money going down the drain. The fix is process, not just technology. Flexera found that 60% of organizations use managed service providers and 59% are expanding their FinOps teams to regain control. By 2026, 63% have a dedicated FinOps team. If you don't have one, start now. A FinOps team can track unit economics—49% of organizations already use that to link cloud cost to business outcomes. Without that oversight, you'll be flying blind.

Step 5: Optimize Continuously, Not Just at the End

Migration isn't a one-shot deal. The Azure migration framework has four stages: Assess, Migrate, Optimize, and Monitor. Optimize and Monitor are often skipped, but that's where the savings live. After migration, you should be right-sizing instances, turning off idle resources, and considering serverless for spiky workloads. Serverless, as Red Hat describes it, is event-driven and metered on demand—an idle function costs nothing. That's a powerful lever for cost optimization. Also, keep an eye on repatriation: Flexera 2025 found that only 21% of workloads have been repatriated, meaning the vast majority are staying in the cloud. So you're likely in it for the long haul—make sure you're running efficiently.

What Can Go Wrong

The biggest danger is under-assessing the application portfolio. DigitalOcean warns that missed dependencies can derail a migration. You think you're moving one app, but it secretly talks to five others. That leads to budget overruns and security vulnerabilities. Another pitfall is treating 'lift and shift' as a permanent state. It's fine as a first step, but if you never modernize, you'll be stuck with high bills and poor scalability. And don't forget security: under the Azure shared responsibility model, you always own your data and access management. Moving to the cloud doesn't absolve you of that.

One concrete example: a customer consolidated 80 SAP systems and achieved 30% cost savings with a cloud-native transformation (AWS). That didn't happen by lifting and shifting—it happened by refactoring and consolidating. If you can do that, great. But for most of us, the pragmatic path is replatforming and retiring waste.

The One Thing to Remember

The cheapest migration is the one that retires what you don't need, replatforms what you can, and refactors only what's worth it. Don't let lift-and-shift be your default. It's a trap.

Sources

• DigitalOcean - https://www.digitalocean.com/resources/articles/cloud-migration-strategy
• AWS Prescriptive Guidance - https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/migration-strategies.html
• Red Hat - https://www.redhat.com/en/blog/how-should-you-modernize-your-applications
• 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/
• Microsoft Learn - https://learn.microsoft.com/en-us/training/modules/design-migrations/3-describe-azure-migration-framework