When Broadcom acquired VMware in late 2023 and announced the discontinuation of perpetual licence sales, it created one of the most significant forced transitions in enterprise infrastructure history. Organisations that had built their virtualisation strategy on owned, perpetual VMware licences — often representing years of capital investment — were told that the licensing model underpinning their infrastructure would no longer be supported.
Two years on, the implications of that decision continue to unfold. This guide addresses the questions that enterprise buyers ask most frequently: What are the actual support end dates for perpetual VMware products? What happens after support ends? And what are the realistic paths forward for organisations that don't want to simply capitulate to Broadcom's subscription mandate?
For broader context on the changes Broadcom has made to the VMware portfolio, see our complete VMware Broadcom licensing guide.
The Perpetual Licence Landscape
VMware perpetual licences were sold with two components: the licence itself (owned permanently) and a support and subscription (SnS) contract that provided access to updates, patches, and technical support. The perpetual licence has no expiry date. The SnS contract does.
Broadcom's policy shift affects these components differently. Perpetual licences remain legally valid — Broadcom cannot revoke licences that were legitimately purchased. However, Broadcom has made clear that it will not sell new perpetual licences, will not renew SnS contracts for perpetual licences on an indefinite basis, and has established end-of-support dates for legacy VMware product versions.
The practical consequence is that perpetual licence holders face a time-limited window during which they continue to receive security patches and technical support. After that window closes, they are running software that will not be updated — a growing security and compliance risk, particularly for regulated industries.
VMware Perpetual Product Support Timeline (Illustrative)
What "End of Support" Actually Means
End of support for VMware perpetual products means the cessation of security patches and critical bug fixes. It does not mean the software stops functioning. Organisations running perpetual VMware vSphere, vCenter, or vSAN in an end-of-support state can continue to operate their existing infrastructure — the hypervisor will not stop working on a predetermined date.
What end-of-support does mean, in practice, is significant operational risk accumulation. Newly discovered security vulnerabilities will not be patched. Compatibility with new hardware will not be tested or certified. Integration with other vendor products (backup solutions, monitoring tools, hyperconverged platforms) may degrade as those products update their VMware compatibility matrices. Regulatory frameworks requiring "supported software" will flag the infrastructure as non-compliant.
Compliance Note: Regulated industries face particular exposure. Frameworks including PCI-DSS, HIPAA, SOX, and ISO 27001 typically require that production infrastructure runs on vendor-supported software versions. Running perpetual VMware beyond end-of-support in regulated environments may require compensating controls, formal risk acceptance, or risk triggering audit findings.
The timeline for acceptable risk varies by organisation. Some enterprises have operated on end-of-support infrastructure for 12–18 months without incident while executing planned migrations. Others, particularly in financial services and healthcare, face regulatory pressure that makes even brief exposure to unsupported software unacceptable.
The Three Paths Forward
Path 1: Migrate to VCF Subscription
Broadcom's preferred path is migration to VMware Cloud Foundation (VCF) or VMware vSphere Foundation (VVF) subscriptions. This path maintains the highest VMware feature parity and the lowest application compatibility risk — existing workloads continue running on familiar hypervisor technology with minimal disruption.
The cost, however, is substantial. VCF subscription pricing represents a significant increase over historical perpetual SnS costs for most organisations — the transition typically results in a 3–8× increase in annual infrastructure software cost. The magnitude depends on the original perpetual licence cost, the server estate size and core count, the VCF tier required, and the negotiated discount.
For organisations where VMware is genuinely the optimal platform — deep integration with VMware-specific features, limited migration capability, high workload sensitivity — the subscription path may be the correct choice, provided the commercial terms are negotiated aggressively. See our guide on negotiating Broadcom VMware contracts for the tactics that deliver the best outcomes.
Path 2: Migrate to Alternative Platforms
The most common alternative for departing perpetual VMware users is migration to one of several competing platforms. The primary options are Nutanix AOS (a hyperconverged platform with its own hypervisor, AHV), Red Hat OpenShift Virtualisation (KVM-based virtualisation integrated into the OpenShift container platform), Microsoft Hyper-V or Azure Stack HCI, and public cloud migration (AWS, Azure, GCP).
Each alternative has a different cost profile, migration complexity, and feature coverage. Nutanix is the most direct VMware competitor for traditional virtualisation workloads. Red Hat suits organisations already invested in the OpenShift ecosystem. Microsoft Hyper-V is attractive for organisations with strong Microsoft licensing relationships. Public cloud migration is the highest-disruption option but eliminates on-premises infrastructure cost entirely for migrated workloads.
| Alternative | Best For | Migration Complexity | Cost vs VCF |
|---|---|---|---|
| Nutanix AOS/AHV | Traditional VM workloads, HCI replacement | Medium | 20–40% lower |
| Red Hat OpenShift Virt | Container + VM mixed estates, OpenShift users | High | Variable — often lower |
| Microsoft Hyper-V/HCI | Microsoft-heavy environments, Azure-integrated | Low–Medium | Often included in existing licensing |
| Public cloud (AWS/Azure/GCP) | Dev/test, disaster recovery, flexible workloads | High | Variable — OpEx model |
| VCF/VVF Subscription | Full VMware parity required, risk-averse migration | Low | 3–8× SnS cost increase |
Path 3: Extended Perpetual Operation with Risk Acceptance
Some organisations — typically those with isolated, non-internet-connected infrastructure, or those in industries with lower regulatory pressure — choose to continue operating perpetual VMware beyond formal end-of-support while executing a longer-duration migration programme. This approach requires formal risk acceptance, documented compensating controls, and a defined migration timeline.
It is not an indefinite strategy. The security risk accumulation from running unsupported hypervisors accelerates over time as vulnerability databases grow and threat actors specifically target known-unpatched systems. Most organisations using this path treat it as a 12–24 month bridge to one of the two substantive alternatives.
Decision Framework for Perpetual Licence Holders
The decision between these paths should be driven by four factors: migration complexity and cost for your specific workload portfolio; the total cost comparison between VCF subscription and alternative platforms over a 3–5 year horizon; your regulatory compliance requirements and the tolerance for any period of unsupported software; and the strategic direction of your infrastructure — cloud migration trajectory, on-premises investment appetite, and vendor relationship management priorities.
The most common mistake is treating this as primarily a technical decision. The commercial and strategic dimensions are at least as important. An organisation with strong cloud migration momentum may prefer to use the VMware transition as an accelerant for cloud adoption rather than investing in a like-for-like replacement. An organisation that has heavily customised VMware-specific capabilities may find that only VCF maintains the full feature set required.
The Role of Independent Advisory Firms
The perpetual licence transition is one of the scenarios where independent licensing advisory adds most value. The decision involves simultaneous assessment of technical migration feasibility, commercial negotiation with Broadcom and alternative vendors, contract structuring for the chosen path, and risk management during the transition period.
Specialist firms like Redress Compliance provide comprehensive VMware transition support — from initial decision framework development through commercial negotiation and contract execution. Their combination of former vendor commercial expertise and active client portfolio intelligence provides insights that internal teams cannot develop independently.
Independent advisors also provide a valuable function in the negotiation itself: organisations that engage specialist advisors for Broadcom VCF negotiations consistently achieve 15–25% better pricing than those negotiating independently, which can change the economics of the VCF path substantially. For organisations where the decision is finely balanced between VCF and an alternative, the savings achievable with advisory support can tip the analysis.
Protecting Your Existing Investment
Regardless of which path you choose, perpetual VMware licence holders should take three immediate steps. First, document your perpetual licence entitlements thoroughly — including product versions, quantities, and associated SnS contract history. These records will be important whether you are negotiating with Broadcom for transition credits or evaluating alternative platforms that may offer licence conversion incentives.
Second, understand your current SnS contract status. Are you in an active renewal period? Have you received notification of end-of-support for your specific product versions? The answer determines your timeline and urgency.
Third, initiate alternative evaluation before your commercial urgency becomes Broadcom's negotiating leverage. The worst position in any Broadcom negotiation is needing to sign because you have no alternative and your support is ending in 60 days. Starting the evaluation process 12 months before your decision deadline changes everything.
For a deeper analysis of the changes Broadcom has made and the full context of the transition, read our detailed review of Broadcom VMware changes since the acquisition. For cost modelling of the migration alternatives, our guide on VMware alternatives and migration costs provides the commercial framework most useful for this analysis.
Our software licensing advisory practice and VMware Broadcom advisory practice support enterprise organisations at every stage of this transition — from decision framework development to commercial negotiation and contract execution.