VMware Perpetual Licence Holders: Your Rights, Options, and Risks in 2026

What Perpetual Licence Rights Actually Mean Under Broadcom

A perpetual VMware licence grants the right to use a specific version of VMware software (e.g., vSphere 7.0 Enterprise) indefinitely. Perpetual rights do not expire, cannot be revoked, and pass to successive administrators and owners. This is fundamentally different from subscription licences, which are usage rights tied to active support and are revoked immediately upon termination or expiry.

Broadcom has not revoked perpetual licences. VMware perpetual holder customers can continue operating licensed software versions today without any renewal, and they can continue indefinitely. This is a legal right under the original licence agreement, and Broadcom is bound by it. However, the distinction between perpetual run-rights and the separate Support and Subscription (SnS) contract is critical: these are two separate agreements with different renewal terms and different consequences when they expire.

Perpetual run-rights are permanent. SnS is a separate contract that expires. The expiry of SnS does not end your perpetual run-rights, but it does remove your access to patches, updates, and technical support.

What Happens When Your SnS Expires

SnS contracts have defined expiry dates, typically set when perpetual licences were originally purchased. When SnS expires, these events occur immediately:

1. Patch Access Ends

You lose access to security patches, bug fixes, and critical updates. Your vSphere 7.0 infrastructure continues operating exactly as it did before SnS expired, but Broadcom will not issue new patches or security releases for your version. Any zero-day vulnerability discovered after SnS expiry affects your infrastructure without remedy. This is the primary security risk of running without SnS.

2. Phone Support Terminates

Technical support from Broadcom ends. If you encounter issues, you no longer have access to Broadcom's support team. You can attempt to work through community forums or hire third-party support, but official Broadcom support is unavailable until you renew SnS.

3. Hardware Compatibility Becomes Unclear

Broadcom provides Hardware Compatibility Lists (HCL) updates with active SnS. When SnS expires, you no longer receive HCL updates. Deploying your perpetual vSphere 7.0 licence on brand-new hardware (e.g., AMD EPYC Genoa CPUs released in 2024) may be untested and unsupported under your expired SnS. This creates risk when adding new infrastructure.

4. Licence Activation Limitations Appear

vSphere 7 licenses can be activated without active SnS. However, vSphere 8 Update 3 (released in late 2024) introduced a technical enforcement: licences require valid SnS during activation. If you attempt to stand up a new vSphere 8 Update 3 cluster, you will be blocked at activation until SnS is renewed. This is the first version of vSphere with technical licensing enforcement.

The Cease-and-Desist Reality: Who Has Received Letters and Why

Broadcom has issued cease-and-desist letters to perpetual VMware licence holders, but not broadly and not targeting run-rights themselves. These letters target specific behaviour: using post-SnS-expiry patches or attempting to distribute patches obtained through other means.

When Broadcom Issues Cease-and-Desist Letters

The most common trigger is when perpetual licence holders discover vSphere patches released after SnS expiry, download them (often from pirated or leaked sources), and deploy them into production. Broadcom's audit telemetry (CSSM) detects version mismatches: the licence registration shows vSphere 7.0 SP2 but the actual running version is 7.0 SP3 (released after SnS expired). This triggers investigation and, in some cases, cease-and-desist letters claiming unauthorised use of post-support software.

The legal argument is technical: using post-SnS patches without active SnS is argued as outside the perpetual licence scope because the patches were released after the SnS term ended. This argument has not been tested in court, but Broadcom's cease-and-desist letters assert it aggressively.

Cease-and-desist letters are rare and typically target customers who use patches released after SnS expiry. Customers running perpetual vSphere versions exactly as licensed (no post-expiry patches) have not received letters.

The Realistic Risk

If you hold a perpetual vSphere 7 licence and SnS expired in 2024, and you continue running vSphere 7.0 SP2 (the last version released before SnS expired) unchanged, you are extremely unlikely to receive a cease-and-desist letter. Broadcom's enforcement targets clear cases of post-SnS patch use, not perpetual licence holders maintaining licensed versions as-is. Running without patches is operationally risky from a security standpoint, but not legally risky from Broadcom enforcement.

The Trade-In Offer: What Broadcom Is Offering and What It Actually Costs

Broadcom launched perpetual licence trade-in programs in late 2024, offering perpetual holders a path to subscription by applying credit toward VCF (VMware Cloud Foundation) subscriptions. The headline offer is attractive: 50-60% discount on subscription list price in exchange for retiring perpetual licences.

However, the true cost requires careful analysis:

Trade-In Mathematics

A perpetual vSphere Enterprise licence (8 cores) holds an estimated fair-market value of USD 15,000-20,000 (based on secondary market transactions). Broadcom's trade-in offer provides USD 10,000-12,000 credit (50% discount assumption) toward a VCF Standard or Advanced subscription. This trade-in credit is applied to list rates that are already inflated by bundle requirements and 72-core minimums.

Example calculation: a customer with 400 cores of perpetual Enterprise licence could trade in for USD 200,000-240,000 credit. Broadcom's list VCF Standard is USD 7,500 per core per year. With 400 cores, the annual subscription cost is USD 3,000,000 before discount. The USD 200,000-240,000 credit reduces the first-year cost to USD 2,760,000-2,800,000. Compared to perpetual (zero annual cost), the customer is now paying USD 2.76M annually in perpetuity, while the trade-in credit only covers part of year one. Net cost over five years: USD 13.8M versus zero with perpetual. The trade-in offer looks poor on total cost of ownership for large deployments.

When Trade-Ins Make Sense

