Broadcom stopped selling perpetual VMware licenses after the acquisition closed. Existing perpetual licenses still function. Existing support contracts run their course. Then the customer faces a binary choice: convert to Broadcom subscription at materially higher annual cost, or migrate off VMware to an alternative platform. Three years on, the migration economics have changed enough that "stay on VMware" is no longer the obvious answer.
Key Takeaways
- Perpetual VMware licenses continue to work; the change is at support contract expiry when security updates and feature releases stop.
- Migration to Broadcom VVF subscription typically costs 50 to 100 percent more annually than the perpetual support that preceded it; VCF costs 200 to 350 percent more.
- Five credible alternatives at enterprise scale: Nutanix, Proxmox VE, OpenStack with KVM, hyperscaler-native virtualisation, and Red Hat OpenShift Virtualization.
- Migration timelines run 2 months to 30 months depending on estate size; the work is real but tractable.
- Most enterprises plan a transition within 4 years of perpetual support expiry; staying on un-supported perpetual indefinitely creates compounding technical debt.
What the perpetual position actually means now
Perpetual VMware licenses sold before Broadcom closed the acquisition (early 2024) continue to function indefinitely. ESXi keeps running. vCenter keeps managing. vSphere features keep working. Production workloads do not stop on any contractual or technical date.
The change happens at support contract expiry. Without an active support contract:
- Security patches stop. New CVEs are not addressed in your installed version.
- Bug fixes stop. Operational issues require workarounds rather than vendor fixes.
- Feature releases stop. New vSphere versions, vSAN improvements, NSX features are unavailable.
- Hardware compatibility lists do not extend. New server hardware may not be supported.
- Vendor support cases are not accepted. Production troubleshooting falls fully on the customer.
Most enterprises ran their perpetual support contracts through 2024-2026. By the time of writing in 2026, the choice is concrete: convert to Broadcom subscription, find third-party support that extends the perpetual life (limited and contested), or migrate off VMware.
The cost comparison: perpetual support vs Broadcom subscription
For a 1,000-core estate, the rough cost picture in 2026:
| Scenario | Annual cost (indicative) | 3-year total |
|---|---|---|
| Pre-Broadcom perpetual support (2023 baseline) | 50,000 to 80,000 USD | 150,000 to 240,000 USD |
| Broadcom VVF subscription (3-year, negotiated -30%) | 95,000 USD | 285,000 USD |
| Broadcom VCF subscription (3-year, negotiated -30%) | 245,000 USD | 735,000 USD |
| Nutanix Acropolis migration (Year 1: project cost; Years 2-3: subscription) | Year 1: 200K project + 80K subscription. Years 2-3: 80K subscription | 440,000 USD |
| Proxmox VE migration (Year 1: project; Years 2-3: optional commercial support) | Year 1: 150K project + 20K support. Years 2-3: 20K support | 210,000 USD |
The numbers are deployment-dependent and the table is illustrative. The pattern across actual engagements: Broadcom VVF is roughly twice the cost of pre-Broadcom perpetual support; Broadcom VCF is roughly four times. Migration to Nutanix or Proxmox is upfront-heavy but year-2-and-onwards cheaper.
The five credible alternatives at enterprise scale
1. Nutanix Acropolis Hypervisor (AHV)
Best fit for enterprises previously running VMware on hyperconverged infrastructure. Nutanix has invested heavily since the Broadcom acquisition in VMware migration tooling, partner relationships and support models. AHV is included in Nutanix licenses (no separate hypervisor cost). Acropolis Move is a free, supported migration tool. Operational model is similar enough to VMware that team transition is manageable.
2. Proxmox VE
Open source, KVM-based, with Proxmox Server Solutions providing commercial support. Lowest licensing cost: free for the platform itself, optional commercial support around 1,000 EUR per CPU per year. Operational model is more Linux-native than VMware-like; team transition takes longer. Production-ready and used at scale by some European enterprises.
3. OpenStack with KVM
Most flexible, highest engineering investment. Suits organisations that want full control of the platform and have engineering depth. Distributions from Canonical, Red Hat (OpenStack Platform), Mirantis, and others provide commercial support. Production-grade but operationally heavier than VMware or Nutanix.
4. Hyperscaler-native virtualisation
Azure Stack HCI for on-premises Microsoft alignment, AWS native services for cloud-first migrations, Google Cloud VMware Engine for transitional VMware-compatibility cases. The fit is strongest for enterprises already committed to a single cloud platform. Native services replace virtualisation entirely in many cases (containers, managed services).
5. Red Hat OpenShift Virtualization
Best fit for enterprises whose primary platform is Kubernetes (OpenShift) and who run a few residual VM workloads. OpenShift Virtualization runs VMs as Kubernetes resources alongside containers. Operational model is Kubernetes-native; not the right fit for organisations that are not already on OpenShift.
Migration timelines and risk profile
Migration timelines depend on estate size, application complexity and team capacity. Across the engagements we have advised on, typical patterns:
- Small estates (under 100 VMs): 2 to 4 months migration timeline. Single team, single platform target, single cutover wave.
- Mid-size estates (500 to 2,000 VMs): 6 to 12 months. Multiple migration waves, shared engineering team across waves, dev/test first then production.
- Large enterprise estates (5,000+ VMs): 18 to 30 months. Multi-team, multi-region, multi-application waves. Critical production deferred to last; rollback plans documented for each wave.
The risk profile of migration has standard data-centre-platform-change components: backup tooling adjustment, monitoring and observability tool reconfiguration, automation script updates, application compatibility validation, network architecture review, and team training. Each is addressable. Most successful migrations document each risk and assign mitigation owners before kicking off.
The decision framework
The migration decision rests on five questions.
1. What is the 5-year total cost difference? Model Broadcom subscription against the migration project plus the alternative's 5-year run cost. Most estates above 500 cores show a meaningful saving on migration once the multi-year window is included.
2. What is the engineering capacity? The migration is real engineering work. If the team does not have capacity, the migration is contracted out (more upfront cost) or deferred (more Broadcom subscription cost). The right answer depends on your team and your time horizon.
3. What is the application risk profile? Some workloads migrate cleanly to any alternative. Some have VMware-specific dependencies (VMware Tools features, NSX integration, vSphere API integration) that need rework. Inventory before commitment.
4. What is the operational model preference? Nutanix is operationally similar to VMware. Proxmox is more Linux-native. OpenStack is engineering-heavy. Hyperscaler-native shifts the model entirely. Pick the platform whose operational model matches your team's strengths.
5. What is the strategic direction? If the organisation is moving toward cloud-first, hyperscaler-native may be the right answer regardless of cost. If the organisation is committed to on-premises, Nutanix or Proxmox is the typical choice. The decision needs to align with the broader infrastructure strategy.
Modelling the VMware migration decision?
The right answer depends on estate size, application mix, engineering capacity and strategic direction. Independent Broadcom VMware advisory models all alternatives, runs the cost case and recommends the path with the lowest 5-year TCO at acceptable operational risk.
Book a 30-minute scoping callFrequently asked questions
What happens to my VMware perpetual licenses under Broadcom?
Perpetual VMware licenses sold before the Broadcom acquisition continue to function indefinitely. The change is at support contract expiry: once your support lapses, you no longer receive security patches, bug fixes or feature updates.
What is the true cost of moving from VMware perpetual to Broadcom subscription?
For a 1,000-core estate previously on perpetual with annual support of approximately 50,000 to 80,000 USD, the move to VVF subscription costs approximately 95,000 to 135,000 USD per year. The move to VCF costs approximately 245,000 to 350,000 USD per year.
What are the credible alternatives to staying on VMware in 2026?
Five alternatives are credible at enterprise scale: Nutanix Acropolis Hypervisor, Proxmox VE, OpenStack with KVM, hyperscaler-native virtualisation, and Red Hat OpenShift Virtualization.
How long does a migration from VMware to Nutanix or Proxmox take?
Migration timelines depend on estate size. Small estates (under 100 VMs) migrate in 2 to 4 months. Mid-size estates (500 to 2,000 VMs) typically run 6 to 12 months. Large enterprise estates run 18 to 30 months.
What are the risks of migrating away from VMware?
Operational risks include integration tool changes, application compatibility, team skill transition, and the migration project itself. Each is addressable. The migration risk profile is comparable to any major data centre platform change.
Is staying on perpetual VMware viable long-term?
For 2 to 4 years, yes, depending on patch cadence requirements. Beyond that, the absence of security updates and feature releases creates compounding technical debt.