The Short Answer
VMware's 2026 pricing model — subscription-only licensing, bundled SKUs, multi-year terms and core-count minimums — has pushed renewal quotes to multiples of prior contracts, but the hypervisor bill is not the real lock-in.
The real hostage is your backup history: years of restore points in a VMware-only format that conventional backup tools cannot restore anywhere else. An exit plan has to move the backup lineage, not just the VMs.
What actually changed
Since Broadcom's acquisition closed, the commercial model has been rebuilt around four mechanisms, each of which moves money in the same direction:
- Perpetual licences are gone. The licence you owned became a subscription you rent. Support renewals on perpetual licences were discontinued, which converts "we can sweat this asset" into "we must renew or run unsupported."
- Products became bundles. Point products were folded into larger suites. If you ran vSphere and nothing else, the entry ticket now includes components you never deployed — priced in.
- Core minimums set the floor. Licensing is per core with minimum counts per CPU. Small hosts pay for cores they do not have; the floor, not your hardware, sizes the bill.
- Multi-year terms front-load commitment. The discount sits on the multi-year subscription; the multi-year subscription removes your negotiating leverage at precisely the moment prices are moving.
The result, reported consistently across industry surveys and public accounts since 2024: renewal quotes commonly land at two to five times the prior contract, with worse outliers for small estates caught by bundle and core minimums. Specific numbers vary by estate and negotiation — get your own quote early — but the direction has not varied.
Why the renewal maths gets worse, not better
A renewal negotiation is priced on your alternatives. If the realistic alternative is "migrate the estate in the four months before the contract lapses," you have no alternative, and the quote reflects that. Each multi-year renewal also resets the clock on optionality: the skills, tooling and platform decisions that would make an exit cheap atrophy while the subscription runs. Teams that wait for the renewal that finally hurts enough discover that the hurting renewal is also the worst possible moment to start building an exit.
The organisations that negotiate well do the opposite: they build a credible, tested exit path while they still intend to renew. Sometimes the exit gets exercised; more often the credible threat of it changes the quote.
The part nobody prices in: your backup history
Retention obligations don't reset because you migrated
Compliance frameworks and internal policy define how far back you must be able to restore — commonly three, five or seven years. Those obligations attach to the data, not the hypervisor. Migrate every VM tomorrow and the requirement to restore last March's finance server is exactly what it was.
The zombie cluster
Conventional backup products store recovery points in formats restorable only into the platform that produced them. So the standard exit plan grows a quiet appendix: keep a minimal vSphere cluster — licensed, patched, supported — alive for years, purely as a restore target for old backups. That appendix is a recurring VMware bill inside your VMware exit. It is the hostage payment, formalised.
Why "restore then convert" fails at audit time
The workaround usually proposed is to restore old points into VMware and convert them on demand. At audit or incident time, that means a multi-hour, multi-tool pipeline — restore, convert, boot, hope — executed under the worst possible conditions, dependent on infrastructure you were trying to switch off. A recovery capability you cannot rehearse cheaply is not a capability; it is a story.
What backup-lineage portability looks like
The structural fix is to take the restore points out of the hypervisor's format entirely. When recovery points live in a platform-neutral repository and the restore path can convert on the way out, the question "can we still restore the old VMware backups?" stops depending on VMware existing. Yesterday's VMware backup restores onto CloudStack tomorrow — same lineage, same retention clock, no zombie cluster. This is precisely how Sendense treats backup history across platforms: the history travels with the workload, and the destination platform inherits protection on day one.
Sequencing the exit
None of this argues for a panicked migration. It argues for sequencing: prove restore portability first (it is a one-afternoon test), replicate a pilot group second, and only then put a date against the estate — with the renewal calendar, not after it. We maintain a full phase-by-phase checklist in the VMware exit solution, and the engineering-side pitfalls are covered in VMware to CloudStack migration: what breaks and how to plan for it.
FAQ
Why did VMware costs rise so sharply after the Broadcom acquisition?
Perpetual licences were discontinued in favour of subscription-only terms, products were consolidated into larger bundles, and minimum core counts were introduced. Customers who previously licensed exactly what they used now buy bundled subscriptions sized by rules they don't control — and renewal quotes at multiples of prior contracts have been widely reported across the industry.
Can I keep restoring old VMware backups after migrating away?
Only if something can read them. Conventional backup formats restore only into the platform they came from, which forces a choice: keep a minimal vSphere environment alive as a restore target, or store recovery points in a platform-neutral format that can restore to the new platform. The second option is what makes a clean exit possible.
Is migrating off VMware cheaper than renewing?
It depends on the renewal quote, the estate size and the migration cost — which is why the honest first step is the maths, not the migration. What consistently changes the equation is the backup question: if exit requires keeping licensed VMware infrastructure alive for years of retention, the exit business case quietly erodes. Lineage portability removes that line item.
What should I do before my next VMware renewal?
Three things: get the renewal quote early so the comparison is real; inventory which workloads could run on an alternative platform; and test-restore a current VMware backup onto that platform. The third step is the one most teams skip, and it is the one that converts an exit from a slide deck into an option you can actually exercise.