Trade-in offers are most valuable in these scenarios: (a) SnS is about to expire or has already expired, and you cannot afford the cost of no patches; (b) you are approaching end-of-life for a hardware generation and refresh is planned within 24 months; (c) you have compliance requirements that mandate current-version or actively-supported software; (d) you lack internal talent to maintain unsupported versions safely. In these cases, migration to subscription may cost less than the security and operational risks of running perpetual without SnS indefinitely.

Three Paths Forward for Perpetual Licence Holders

Path 1: Stay on Perpetual, Accept No Patches

Continue operating your perpetual vSphere version exactly as licensed, without SnS and without patches released after SnS expiry. This path is legally safe (no cease-and-desist risk) but operationally risky (no security updates, no new hardware support). This path is viable for:

• Non-production or test environments where security is a lower priority.
• Infrastructure planned for decommissioning within 2-3 years.
• Organisations with isolated networks and strict change controls preventing external threats.
• Teams with strong internal VMware expertise and ability to diagnose and workaround issues without Broadcom support.

Expected lifespan: vSphere 7 can remain operational for 5-8 years post-SnS expiry in stable environments. However, hardware generations move faster (new CPUs, new chipsets), so compatibility challenges will emerge around year 3-4 when hardware refresh becomes necessary.

Path 2: Buy Subscription to Modernise

Transition to Broadcom VMware subscription, either through trade-in programs or standard renewal. This path provides ongoing patches, support, and hardware compatibility. Total cost is USD 3-5M annually for mid-large deployments, but you gain modern infrastructure posture and Broadcom support.

This path makes sense if: (a) you have compliance requirements for current software versions; (b) your hardware refresh cycles align with subscription (every 3-5 years); (c) your infrastructure is actively growing and you need new deployment capacity; (d) you lack internal expertise to maintain perpetual versions long-term.

Path 3: Migrate to Alternatives

Evaluate and migrate to alternative hypervisor and cloud platforms (Proxmox, OpenStack, Nutanix). This path eliminates Broadcom dependency but requires capital investment in migration, operational reskilling, and possible application re-architecting. Total migration cost is typically USD 500K-2M for mid-size deployments, but ongoing licensing cost drops to near-zero for open-source stacks (Proxmox) or fixed subscriptions much lower than VMware (Nutanix).

This path makes sense if: (a) your total perpetual and ongoing subscription cost over five years exceeds the migration investment plus alternative platform cost; (b) you have skilled engineering teams capable of operating open-source infrastructure; (c) your workloads are not tightly bound to vSphere features (e.g., heavy vSAN users face higher migration cost).

For organisations with 500+ cores, alternatives become financially competitive within 2-3 years of subscription ownership. Calculate your five-year total cost across all three paths before deciding.

The Security Risk of Running Without Patches

Running perpetual vSphere without patches is operationally simple but security-risky. Each month that Broadcom releases security patches for active versions, perpetual licence holders without SnS fall further behind. Vulnerabilities in hypervisors are particularly dangerous because they often allow host-to-VM escape, granting attackers access to all virtual machines on compromised hosts.

Recent example: vSphere 7 vulnerabilities (CVE-2023-20897, CVE-2024-22206) required patches released in 2024. Perpetual licence holders without renewed SnS could not apply these patches. Their vSphere infrastructure remained vulnerable for months or years unless they purchased subscription retroactively.

Security insurance costs often exceed subscription renewal costs. If your organisation carries cyber insurance with exclusions for unpatched software, running without patches may void coverage. This indirect cost should factor into your perpetual versus subscription calculation.

Five Decisions to Make Before Your Next SnS Expiry Date

Decision 1: Calculate Your Five-Year Cost

Model total cost of ownership for all three paths: (a) stay on perpetual with no patches; (b) renew subscription; (c) migrate to alternatives. Include patch risk, security insurance impact, and operational labour. Use realistic subscription pricing (not list rates), and factor in audit and true-up settlement risk. Spreadsheet the five-year cost for each path and identify the lowest-cost option.

Decision 2: Assess Compliance Requirements

Determine whether your regulatory environment (PCI-DSS, HIPAA, SOC2, NIST) allows running perpetual software without active support. Some compliance frameworks explicitly require current or actively-supported software versions. Others allow older versions if documented risk assessments are completed. Document your compliance position before SnS expires.

Decision 3: Evaluate Your Hardware Refresh Cycle

Perpetual vSphere 7 will encounter hardware compatibility limits around years 3-4 post-SnS. If your hardware refresh cycle is 5-6 years, you will need subscription or alternatives before your next refresh. If your refresh cycle is 2-3 years, you may be able to stay on perpetual until refresh, then migrate to alternatives. Align your licence decision with infrastructure refresh timing.

Decision 4: Commission a Migration Evaluation

Whether you choose perpetual, subscription, or alternatives, invest in a professional evaluation comparing all three. Migration cost, operational impact, and licensing cost vary significantly based on your specific workloads, team skills, and infrastructure scale. A USD 10K-20K evaluation provides clarity worth millions in future cost avoidance.

Decision 5: Engage Broadcom or Third-Party Advisory

If you choose subscription, negotiate the transition actively. Broadcom's initial offers are not final positions. Engage sales leadership, prepare alternative architecture evaluations, and negotiate price caps and mid-term reduction rights. If you choose alternatives or extended perpetual, document your decision and ensure your procurement and compliance teams understand the strategy and timeline.

Whether you plan to stay on perpetual licensing, transition to subscription, or migrate to an alternative platform, the commercial negotiation strategy matters enormously. The Broadcom VMware negotiation playbook gives perpetual holders the commercial framework to engage Broadcom from a position of strength — whether negotiating trade-in credits, subscription terms, or exit timelines.