Delaying a VMware Renewal Has a Cost Too
- Natalie Stipan
- 409 views
Staying put on VMware renewals may feel safe, but it cedes budget and platform control. Smaller estates can often migrate in months, not years.

Cloud licensing has come up in nearly every customer conversation I've had this year. The talk usually starts with a renewal quote that's hard to swallow and quickly turns into the question every IT leader asks next: what are our options?

Broadcom's acquisition of VMware is behind much of this. The headline numbers make it hard to ignore. AT&T's renewal increase of 1,050% has been widely quoted, and Tesco's plan to move 40,000 workloads off VMware has become a reference point for what a large-scale exit looks like. Those are the outliers, though. Most of the organisations I speak with don't have the scale of either business.
Why most teams end up accepting the terms
Large enterprises have leverage. They can negotiate hard, phase their exits and fund dedicated migration teams. Mid-sized organisations usually can't do any of that. They're left with per-core subscriptions, bundled products they didn't ask for and an annual renewal that keeps climbing. Signing the renewal is the path of least resistance, so it's often where the decision stops.
I understand the logic. A migration takes time, pulls people away from other projects and carries real risk to production systems. Renewing for another year feels like the cautious option. The trouble is that it isn't really a neutral choice. Each renewal resets the same negotiation with the same vendor, and the price tends to move in one direction.
Staying put is a decision, not a holding pattern
Here's the thing: choosing to stay on the current platform is a valid option, but it doesn't give you control. You still don't set the price, and you still don't decide how the platform evolves or which bundles you're forced to buy. What you're really doing is deferring the decision and hoping next year's quote is more manageable.
That hope is the part I'd push back on. If the cost of staying rises each cycle, the cost of leaving rises too, because the longer you wait, the more workloads, integrations and dependencies pile up. Delay doesn't make the migration smaller. It usually makes it harder and gives the vendor more time to set the terms.
Why smaller estates can move faster than they expect
The good news for smaller organisations is that scale cuts both ways. Tesco's estate is measured in tens of thousands of workloads. A mid-sized business might be running a few hundred. With that footprint and the right plan, a migration can realistically be measured in months rather than years. That's a very different proposition from the multi-year programmes that dominate the headlines.
The planning is where I think most of the success comes from. Before anything moves, I'd push teams to run a detailed discovery phase. You need a clear inventory of what's running where, and an honest map of what each workload depends on: network paths, authentication, storage, backup jobs, and the applications that quietly rely on all of them. Teams tend to underestimate the dependencies they haven't documented. Discovery is what surfaces them before they cause an outage.
Start small and protect the sensitive workloads
Once discovery is complete, I'd recommend starting small. A greenfield project on a second platform is a sensible first step. The new environment gets built and tested without touching production, and the team learns how the target platform behaves under real conditions. Less critical workloads can follow, giving staff time to build confidence and refine their runbooks.
Your most sensitive workloads should stay where they are until the team is confident in the new environment. That approach limits unnecessary downtime and risk. It also means the migration can pause or change direction without becoming a crisis, which matters when budgets and timelines shift mid-project.
What to watch next
My read is that renewal quotes will keep shaping these conversations through the next few cycles. IT leaders who treat the current renewal as a deadline for a decision, rather than a routine invoice, will have more room to choose their own path. Start with a discovery inventory now, even if you don't plan to move anything this year. Once you know what you run and what depends on what, the question of whether to stay or leave becomes a costed decision you can actually make.