VMware Perpetual License End: What Now

VMware sold perpetual licenses for more than two decades. Customers bought the license outright, paid an annual Support and Subscription contract, and ran the software indefinitely with updates and support included as long as SnS remained active. The model was familiar, predictable, and economic for stable workloads with multi-year operating profiles. It is gone.

Within six weeks of the Broadcom acquisition closing in November 2023, perpetual licensing was retired from the VMware catalogue. New purchases moved exclusively to subscription. SnS contracts on existing perpetual entitlements were no longer renewed past the established phase-out dates. Customers running perpetual VMware today face a defined choice: convert to subscription, run unsupported, or migrate off the platform. This guide covers the legal position, the support cliff, and the practical playbook for each of those choices.

The legal position: what perpetual customers still have

Existing perpetual licenses remain valid. Customers who purchased perpetual VMware before the acquisition own those entitlements in perpetuity and can continue running the licensed software indefinitely. Broadcom's retirement of perpetual licensing applies to new sales, not to the rights customers already hold under existing contracts.

What changed is the support model around the licenses. The Support and Subscription contract that customers attached annually to perpetual entitlements has been progressively phased out. In most regions, new SnS sales on perpetual licenses ended in late 2024. SnS renewals on existing contracts have been honoured to the contracted end date but are not being renewed thereafter on perpetual entitlements. The practical effect is that customers can run their existing perpetual licenses but cannot receive updates, patches, or vendor support unless they roll the entitlements into a subscription bundle.

The terms of the original perpetual license agreement are also still in force. Audit rights, geographic-use restrictions, and entitlement counting under the original contract continue to apply. Broadcom has the contractual right to audit perpetual deployments — the change of corporate parent does not affect the audit clauses that were in the original VMware contracts. Customers running perpetual entitlements without active SnS should expect this audit risk to be enforced more rigorously, not less, as Broadcom's compliance organisation grows.

The support cliff

The most immediate consequence for perpetual customers is the loss of vendor support and updates. Three sub-questions matter.

Security patches

VMware historically released security patches for supported releases through SnS. Without active SnS, customers do not receive these patches. For customers running perpetual entitlements on internet-exposed or regulated workloads, the absence of security patches is a material risk that compounds over time. Severity of this risk depends on workload profile — an isolated lab environment has different exposure than a public-facing application.

Functional updates and version progression

New vSphere and related-product releases require an active subscription. Customers running perpetual entitlements are frozen at the last release available under their SnS coverage. As new hardware and modern guest operating systems are released, the perpetual deployment becomes progressively less able to support them. The hardware and guest-OS compatibility matrices stop updating for the customer's frozen version.

Vendor incident support

Without SnS, customers cannot open vendor tickets for production incidents. The practical effect varies by environment — mature operations teams with strong third-party support relationships can manage without vendor support; less mature teams cannot. For Severity 1 production incidents, vendor support is genuinely useful, and its absence is a material operational risk.

Option 1: Convert to subscription

The most common path is to convert perpetual entitlements into a subscription bundle — typically VVF for vSphere-focused customers, VCF for multi-product customers. The conversion involves three commercial elements.

Credit for existing entitlements

Broadcom offers conversion mechanics that credit the perpetual entitlements against the subscription pricing. The credit is real but is typically less generous than customers expect — the conversion arithmetic is structured to encourage the migration to subscription, not to make the customer financially whole on the perpetual investment. Customers should expect to negotiate the conversion credit, not accept the first offer.

Per-CPU to per-core conversion

The conversion arithmetic from per-CPU entitlements to per-core entitlements is governed by a published conversion ratio that has moved across the catalogue's lifetime. Early conversions used eight cores per CPU; later conversions used sixteen cores per CPU. The ratio is the single largest financial variable in the conversion and is negotiable, particularly for larger deals.

Subscription term and pricing

Once converted, the customer is on a subscription term — typically three or five years — at the negotiated per-core price. Renewal pricing for the term after this one is the second-most-important negotiation point, after the conversion ratio.

Option 2: Run unsupported on perpetual

A meaningful subset of customers have chosen to run their perpetual entitlements without active support. The economic case is straightforward — the subscription cost is avoided. The risk case has several components.

Security exposure increases over time as patches are not applied. Hardware and OS compatibility erodes as the frozen version ages. Vendor incident support is unavailable. And the audit-rights position remains in force, with the additional consideration that Broadcom is unlikely to deal generously with non-converted perpetual customers in an audit finding.

This path is viable for customers with three characteristics: workloads that are operationally stable and unlikely to require functional updates; mature internal operations teams that can manage without vendor support; and a realistic timeline to a migration alternative that closes within two-to-three years before the unsupported risk compounds materially.

Option 3: Migrate off VMware

For customers whose subscription economics do not work and for whom unsupported continuation is too risky, the third option is migration to an alternative platform. The realistic alternatives have matured since the acquisition closed.

Hyper-V is the strongest alternative for Windows-centric estates. Nutanix AHV is the strongest hyperconverged alternative for customers seeking VCF-equivalent functionality. OpenShift Virtualization is increasingly viable for Kubernetes-centric organisations. Proxmox is the open-source path receiving significant adoption from cost-pressured customers with capable Linux operations teams. Our complete VMware licensing guide covers the migration options in more detail.

