"Leave VMware" is the loudest threat in every Broadcom renewal conversation. The migration paths are real but uneven. This article covers the four alternative platforms most customers actually deploy — Nutanix AHV, Microsoft Hyper-V with Azure Local, Red Hat OpenShift Virtualization, and Proxmox — with honest economics, workload fit, and the negotiation leverage migration creates even when it isn't executed.
"Leave VMware" is the loudest threat in every Broadcom renewal conversation. The migration paths are real, but the gap between threat and execution is wider than most customers acknowledge. Of the 340+ engagements our team has worked since the acquisition, roughly one in five customers executed a partial migration, and one in twenty executed a full migration within twenty-four months. The rest negotiated. The four alternatives below are the migration targets we see most often in production.
The most mature commercial alternative for hyperconverged customers. Nutanix bundles its AHV hypervisor with the AOS storage platform — meaning customers who replace a VMware vSphere + vSAN deployment with Nutanix eliminate the hypervisor licence entirely while gaining a comparable hyperconverged stack. Migration from vSphere is well-tooled (Nutanix Move handles VM conversion), and the operational model is closer to vSphere than any other alternative. Costs run higher than baseline Hyper-V or Proxmox but materially below VCF for equivalent functionality. The trade-off is a single-vendor lock-in to Nutanix, which has its own commercial dynamics under Bain Capital ownership.
Built on KubeVirt and KVM, OpenShift Virtualization is the migration target most often cited by customers with a Kubernetes-first strategy. The thesis is that the customer is moving to containers anyway, and OpenShift Virtualization lets the residual VM workloads sit on the same orchestration platform as the modern containerised workloads. The operational model is heavier than vSphere — OpenShift carries its own learning curve — but the per-core economics are favourable, particularly when the customer has existing Red Hat subscriptions. The pattern works best for engineering-led organisations with platform teams that can absorb the operational complexity.
The decision rests on workload mix, team skill, and the credibility of the timeline. We model all four.
Hyper-V has been a credible enterprise hypervisor for years and is the natural alternative for Windows-centric estates. Microsoft's investment in Azure Local (formerly Azure Stack HCI) extends Hyper-V into a hyperconverged platform with Azure integration. Customers with Windows Server Datacentre licences already in place often find the migration economics compelling — the hypervisor licence is effectively bundled, the management plane (SCVMM, System Center) is familiar to existing teams, and Azure integration creates a hybrid story that VMware has struggled to match. The weakness is Linux workload tooling, which has improved but remains less mature than VMware's.
Proxmox has matured into a legitimate enterprise option for cost-sensitive workloads. Built on KVM and LXC with a ZFS-based storage layer, Proxmox offers a subscription model that is materially cheaper than any commercial alternative. The trade-off is enterprise support depth: Proxmox's vendor support organisation is smaller, and enterprise customers typically procure third-party support contracts from regional partners. Deployment is most successful where the customer has internal Linux skill, where workload tolerance for downtime is moderate, and where the procurement priority is unit-economic discipline.
Includes the full alternatives comparison and migration cost benchmarks.
Migration is not free. Across our engagements, the realistic all-in cost of migrating a non-trivial VMware estate — including target platform licensing, tooling, professional services, parallel running, training and the inevitable scope expansion — runs $4,000–$12,000 per migrated VM, with a 12–24 month timeline for estates above 500 VMs. The payback period against Broadcom subscription savings averages 18–30 months. Customers who pencil migration economics without accounting for parallel running and tooling typically underestimate the cost by 40–60%.
That said, the migrations that get executed tend to share three characteristics: a multi-year horizon, an executive sponsor at CIO level, and a clear application-modernisation thesis that justifies the operational disruption. Migration purely as a cost-cutting exercise rarely survives the first major incident. Migration as part of a larger platform strategy — cloud-native, AI infrastructure, edge computing — consistently does.
A real, costed migration plan for a defined percentage of the estate is the single most credible Broadcom negotiation lever. Vague threats are discounted. A board-approved 30% migration plan with named target platform, costed timeline, and an executive sponsor changes Broadcom's commercial position materially. The customers who use this lever most effectively are not the ones who execute the migration — they are the ones who genuinely could.
Our VMware practice is led by former VMware and Broadcom commercial veterans. We work for buyers only.
Weekly compliance intelligence for IT leaders.