This is no longer a purchase comparison: Broadcom closed perpetual VMware licensing to new sales in early 2024 and is not renewing support contracts on existing perpetual estates. The decision rule for 2026 is therefore about your end state, and there are exactly three — run your perpetual licenses unsupported past the support cliff, trade the estate in to a VCF or VVF subscription, or replatform off vSphere — each with a different risk profile, cost curve and negotiating clock.
Published 5 May 2026 · Last reviewed 28 May 2026
Three facts define the post-acquisition position. First, perpetual SKUs are closed: since early 2024 there has been no way to buy a new perpetual VMware license, and no announced path back. Second, existing support and subscription (SnS) contracts run to the end of their committed term and are honoured — entitlement to patches, updates and support continues exactly as contracted until expiry. Third, SnS is not renewed at expiry: instead of a renewal quote for support, customers receive a subscription quote for VCF or VVF, the two per-core bundles into which the old portfolio was consolidated.
What survives is the perpetual right itself. A perpetual license remains a permanent right to run the software version you are entitled to, and that right does not lapse with support. What lapses is everything around it: security patches, version upgrades, and someone to call. The post-expiry position is workable for some estates and untenable for others, which is why the decision below is genuinely three-way rather than a forced march to subscription.
The commercial context matters too, stated factually: industry reporting since 2024 has consistently described subscription quotes at renewal that represent multiples of customers’ previous annual SnS spend, with the steepest movements on small and mid-size estates. Whatever your own quote says, it should be treated as an opening position in a negotiation, not a tariff.
This guide compares licensing programs and end states as published and reported; it is general information, not legal or licensing advice for your situation, and it names no firms. Where the comparison touches contested commercial ground — lapsed-support usage, third-party support — both sides’ factual position is stated. The firm directory lists VMware-capable advisors with balanced pros and cons, listed, not ranked.
| DIMENSION | STAY PERPETUAL, UNSUPPORTED | TRADE IN TO SUBSCRIPTION | REPLATFORM OFF VSPHERE |
|---|---|---|---|
| Right to run | Permanent, at the version and patch level reached when support expired | For the subscription term only; ends if the term ends | Governed by the replacement platform’s terms |
| Updates & security | None after expiry; applying later patches is generally outside entitlement. Third-party support firms offer fixes-without-vendor-code; Broadcom disputes the boundaries of some of these models | Full stream of updates, versions and support for the term | Replacement vendor’s update stream; migration window is the exposed period |
| Commitment | None — that is its appeal; viable as a deliberate bridge, riskier as a destination | Per-core, term-based (one to five years); a 16-core-per-CPU floor applies (a 72-core order minimum announced for April 2025 was withdrawn) | Migration project cost up front; commercial terms reset on the new platform |
| Exit / renewal dynamics | Maximum optionality, decaying over time as hardware and hypervisor drift apart | Renewal is the pressure point: no terminal value, repricing risk at every term end | Trades a known vendor dependency for a new one — evaluate the replacement’s lock-in honestly |
| Fits | Stable, ring-fenced estates; hard isolation; planned decommission inside ~24 months | Estates staying on VMware strategically — then the real question becomes VCF vs VVF | Estates where the subscription economics or stack direction no longer fit; needs executive patience |
Most large organisations end up in a blend: subscribe the strategic core, freeze and ring-fence the stable legacy clusters, and replatform the workloads with the easiest exits. The blend is not indecision — it is usually the position with the strongest renewal leverage, because it proves to the vendor that part of the estate can leave.
The clock is the negotiation. Your leverage peaks while your SnS contract is still live and decays toward its expiry date, because every option — freezing, subscribing on decent terms, or migrating — is cheaper and calmer with support still in place. Buyers who start the evaluation twelve months before expiry choose an end state; buyers who start three months before have one chosen for them. The timing dynamics mirror any major VMware renewal negotiation.
Trade-in value is a variable, not a tariff. Transition incentives recognising perpetual investment exist but are set deal by deal. Treat the credit as one negotiable lever alongside term length, core count, bundle tier and co-termination — and get every concession in the order paperwork, not in the account manager’s email.
Know your entitlement before anyone quotes you. The subscription quote will be sized on Broadcom’s view of your estate. An independent effective license position — perpetual entitlements, live SnS coverage, actual core counts under the 16-core-per-CPU floor — is the difference between negotiating from your data and negotiating from theirs.
The lapsed-support compliance line. Running within your perpetual entitlement after support expires is lawful. Applying patches or binaries released after expiry is generally outside entitlement, and Broadcom has actively written to lapsed-support customers about post-expiry downloads. If the freeze is your strategy, document your patch level at expiry and lock the repositories — an auditable freeze is a defensible freeze. Third-party support is a further option whose boundaries the vendor contests; both positions are factual, and the choice deserves specific advice rather than a blog’s confidence.
Audit posture changes either way. Subscribers should expect entitlement-versus-deployment reconciliation against core counts; perpetual holders should expect scrutiny of version and patch levels. Whichever end state you pick, the response playbook is the standard one — covered by the firms on the VMware audit defense page.
Letting SnS lapse before deciding. The expiry date is a one-way door for your options, not just your support. Once lapsed, the freeze is your default whether or not it suits the estate, and any later subscription starts from a weaker negotiating position. Decide before the door closes, even if the decision is a deliberate bridge.
Assuming perpetual covers upgrades. The perpetual right is to the versions your entitlement reached, not to whatever ships next. Estates that casually upgrade past their support window create exactly the paper trail an audit finds fastest.
Sizing the subscription on stale core counts. The per-core metric with its 16-core-per-CPU floor prices differently from the old per-socket world (a 72-core per-order minimum announced for April 2025 was withdrawn within days). Recount the estate on the new rules before evaluating any quote; the spread between socket-think and core-think is where surprise lives.
Treating the replatform estimate as a press release. Migration timelines from real projects run months to years depending on operational depth. An end state you cannot reach before your support cliff is not leverage — the vendor can read a calendar too. Build the honest timeline first, then negotiate with it.
Taking direction from the channel without the conflict check. Much transition advice arrives from parties earning margin on the destination. The independence test — who pays your advisor, and for what — applies to this decision more than most, and how to choose a software licensing consultant covers the fuller diligence.
No. A perpetual license is a permanent right to run the version you are entitled to. What ends with the support contract is everything around the right to run: security patches, updates, new versions and vendor support. The license survives; the safety net does not.
As a rule, no. Broadcom announced the end of perpetual license sales and of SnS renewals as part of the move to subscription; existing support contracts run to the end of their committed term and are then closed. Limited exceptions have surfaced case by case, but planning should assume the renewal door is shut.
Running the software within your perpetual entitlement is lawful. The compliance boundary is updates: applying patches or versions released after your support expired is generally outside your entitlement, and Broadcom has written to lapsed-support customers on exactly this point. If you stay perpetual, freeze your patch level at expiry and document it.
Broadcom and its partners have offered transition incentives that recognise existing perpetual investment when a customer moves to VCF or VVF subscription. There is no universal published program; the value is set deal by deal, which makes it a negotiation variable like any discount. Treat it as one lever among several, not as a fixed entitlement.
Estimates from real migrations run from months for a small, simple estate to multiple years for large environments with deep operational integration. The honest planning number matters because it sets your negotiating position: a replatform you cannot complete before your support cliff is leverage for the vendor, not for you.
No. This is a directory, not a ranking. Firms are listed alphabetically with balanced pros and cons. Independence is shown as a pro and reseller, Big-Four or vendor-side-audit ties as a con, both stated as factual trade-offs for you to weigh.
Choosing an end state, recounting the estate on per-core rules, pricing the trade-in lever and building the timeline that protects your leverage is precisely the work of a VMware licensing advisory engagement. The Broadcom VMware hub maps the vendor’s wider licensing world, and the directory lists every firm covering VMware — balanced pros and cons, listed, not ranked.
If you subscribe, this is the next decision →
Every firm for this work →
The renewal-event playbook and its firms →
The selection framework →
Filtered, listed, not ranked →
Every field guide on the site →
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.