Your VMware renewal: four options, costed
Infrastructure
Since Broadcom acquired VMware, the question is no longer whether your virtualisation bill will rise, but by how much — and what you intend to do about it. Perpetual licences are gone: VMware is now sold by subscription only, billed per processor core, with a floor of sixteen cores per processor whether you use them or not.
For an estate of three to ten hosts — the size we most often meet in the region's banks, telecom operators and oilfield service companies — published accounts report bills two to three times higher on the move to subscription. This is no longer a budget line you renew without reading it.
What actually changed
- No more perpetual licence. What you once bought is now rented. Not renewing does not switch your virtual machines off, but it cuts you off from security patches and support — that is, from the right to stay in production with any peace of mind.
- Per-core billing, sixteen-core floor. A dual-socket server with eight-core processors is billed as if it had thirty-two cores. Estates built on many small hosts are hit hardest, and those are usually the oldest ones.
- Bundling. Components are sold in packages: you pay for building blocks you had no plan to run.
The four possible paths
1. Renew with Broadcom
The simplest and the most expensive. It holds up when your platform is deeply integrated — NSX, vSAN, in-house automation — and a migration would cost more over three years than the overcharge. Provided you actually run that calculation rather than assume it: get the quote before you decide, not after.
2. Stay on VMware, but through a managed provider
A provider buying at scale resells capacity at a price you would not obtain alone. You keep your skills and your procedures. In exchange you hand over part of the control — and you need to look closely at where your machines actually run, which is not a neutral question for an institution subject to data-residency requirements.
3. Migrate to Nutanix AHV
Today this is the most travelled exit for organisations that want a comparable enterprise stack without re-architecting everything: the AHV hypervisor is included, and management depth is of the same order. The price is a change of tooling for your teams, and a cutover to plan machine by machine.
4. Migrate to Proxmox VE, Hyper-V or OpenShift Virtualization
Proxmox VE is markedly cheaper and its growth is striking; it is also the option that leaves you most on your own, because the integrator ecosystem and contractual spare-part landscape are not established everywhere yet. Hyper-V makes sense when you are already heavily invested in Microsoft. OpenShift Virtualization is only worth it if you were heading for containers anyway.
The question nobody asks: do your backups follow?
This is what derails migrations. Your restore points were taken on ESXi; they do not restore as they are onto another hypervisor. Before settling on a choice, check three things with your backup tool — Veeam, Veritas NetBackup, whatever you run:
- is the target hypervisor supported by the version you own, or only by a paid upgrade;
- what becomes of the history already stored: does it remain restorable after the cutover, and for how long;
- has a real restore been tested — not described in a datasheet, tested on your site, stopwatch in hand.
A hypervisor migration that succeeds technically but leaves you with three years of unreadable archives is a failure.
What this changes in Central Africa
Two local factors weigh heavily on the decision and appear in no international comparison. The first is supply: renewing hosts to cut the number of billed cores assumes delivery lead times and a spare-part stock reachable from Brazzaville or Pointe-Noire. The second is skills: changing hypervisor means training your administrators, and planning for the period during which they will be slower on an incident than they were before.
Where to start
- Produce the exact inventory: hosts, processors, cores per processor, contract end dates.
- Ask for the renewal quote. Without that figure, no comparison means anything.
- List what ties you to VMware: features genuinely used, scripts, backup and monitoring integrations.
- Test a restore before deciding, not after the cutover.
We run this assessment in two to five days, with an audit report and a prioritised action plan. The conclusion is not always "migrate": sometimes it is "renew, but on two fewer hosts".
Sources
- VMware Licensing in 2026: How Costs Are Reshaping IT Strategy — Tasrie IT Services
- Navigating VMware Licensing Changes — Marco
- Ex-VMware customers explain why they migrated to Nutanix — The Register
- VMware in the post-Broadcom era — Cloud Magazin