VMware Broadcom Transition Guide 2026
How Broadcom rebuilt VMware's commercial model around subscription bundles, and the field-tested moves enterprise buyers use to contain a 2 to 5x cost shock, preserve use, and keep a credible exit on the table.
Executive Summary
Since closing its acquisition of VMware in November 2023, Broadcom has executed one of the most aggressive commercial transformations in enterprise software history: perpetual licenses were discontinued and replaced with subscription-only terms, the product catalogue was collapsed from dozens of SKUs into a small number of bundles led by VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF), Support and Subscription (SnS) was folded into the subscription, and minimum purchase thresholds were raised, first to 16 cores per CPU, then, for many customers, toward much larger minimum commitments. The result for a typical enterprise renewal is a quoted cost increase of two to five times, and in outlier cases ten times or more.
This guide distils what former VMware and Broadcom commercial practitioners understand about how the new model is engineered and where it can be challenged. It covers the bundle economics, per-core subscription mechanics, the perpetual-to-subscription cliff, term and discount benchmarks, the realistic alternatives (Nutanix, Microsoft Azure Local, Proxmox, public cloud), and a structured negotiation and exit framework. The central message for buyers is unambiguous: Broadcom's first quote is an anchor built on your perceived lock-in, and a credible, costed alternative is the single most powerful lever for bringing that number down 20 to 50%.
1. What Broadcom Actually Changed
The transition is not a price rise layered on the old model, it is a different commercial architecture. Three structural changes do most of the work, and each one is designed to convert what was previously optional spend into recurring, bundled, committed spend.
First, perpetual licensing ended. Existing perpetual licenses remain valid, but they can no longer be renewed for support; once SnS lapses, the only path to patches, security fixes, and upgrades is a subscription. This removes the "run it as-is for another three years" option that many infrastructure teams relied on as a fallback. Second, the catalogue was consolidated into bundles. Where customers once bought vSphere standalone and added vSAN, NSX, or Aria selectively, the headline offerings are now VMware Cloud Foundation (the full stack, compute, storage, networking, and management) and the smaller vSphere Foundation. Customers who used only a fraction of the stack are pushed toward paying for the whole bundle. Third, pricing moved to a per-core subscription with rising minimums, so even lightly populated CPUs are billed at a floor that often exceeds prior usage.
Understanding this architecture matters because each lever is negotiated differently. Bundle composition is contestable through edition selection; per-core cost is contestable through core-count discipline and term; and the migration cliff is contestable only by having somewhere else to go.
Broadcom's commercial teams are measured on total contract value and multi-year commitment, not on logo retention at any price. That is why the opening quote is deliberately high and why the deepest concessions appear late in the cycle and almost always require evidence that you are seriously evaluating an alternative. The number moves when your BATNA becomes believable, not when you object to the number.
2. The Bundle Economics: VCF vs VVF
The two anchor products define the decision space. VMware Cloud Foundation (VCF) is the premium full-stack bundle and carries the higher per-core rate; VMware vSphere Foundation (VVF) is the lighter bundle aimed at customers who need virtualization and management but not the integrated storage and networking layers. Broadcom's sales motion strongly favours steering customers to VCF, because it captures the largest share of wallet and locks in the most components. For a buyer, the first analytical task is brutally honest: which components of the stack are you actually running in production, and which are being attached because the bundle makes them "free"?
The table below sketches the indicative positioning of the two bundles. List rates move and are negotiable; the point is the relative gap and what each tier includes.
| Bundle | Core components | Indicative list / core / year | Best fit |
|---|---|---|---|
| vSphere Foundation (VVF) | vSphere, vCenter, Aria management, limited vSAN capacity | ~$135 | Compute-centric estates using third-party storage/networking |
| Cloud Foundation (VCF) | vSphere, vSAN, NSX, Aria suite, full SDDC stack | ~$350 | Private-cloud / full software-defined data centre adopters |
| vSphere Standard (where offered) | vSphere only, capped | ~$50 | Small clusters, edge, ROBO sites |
The single most common overspend we see is a customer accepting VCF when their production reality is "vSphere plus a bit of vSAN." If NSX and the full Aria suite are not deployed and not on a near-term roadmap, paying the VCF premium for them is pure leakage. The bundle's bundled extras are only a saving if you would otherwise have bought them.
3. Per-Core Mechanics and the Minimum-Commitment Trap
Broadcom prices per physical core, with a minimum of 16 cores billed per CPU regardless of the actual core count. For older or smaller processors this floor inflates the bill; for modern high-core-count CPUs the minimum is less of a factor but the per-core rate dominates. Critically, many enterprise agreements now also carry an overall minimum core commitment for the account, which can force customers to license well above their current deployed footprint.
The arithmetic compounds quickly. A modest cluster that cost a few tens of thousands of dollars per year in perpetual SnS can re-quote into the high six figures once every core is subscription-licensed at bundle rates. The worked example below shows how the same 8-host cluster lands under the old and new models.