What Broadcom Actually Ended — and When
On 11 February 2024, Broadcom formally announced the end of all perpetual licensing for VMware products. This was not a gradual transition with multi-year notice periods. Partners received days of warning. Resellers had perpetual inventory pulled from catalogues within weeks. Enterprise customers in active renewal negotiations found the products they were negotiating for no longer existed.
The change applied to every VMware product: vSphere, vSAN, NSX-T, Aria (formerly vRealize), Horizon, Tanzu, and all associated management and operations tooling. The only licensing model now available is subscription-based, anchored to two primary bundles: VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF).
Support and Subscription (SnS) renewals for perpetual licences were also discontinued. Customers cannot renew support on existing perpetual assets. Broadcom's stated position: perpetual licences remain technically valid, but without SnS, customers operate without security patches, critical updates, or access to technical support.
This is a fundamental change to the economics of VMware infrastructure. Understanding the financial impact requires first understanding what perpetual licensing actually provided — and what its replacement demands.
The Financial Impact: Why Costs Jump So Sharply
The cost increase from perpetual plus SnS to VMware subscription bundles is driven by three structural factors that most finance and IT leaders have not fully worked through:
1. Forced Bundle Inclusion
VMware Cloud Foundation (VCF) is an all-in bundle: vSphere, vSAN, NSX, and Aria Operations are all included, mandatory. Organisations that previously ran vSphere only — the largest segment of VMware's enterprise base — now pay for vSAN storage networking and NSX software-defined networking whether they use them or not. For a typical 500-core estate, this forced inclusion alone drives 40–60% of the cost increase before per-core price changes are considered.
2. Per-Core Pricing on Every Socket
Legacy perpetual licensing used per-CPU socket pricing with minimums. VCF pricing is per core, with a 16-core minimum per processor. Modern high-core-count processors (Intel Xeon Platinum, AMD EPYC) typically run 32–64 cores per socket. An organisation running two 32-core processors per server now pays for 64 VCF cores rather than 2 processor licences — a 32× increase in the licence unit count, offset only by per-core pricing that is lower than per-socket pricing was.
3. Elimination of Perpetual Asset Value
Perpetual licences were balance-sheet assets with indefinite useful life. SnS was the only ongoing cost. The migration to subscription eliminates all perpetual asset value. The perpetual licences organisations spent years purchasing are worth nothing in Broadcom's new commercial model. There is no credit, no trade-in, no value preservation mechanism.
The compound effect: A 500-core VMware vSphere estate paying £400k/year in SnS renewals typically sees VCF subscription costs land between £1.4M and £2.2M annually at list pricing — a 3.5× to 5.5× increase before any negotiation. This is before accounting for deployment model complexity or additional Broadcom-required add-ons.
Who Is Most Financially Affected
Not all organisations face the same impact. The severity of the cost increase correlates with how VMware licences were previously structured and what products were in scope:
vSphere-Only Estates
Highest relative increase. Forced to purchase VCF or VVF bundles containing vSAN and NSX they don't use. Typically 4–6× cost uplift.
High-Core-Count Environments
Organisations running modern processors (32+ cores/socket) face the sharpest unit count expansion. Per-core minimums hit hard.
ELA Customers at Renewal
Enterprise License Agreements must now convert to VCF/VPP subscriptions. Historical ELA discounts rarely carry forward. Most see 50%+ uplift.
vSAN and NSX Users
The least impacted. These customers were already paying for storage and networking components now bundled into VCF. Relative increase smaller.
The Support Gap: Operating Without SnS
A significant fraction of enterprise VMware customers are currently operating on lapsed or expiring SnS with no clear path to renewing it. Broadcom will not renew SnS on perpetual products. This creates a support gap that carries material operational and security risk:
Without active SnS, customers cannot download patches or security updates for vSphere, vSAN, or NSX. Critical vulnerabilities — including the type of hypervisor escape and privilege escalation vulnerabilities that VMware has disclosed every quarter for years — go unpatched. Security and compliance frameworks (ISO 27001, SOC 2, PCI DSS) require timely patching of infrastructure. Operating without SnS puts compliance certifications at risk.
Broadcom's implicit message is clear: the only way to maintain a supported, patched, secure VMware environment is to migrate to subscription. The support gap is not an oversight — it is a design feature of their migration pressure strategy.
Realistic Migration Options
Organisations facing perpetual licence end have five realistic options, each with distinct time horizons, cost profiles, and risk levels:
| Option | Time to Execute | Cost vs VCF | Key Risk |
|---|---|---|---|
| Migrate to VCF/VVF | Immediate | Baseline | Lock-in at high price point |
| Migrate to Nutanix AOS | 6–18 months | -20% to -40% | Re-tooling complexity |
| Move to public cloud (AWS, Azure) | 12–36 months | Variable | Egress costs, latency, security |
| Migrate to Microsoft Hyper-V / Azure Stack HCI | 6–18 months | -30% to -50% | Operational re-skilling |
| Bare-metal / KVM open source | 18–36 months | -60% to -80% | Support model, ecosystem gaps |
Most large enterprises will not execute a full platform migration in the timeframe Broadcom's renewal pressure implies. The credible threat of migration, however, remains your most powerful negotiating lever — and Broadcom's sales organisation knows it.
Your Negotiation Position
Despite the aggressive commercial posture, VMware subscription pricing is negotiable. Broadcom's public statements about standardised pricing should not be taken at face value in the enterprise segment. Our data across 40+ VMware engagements since the acquisition shows achievable outcomes:
- Multi-year commitments (3-year term) securing 25–35% discount on list VCF pricing
- Workload growth commitments in exchange for lower per-core rates on current estate
- Phased migration schedules allowing delayed full-estate conversion
- Exclusion of edge and DR workloads from primary VCF count
- Retention of existing perpetual discounts as a baseline for subscription pricing discussions
- Partner-sourced pricing through preferred Broadcom partners unlocking additional rebate structures
The critical prerequisite for any of these outcomes is that you arrive at the negotiation with a credible alternative. Broadcom's account teams are experienced — they will probe whether your migration threat is real. You need internal executive sponsorship for the alternative path, at least one vendor's proof-of-concept scoped and documented, and a timeline that Broadcom can see is operationally plausible.
Timing matters critically: Broadcom applies significant pressure in the 90-day window before SnS expiry. Organisations that begin negotiation inside that window concede enormous leverage. The optimal engagement point is 9–12 months before renewal — before Broadcom's renewal team has initiated formal contact.
What Enterprise IT Should Do Now
The organisations we see achieving the best outcomes share five common preparation steps, regardless of their eventual migration decision:
Step 1: Baseline Your Current Asset Position
Document every perpetual VMware licence you hold, its SnS expiry date, and its equivalent in VCF core count terms. This mapping is the foundation of every negotiation conversation. Most organisations underestimate their core count requirement because they haven't converted historical socket licences to core equivalents.
Step 2: Model the True Cost of VCF at List
Get Broadcom to provide a formal proposal in writing, at list pricing, covering your full estate. This gives you a negotiating anchor. It also frequently reveals errors in how Broadcom has sized the requirement — particularly around core counts and optional add-ons they've included without discussion.
Step 3: Initiate at Least One Alternative Vendor Evaluation
You don't need to complete a migration to use one as leverage. A documented Nutanix or Microsoft HCI evaluation with scoped pricing gives your procurement and legal team the negotiating materials they need. This step alone has saved clients 20–30% on VCF negotiations before any other discussion.
Step 4: Engage Legal Early
Broadcom's subscription agreements contain materially different terms than historical VMware ELAs — particularly around audit rights, pricing adjustment mechanisms, and termination provisions. Have counsel review before signing. The T&Cs have been updated multiple times since the acquisition and contain provisions that limit your options at renewal.
Step 5: Bring in Independent Advisors
Broadcom's account teams negotiate VMware deals every day. Enterprise IT procurement teams negotiate them every three to five years. This asymmetry of experience and information is the single biggest factor determining negotiation outcomes. Independent advisors with current market data close this gap.