Perpetual options, after Broadcom.

Broadcom ended perpetual license sales and support renewals, but the licenses themselves survive. Perpetual owners hold four options: run unsupported, buy third party support, convert to subscription, or migrate off.

What do perpetual VMware owners actually hold in 2026?

Perpetual license owners hold a permanent right to run the licensed version, and that right survived the Broadcom transition; what they lost is the ability to renew support or buy new perpetual licenses. The transition details sit in Broadcom's own announcements and the Broadcom support portal.

Without active support, there are no new patches, no severity tickets, and no upgrade rights. The license runs; the safety net is gone.

What expired support actually means

• Usable. The licensed version keeps running indefinitely on existing hardware.
• Frozen. No version upgrades and no security patches from Broadcom.
• Exposed. New CVEs against the frozen version accumulate as unmanaged risk.

The clock that matters

The decision clock is not the license; it is hardware refresh and CVE accumulation. Most stable clusters can run 2 to 4 years frozen before either forces a move.

What are the four options for a perpetual estate?

The four options are run unsupported, third party support, subscription conversion, and migration, and they are not mutually exclusive across an estate. The right answer is usually a portfolio split by workload criticality.

Conversion: what VCF and VVF actually price

Broadcom sells VMware Cloud Foundation and vSphere Foundation per core with a minimum per CPU. Core dense hosts multiply the bill, so the conversion decision is a hardware density decision as much as a licensing one.

Migration: the honest timeline

Hypervisor alternatives are production credible in 2026, but enterprise migrations run 12 to 24 months once tooling, operations retraining, and application validation are counted. The option is real only if started before renewal pressure peaks.

How do you decide across the four options?

Split the estate by workload criticality and hardware runway, then assign each cluster the cheapest option that meets its risk bar. Whole estate answers are almost always wrong in one direction or the other.

• Strategic core. Growing, integration heavy clusters: convert, but negotiate the tier and core count hard.
• Stable production. Flat workloads on supported hardware: third party support buys years of runway.
• Ring fenced edge. Isolated, stable, low change clusters: run unsupported with compensating controls and an exit date.
• Replaceable tier. Workloads with credible alternatives: migrate on your calendar, not Broadcom's.

Where the common advice on VMware perpetual licenses is wrong

The standard advice is that running unsupported hypervisors is reckless and conversion is the only responsible path. We disagree. In roughly a third of the VMware estates Fredrik Filipsson advised in 2024 to 2025, ring fenced stable clusters ran unsupported or on third party support with no production incident attributable to the choice, while saving 40 to 70 percent against the conversion quote. The buyer side move is risk tiering, not blanket conversion. Broadcom's pricing assumes fear does the negotiating; a tiered estate plan takes that lever away.

Broadcom priced the renewal assuming you have no plan. The estate that arrives tiered, with exit dates per cluster, pays a different number.

What to do next

1. Inventory perpetual entitlements, support end dates, and core counts per host.
2. Tier the estate: strategic core, stable production, ring fenced edge, replaceable workloads.
3. Price third party support quotes against the Broadcom subscription quote per tier.
4. Model VCF and VVF conversion cost against actual core density and component usage.
5. Start the migration assessment on replaceable tiers now, before renewal pressure peaks.
6. Set compensating security controls and exit dates for any unsupported clusters.
7. Take the tiered plan into the Broadcom negotiation; it is the leverage.

For the wider Broadcom picture, start with the Broadcom VMware advisory practice. For an always on review lane across all your vendors, see Vendor Shield.

Frequently asked questions

Can we legally keep running perpetual VMware licenses?

Yes. Perpetual licenses grant a permanent right to run the licensed version, and that right survived the Broadcom transition. What ended is support renewal, patches, and upgrade rights.

How risky is running vSphere unsupported?

It depends on the cluster. Stable, ring fenced, low change clusters with compensating controls ran without attributable incidents across our 2024 to 2025 engagements. Internet adjacent or fast changing clusters carry real CVE exposure.

What does VMware subscription conversion cost?

Quotes in our engagement file ran 2 to 5 times prior support spend, priced per core with per CPU minimums. Core dense hosts multiply the bill, which makes hardware density the key cost input.

Is third party support for VMware credible?

Yes, for stable estates. Providers deliver severity response and security advisories at 40 to 70 percent below subscription cost. The trade is no new versions and advisory based rather than vendor patching.

How long does a VMware migration really take?

Twelve to twenty four months at enterprise scale, counting tooling, operational retraining, and application validation. The option is only real if started before the renewal deadline removes your calendar.