Leaving VMware
Broadcom's licensing changes have turned VMware renewal from a routine line item into a board-level cost question for many mid-sized estates. The renewal quote arrives multiples higher, the SKUs you ran are bundled away, and the deadline does the negotiating.
There are credible paths off, and one credible path that stays. Which one is right depends on estate size, staff skills, timeline, and how much of the VMware feature set you actually use. Migrating a hypervisor is a project, not a purchase; anyone who tells you otherwise is selling something.
What actually determines the answer
| Factor | Why it matters |
|---|---|
| Estate size and complexity | Sub-100-VM estates can move in a quarter. Larger or DR-entangled estates need phased migration planning. |
| Staff skills | Your team's operational muscle memory is a real asset with a real replacement cost. |
| Feature dependence | If you lean on DRS, NSX, or SRM, list what actually breaks before choosing a destination. |
| Timeline versus renewal date | A migration started under deadline pressure costs more. A short-term renewal to buy migration time is sometimes the cheapest option on the table. |
The paths, with their trade-offs
Rehost on new hardware, migrate hypervisor
When your hardware refresh is due anyway and you want one project, not two.
Trade-off: The biggest single change, but it avoids paying to migrate twice. New hosts run the destination hypervisor from day one.
Configured BOM
R770 - 60 VM virtualization host
- CPU 2× Intel Xeon 6 processor, 48 cores each
- Memory 8× 64 GB DDR5 RDIMM (512 GB total)
- Storage 6× 3.84 TB NVMe read-intensive SSD
- Network Dual-port 100 GbE adapter
- Support 4-year ProSupport Plus, next business day
HPE VM Essentials on ProLiant
When you want a supported, cost-predictable KVM-based stack from a tier-one vendor.
Trade-off: A younger ecosystem than VMware's. Test your backup and monitoring integrations before committing.
Configured BOM
DL380 Gen12 - 60 VM virtualization host
- CPU 2× Intel Xeon 6 processor, 48 cores each
- Memory 8× 64 GB DDR5 RDIMM (512 GB total)
- Storage 6× 3.84 TB NVMe read-intensive SSD
- Network Dual-port 100 GbE adapter
- Support 4-year HPE support, next business day
Stay on VMware, renegotiate
When your feature dependence is deep and the migration cost exceeds the renewal delta.
Trade-off: Nobody's favorite answer, but sometimes the honest one. Right-sizing cores and dropping unused bundles can close part of the gap.
Run your own numbers first: VM sizing calculator →
What deployment involves
Typical scope: destination platform build, backup and monitoring re-integration, pilot workload migration, then phased cutover by maintenance window.
Plan the exit of the old cluster explicitly; parallel-running two hypervisors is where these projects quietly blow their budgets.