Broadcom's acquisition of VMware in November 2023 changed the licensing economics of the data center overnight. The 8,000 SKU portfolio was collapsed into a small set of bundles. Perpetual licenses were eliminated. Subscription pricing replaced upfront purchase with multi year commitments. The partner channel was reshaped. The customer experience reset.
For most enterprises, the result has been a renewal proposal that arrives larger, more complex, and less negotiable than what it replaces. This playbook is the buyer side response. It is built from the same negotiation muscle our advisors bring to a Broadcom VMware renewal, an Enterprise Licensing Agreement (ELA), or an audit defense cycle.
The pages that follow do not assume you can avoid the Broadcom motion. They assume you have to engage it. What we offer is sequence, evidence, and the contract clauses we have seen Broadcom defend hardest. Pair this with our Broadcom VMware Knowledge Hub and the Broadcom services overview.
The new Broadcom VMware model
The Broadcom motion has three commercial pillars. Subscription only licensing. Bundled SKUs. Centralised account ownership. Each pillar is non negotiable as a category. Each is heavily negotiable in its specifics. The buyer who tries to argue against the model loses. The buyer who works inside the model wins discount, term, and exit flexibility.
- Subscription only.Perpetual licenses are no longer sold. Existing perpetual customers retain rights but receive no new patches once support expires. Renewal moves the customer to subscription.
- Bundles.The 8,000 SKU portfolio was collapsed primarily into VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF). Within each bundle, capabilities customers used to buy individually are now grouped.
- Direct accounts.Strategic accounts are managed directly by Broadcom. The legacy partner channel handles smaller customers. The change shifts negotiation from a partner mediated discount to a direct discount discussion.
VCF, VVF, and the bundle decision
The first decision in any Broadcom renewal is bundle selection. VCF is the full platform: vSphere, vSAN, NSX, Aria. VVF is a smaller bundle: vSphere, vSAN, Aria. Below those is vSphere Standard for low end use cases. The bundle choice locks the customer into a price point and a feature surface for the term. Choose well or pay twice.
When VCF makes sense
VCF is appropriate for customers who already use NSX heavily, who run vSAN at production scale, and who are committed to the full SDDC stack. The per core pricing is the highest of the three bundles, but the avoided cost of separate networking and storage software is real. We recommend VCF when at least three of the four components are in production today.
When VVF makes sense
VVF is appropriate for customers who run vSphere and use vSAN but do not run NSX in production. It carries lower per core pricing than VCF and avoids the lock in on networking. We recommend VVF for the majority of mid market and many enterprise estates.
When vSphere Standard makes sense
vSphere Standard is appropriate for very small footprints, edge sites, and tertiary environments. It does not include vSAN. It carries the lowest per core list price. It is rarely the right answer for a primary data center, but a useful tool for edge and remote sites that should not bear VCF or VVF cost.
The bundle trap
The most common mistake we see is customers selecting VCF because the discount looks larger than VVF, without modeling whether they will use NSX. The discount is real. The unused entitlement is also real. We model the per core cost of the actual workload pattern (VMs per core, network virtualisation requirement, storage performance tier) and compare against VVF list with vSAN add ons. The optimal answer surprises customers about half the time.
Per core pricing and the right sizing argument
Broadcom prices VMware by physical core. Hyperthreading does not increase the license requirement. The minimum is 16 cores per CPU socket, even on smaller processors. The per core list pricing has risen materially since the acquisition. The customer's leverage is not in the per core rate. It is in the core count.
Three levers reduce core count without reducing capacity.
- Refresh older hardware to fewer, larger sockets. A workload that ran on 200 older 10 core CPUs may run on 100 newer 24 core CPUs, reducing licensable cores.
- Right size the cluster. Most VMware estates run with substantial headroom. Reducing per VM CPU allocation, increasing consolidation ratios, and decommissioning idle VMs reduces total cores.
- Move workloads. Workloads that do not need the SDDC stack belong on a hyperscaler, on a Hyper V cluster, or on a different hypervisor entirely.
The Broadcom ELA negotiation
For larger customers Broadcom offers an Enterprise Licensing Agreement (ELA), a multi year unlimited or capped commitment for a defined set of products. The ELA is a useful tool for customers who expect growth and want price certainty. It is a trap for customers who expect to shrink their VMware footprint.
Four levers in the ELA
- Scope.Which products are in the ELA? VCF? VVF? Add ons? Loose scope creates ambiguity that Broadcom resolves on its terms at renewal.
- True up rules.How is overconsumption measured and billed? At what cadence? With what notice?
- True down rights.Broadcom resists. Push for the right to reduce capacity at renewal milestones if business conditions change.
- Term.Three years is the most common. Five years is offered with deeper discount but locks in a price point that may not survive market change.
Audit defense under the new model
Broadcom inherits VMware's audit motion and has signalled it will be enforced more actively. The audit risk on VMware estates has historically been moderate compared to Oracle or IBM. Under Broadcom we expect that to change. Three risk areas deserve attention.
Over deployment
Most VMware audits find over deployment, not under. The customer bought 1,000 cores worth of vSphere and is running 1,200. The 200 core gap is the audit finding. The fix is mechanical: reconcile installed capacity quarterly, document decommissions, hold a 5 percent buffer at most.
vSAN reconciliation
vSAN is licensed by capacity tier. Customers who upgrade storage without re licensing vSAN create exposure. The reconciliation should match installed capacity to licensed tier and adjust at renewal.
NSX entitlement
NSX is included in VCF but priced separately in non VCF estates. Customers who use NSX functions without the entitlement (typical of customers who acquired the capability through a previous bundle that no longer exists) face exposure at renewal. Document NSX usage and reconcile against current entitlements.
Credible alternatives: the migration question
The question of whether to migrate off VMware has moved from theoretical to practical for many enterprises. Three credible paths exist. None are easy. All are real.
Hyperscaler native
Lift and shift VMware workloads to AWS EC2, Azure VMs, or GCP Compute Engine, and refactor over time. The transition is the slowest of the three but produces the cleanest exit. The cost economics depend on the hyperscaler discount level. Pair with our AWS, Microsoft Azure, and Google Cloud services briefs.
Alternative hypervisor
Migrate to Microsoft Hyper V, Nutanix AHV, Red Hat OpenShift Virtualisation, or Proxmox. Each has its own migration path, support model, and feature gap relative to VMware. Hyper V is the most direct path for Microsoft heavy estates. Nutanix is the most direct path for HCI estates. OpenShift is the path for customers committed to Kubernetes as the long term platform.
VMware on cloud
VMware Cloud on AWS, Azure VMware Solution, and Google Cloud VMware Engine continue to operate. The licensing flows through the hyperscaler in some configurations and through Broadcom in others. The mechanics are evolving. The strategic question is whether VMware on cloud is a transition path or a destination.
Renewal sequencing
The Broadcom renewal cycle is short. Many customers received contract termination notices with little lead time and were forced into expensive emergency renewals. Do not let that happen twice. Begin the next renewal cycle nine to twelve months early.
- Nine months out: inventory.Document every host, every cluster, every entitlement. Reconcile installed capacity. Identify the bundle that fits the workload pattern.
- Six months out: alternatives.Develop a credible alternative path. Cost it. Time it. Identify the workloads that would migrate first.
- Three months out: open the negotiation.Bring the inventory, the alternative, and the proposed bundle. Anchor on per core cost reduction, term flexibility, and exit ramp.
- Closing: negotiate the contract terms.The headline price gets attention. The contract clauses determine the cost over the term.
Contract clauses we negotiate hardest
- Price hold.Lock per core list price for the term, with capped escalation at renewal. Broadcom resists. Push.
- Bundle re selection.The right to switch from VCF to VVF (or vice versa) at a renewal milestone if workload patterns change.
- Audit notice.60 days notice. Defined scope. Right to use the customer's own measurement methodology.
- True down rights.The right to reduce capacity at renewal milestones, ideally annual.
- Exit assistance.If the customer migrates off VMware, what assistance, what data, what license transfer is provided?
- Termination for convenience.Rare. Worth raising. Sometimes obtained on a partial basis.
Pattern: the high cost renewal
A large media company we worked with received a Broadcom renewal proposal at three times the prior VMware run rate. The bundle selection had moved to VCF by default. The core count had risen because newer hardware had been procured without re licensing. The discount had compressed because the partner relationship had been replaced with a direct account.
The defense ran in four steps.
- Inventory rebuild. We rebuilt the inventory and demonstrated the actual NSX usage was low, justifying VVF.
- Cluster right sizing. We right sized the cluster and reduced licensable cores by 22 percent.
- Alternative path. We developed a Hyper V alternative for one third of the workload.
- Renewal close. We negotiated the renewal with a credible alternative on the table.
The final outcome was a 38 percent cost reduction relative to the initial proposal, on a three year term, with annual true down rights at renewal.
For more renewal patterns see our case studies library.
The CFO view
From a CFO perspective the Broadcom transition has three financial properties to plan against.
- Subscription replaces capex with opex on a multi year horizon. The cash profile changes. The depreciation line shrinks. The operating expense line grows.
- Multi year commitment locks in a cost basis that does not flex easily downward. Once committed, the downward flex is limited until renewal.
- Audit risk is rising and should be priced into the operating budget. Plan a reserve against future reconciliation findings.
The CFO playbook on Broadcom is to treat the renewal as a strategic procurement event, not a vendor refresh. Build the alternative path in parallel. Time the close to your fiscal calendar and Broadcom's quarter end. Hold the executive sponsor accountable on cost outcome, not on the absence of disruption.
Closing thought
Broadcom is not VMware. The negotiation tactics that worked under the legacy VMware account team produce different outcomes under Broadcom. The customers who succeed are the ones who adapt fastest: they accept the new bundle structure, they invest in the inventory and alternative work, and they negotiate from a position of demonstrated optionality. The customers who fail are the ones who wait for the model to revert. It will not revert.
Redress Compliance is independent and 100 percent buyer side. We do not resell VMware. We do not partner with Broadcom. Our advisors have negotiated Broadcom VMware renewals across data center estates from 5,000 to 200,000 cores. If you are facing a renewal, an audit, or a board level commitment to bring VMware spend under control, the next step is a confidential briefing.