Migration timelines for mid-size environments are typically twelve-to-twenty-four months for Hyper-V, eighteen-to-thirty-six months for Nutanix or OpenShift, and longer for Proxmox at enterprise scale. The economics depend on workload count, application portability, and the cost of operational disruption. Customers planning migration should bridge the period with either subscription conversion at minimum commitment or an unsupported-perpetual bridge, depending on risk tolerance.

The decision framework

The right choice depends on five factors.

Workload risk profile

Higher-risk workloads (security-sensitive, regulated, internet-exposed) bias toward subscription conversion or migration; lower-risk workloads (internal lab, isolated, non-critical) can tolerate the unsupported path.

Internal operations capability

Mature operations teams can manage longer on unsupported perpetual; less mature teams need active vendor support.

Strategic VMware direction

Customers committed to VMware long-term should convert and negotiate hard on the conversion ratio and renewal protection. Customers planning migration should take the path that minimises bridging cost.

Negotiating posture

Customers with substantial leverage — large deal sizes, credible migration alternatives, supportive procurement timing — can negotiate conversion terms materially more favourable than the published defaults. Customers without leverage will pay closer to the published conversion economics.

Audit-risk tolerance

Audit risk on unsupported perpetual is non-trivial and likely to grow. Customers who cannot tolerate this risk should convert; customers who can document their entitlements rigorously can manage the risk under continued perpetual operation.

What perpetual customers should do in the next 90 days

Three actions are appropriate for any customer holding perpetual VMware entitlements that have lapsed or are approaching SnS expiry.

First, document the entitlement position. Reconstruct what was purchased, under which contracts, at which CPU counts, with which transitional arrangements. This is the foundation for any conversion negotiation or audit defence.

Second, model the cost of each option. Subscription conversion at realistic negotiated pricing. Continued unsupported operation with explicit consideration of the operational and security cost. Migration to the alternative platform most appropriate to the estate. The comparison frames the decision.

Third, before engaging Broadcom on conversion, secure independent advisory. The conversion negotiation rewards preparation, and Broadcom's first proposal is rarely the right deal.

The audit-rights position on lapsed-SnS perpetual entitlements

One frequently misunderstood aspect of the perpetual-licensing position is the audit-rights status of entitlements where SnS has lapsed. The misunderstanding is that lapsed SnS removes the customer from the vendor relationship and therefore from audit risk. This is incorrect.

The audit rights in the original perpetual licence contract continue in force as long as the customer continues to run the licensed software. The contract permits Broadcom to audit the customer's compliance with the licence terms. Lapsing SnS does not terminate the licence, does not terminate the contract, and does not terminate the audit rights. A customer running perpetual vSphere five years after SnS lapsed remains subject to the audit-rights clause in the original purchase contract.

The practical posture for Broadcom on lapsed-SnS perpetual customers is, anecdotally, less generous than its posture on customers who have converted to subscription. The compliance team treats lapsed-SnS customers as having declined the vendor's preferred commercial direction; findings tend to be enforced more rigorously, with less negotiation latitude on settlement terms. This is not a stated policy but is the observed pattern in our engagement data.

Bridging strategies: subscription as a bridge to migration

For customers planning to migrate off VMware but unable to complete the migration within the perpetual-SnS-lapse window, a bridging subscription is often the right answer. The pattern is: convert perpetual entitlements to a subscription bundle on the shortest available term (typically three years), use the bridge period to execute the migration, and then exit the subscription at the natural term-end.

The negotiation on a bridge subscription differs from the negotiation on a strategic-VMware subscription. The customer's posture is explicitly transactional — minimum commitment, shortest term, minimum bundled functionality. Broadcom's commercial response is generally less generous than on strategic deals (the strategic relationship is essentially absent) but the customer's commitment is correspondingly limited.

Bridging subscriptions are commercially valid — Broadcom sells them — but customers should be clear about the strategic posture, both internally and with the vendor. Conflating a bridge subscription with a strategic commitment produces worse outcomes on both ends: the bridge becomes a multi-year reluctant commitment, or the strategic deal is undercommitted and forced to renegotiate prematurely.

Industry-specific considerations

The perpetual-end transition has different consequences in different industries. Three sectors face particularly distinct considerations.

Financial services and regulated industries

Regulated industries face elevated risk from running unsupported software. The compliance and risk-management obligations on regulated entities make the unsupported-perpetual path materially harder to defend internally. For these sectors, subscription conversion is generally the only viable path unless migration can be executed quickly.

Healthcare and clinical environments

Healthcare estates have particularly long-lived workloads (some clinical systems run for a decade or more without architecture change) and particularly demanding regulatory frameworks. The perpetual-licensing model historically matched these characteristics. The subscription model is a more uncomfortable fit, and many healthcare customers are evaluating alternative platforms more seriously than they would have under the historic VMware commercials.

Public sector and government

Public-sector procurement practices, multi-year budget cycles, and contractual frameworks all interact awkwardly with the new subscription model. Government customers in many jurisdictions have been particularly slow to convert from perpetual, in part because the procurement frameworks make multi-year subscription commitments harder to authorise than single-purchase perpetual buys. Public-sector engagement with Broadcom on conversion is frequently mediated by central procurement frameworks that change the negotiating dynamic substantially.

Related reading

For deeper coverage of related topics, see the complete VMware licensing guide, the subscription conversion pricing guide, vSphere licensing changes, and Broadcom VMware pricing 2026. For audit defence on perpetual entitlements, see our VMware audit defence guide and audit rights in your contract.