- What Broadcom Changed About VMware Licensing
- VMware Cloud Foundation: The New Reality
- Price Impact: What Enterprises Are Actually Paying
- Your Transition Options and Trade-offs
- VMware Alternatives: Honest Assessment
- Negotiating with Broadcom: The Playbook
- VMware Compliance and Audit Risk Under Broadcom
- Support Model Changes: What You Need to Know
- All Topics in This Cluster
What Broadcom Changed About VMware Licensing
Broadcom completed the acquisition of VMware in November 2023. Within 90 days, Broadcom had announced changes to VMware's licensing model that affected every enterprise VMware customer globally. The headline changes were immediate and comprehensive:
Perpetual licences discontinued. VMware's perpetual licensing model — under which enterprises paid once for a software licence and separately for annual support — was eliminated. All new and renewal purchases moved to subscription-only licensing. Enterprises with active perpetual licences and valid support contracts can continue using them until support expires, but cannot renew on perpetual terms or add new perpetual licences.
Product portfolio collapsed. VMware's 70+ product family portfolio was rationalised to four core bundles: VMware Cloud Foundation (VCF) for full-stack infrastructure; VMware vSphere Foundation (VVF) for compute-only environments; VMware vSAN for storage; and a smaller set of standalone products for specific use cases. This eliminated the ability to purchase vSphere, NSX, or vSAN independently at competitive point-product pricing — customers who want NSX networking now must take VCF or accept significantly higher standalone pricing.
Per-core subscription model imposed. The primary licensing metric changed from per-socket (common in perpetual VMware licensing) to per-core subscription. This change alone, separate from the subscription vs perpetual dynamic, increased licence requirements for many enterprises with modern multi-core processors — a 2-socket server with 64 cores now requires 64 core licences rather than 2 socket licences.
Partner and reseller terms restructured. Broadcom significantly reduced the number of authorised VMware resellers, consolidating distribution through a smaller set of partners with higher revenue minimums. This reduced competitive tension in the reseller channel and made independent pricing benchmarking harder for enterprises.
"Broadcom's VMware strategy is textbook: acquire a dominant infrastructure platform, eliminate perpetual licensing, bundle products together, and extract maximum subscription revenue from a locked-in installed base. The playbook is not unique — but the scale and speed of execution is unprecedented in enterprise software."
VMware Cloud Foundation: The New Reality
VMware Cloud Foundation is Broadcom's flagship product bundle and the destination for most enterprise VMware customers. VCF includes vSphere, vSAN, NSX, vCenter, and Aria (formerly vRealize) operations management in a single per-core subscription. Understanding what VCF includes, what it does not include, and how the per-core count is calculated is foundational to any Broadcom negotiation.
What VCF Includes
VCF Standard includes vSphere Enterprise Plus, vSAN Enterprise, NSX Advanced, and vCenter. VCF Advanced adds additional Aria management capabilities, advanced security features, and expanded vSAN capabilities. Both tiers are per-core subscriptions applied to all physical cores on hosts enrolled in the VCF environment.
Importantly, VCF is a full-stack infrastructure bundle. Enterprises that only need compute virtualisation (vSphere) and do not need vSAN storage or NSX networking are overpaying for bundled capabilities they do not use. VMware vSphere Foundation (VVF) exists as a compute-only alternative — but Broadcom's pricing strategy positions VCF at a lower per-core rate than the individual product components, creating commercial pressure to adopt the full stack regardless of actual need.
Core Count Calculation
VCF core counts are calculated on all physical cores in enrolled VCF hosts — there is no sub-socket or sub-core pricing. A host with 2 processors × 32 cores per processor = 64 cores requires 64 VCF core licences. Minimum core counts per host apply (typically 16 cores per host), and minimum host counts per cluster apply in most VCF configurations.
The critical question in any VCF negotiation is whether Broadcom's proposed core count accurately reflects your actual deployed environment, or whether it includes hosts that should not be enrolled in VCF (development/test environments, edge deployments, or hosts running non-VMware workloads). We consistently identify 10–25% over-counting in Broadcom's initial VCF proposals — and eliminating those cores from the enrolled count materially reduces the subscription commitment.
Price Impact: What Enterprises Are Actually Paying
The price impact of the VMware to Broadcom transition varies significantly by the customer's previous licensing position. The following patterns emerge consistently from our client engagements:
Perpetual vSphere + Support Customers
Enterprises that previously paid annual VMware Support and Subscription (SnS) fees for perpetual vSphere, vSAN, and NSX licences are experiencing the largest absolute increases. A mid-size enterprise previously paying $800K per year in VMware SnS (for a 500-host environment) is typically being presented VCF subscription proposals in the range of $2.4M–$4M per year — a 3–5× increase. The increase reflects both the per-socket to per-core metric change and the full-stack bundling that includes NSX and vSAN even for customers who did not previously purchase them.
VMware ELA (Enterprise Licence Agreement) Customers
Customers who were previously on VMware ELAs with unlimited or broad deployment rights are experiencing the most significant commercial shock. ELA customers often had unlimited-use rights within their VMware environments — and Broadcom is converting them to per-core subscriptions that make the unlimited deployment right economically untenable. ELA customers that negotiated well at the ELA entry point now face renewal negotiations where Broadcom uses the transition as an opportunity to reset pricing to current list rates, eliminating the ELA discount position built over years of committed spend.
SMB and Mid-Market VMware Essentials Customers
Smaller VMware customers who were on vSphere Essentials bundles (designed for environments up to 3 hosts with 2 processors each) face a different challenge: the Essentials product tier was discontinued by Broadcom. These customers must either move to VCF (dramatically oversized for their environment) or migrate away from VMware entirely. For many smaller enterprises, this forced migration is accelerating their evaluation of Nutanix, Proxmox, and Azure Stack HCI as VMware replacements.
Your Transition Options and Trade-offs
Enterprise VMware customers currently face three broad strategic options, each with distinct cost, risk, and timeline profiles.
Negotiate VCF and Commit
Accept the transition to VCF subscription on the best negotiated terms available. Best for enterprises with deep VMware integration, limited internal cloud-native expertise, and a 3–5 year horizon before their next major infrastructure decision. The key is negotiating the transition terms — not accepting Broadcom's list pricing.
Parallel Evaluation: VCF + Alternative
Negotiate VCF for the near term while conducting a structured alternatives assessment. The evaluation process itself strengthens your Broadcom negotiating position by demonstrating credible alternatives. This is the optimal strategy for most enterprises with more than 200 VMware hosts.
Migrate to Alternative Platform
Accept the 12–36 month migration timeline and commit to an alternative hypervisor platform. Best for enterprises where Broadcom's pricing increase is truly untenable, where cloud-native migration is already planned, or where the environment is sufficiently standardised for a managed migration. Requires rigorous programme management and upfront transition cost modelling.
VMware Alternatives: Honest Assessment
Broadcom's pricing changes have accelerated interest in VMware alternatives to a degree not seen since the hypervisor market consolidated around VMware in the 2010s. The realistic alternatives for enterprise environments vary by use case and migration complexity.
Nutanix
Nutanix is the most commonly evaluated alternative for mid-to-large VMware environments. Nutanix AHV (the native Nutanix hypervisor) runs as a component of Nutanix's hyper-converged infrastructure platform, combining compute, storage, and networking in a single managed environment. Nutanix's VMware migration programme (Move) has handled thousands of enterprise migrations and the tooling has matured significantly.
The honest trade-off: Nutanix AHV is not feature-equivalent to vSphere for all workloads, particularly those with advanced vSphere-specific capabilities. The total migration cost — including hardware refresh for Nutanix-compatible nodes, staff retraining, application compatibility validation, and downtime risk management — is substantial and should be fully modelled before committing to a Nutanix migration as a cost-saving measure. See our VMware to Nutanix migration contract guide for the contractual framework.
Microsoft Azure Stack HCI
Azure Stack HCI is Microsoft's hyper-converged infrastructure offering, running on validated hardware and managed through Azure Arc. For enterprises with significant Microsoft footprints — particularly those running Windows workloads and already using Azure — Azure Stack HCI offers strong integration and licensing economics (Windows Server licences are included in the Azure Stack HCI subscription). Azure Stack HCI is not yet a replacement for VMware's full networking and security capabilities, but for Windows-centric workloads it is a credible and cost-effective alternative.
Cloud Migration (AWS, Azure, GCP)
For enterprises with a clear cloud strategy, the VMware transition is an accelerator for cloud migration rather than a trigger for hypervisor replacement. AWS VMware Cloud (VMC on AWS) offers managed VMware environments in AWS data centres, maintained by VMware operations staff, at a subscription rate that is typically cost-competitive with VCF on-premises for right-sized environments. Azure VMware Solution and Google Cloud VMware Engine offer equivalent managed VMware environments on their respective clouds. The cloud migration path preserves VMware operational knowledge while eliminating the Broadcom commercial relationship for the migrated workloads. See our VMware subscription migration guide for the step-by-step process.
Negotiating with Broadcom: The Playbook
Broadcom is a significantly harder negotiating counterparty than pre-acquisition VMware. Broadcom's commercial teams operate with less flexibility than VMware's did, escalation paths are compressed, and the relationship-based negotiation dynamics that characterised large VMware deals have been substantially replaced by process-driven commercial management. That said, VCF is negotiable — and enterprises with meaningful spend leverage consistently achieve better terms than those who accept Broadcom's initial proposals.
Core Count Forensics
The most consistently productive Broadcom negotiation lever is a rigorous independent review of the proposed VCF core count. Broadcom's migration team produces core count proposals based on available infrastructure data, and these proposals routinely include hosts that should not be enrolled (test/dev environments, decommission-eligible hosts, edge nodes, environments running non-VCF workloads). Reducing the enrolled core count by 15–25% directly reduces the subscription commitment by the same proportion — and is a factual exercise, not a commercial concession from Broadcom.
Multi-Year Commitment Leverage
Broadcom's financial model prioritises committed subscription revenue. Multi-year commitments (3 years is the standard, 5 years is available) generate meaningful discount leverage — typically 15–25% off annual list pricing for 3-year commitments and more for 5-year. The trade-off is commitment risk: committing to a 5-year VCF subscription limits your ability to respond to alternatives that may mature during that period. We generally recommend 3-year commitments as the optimal balance of discount leverage and strategic flexibility.
Credible Alternatives Pressure
Broadcom's negotiating teams are highly attuned to alternatives evaluations. Demonstrating a credible, documented Nutanix or Azure Stack HCI evaluation — complete with PoC results and migration cost modelling — provides commercial leverage that abstract alternatives threats do not. Broadcom account teams have finite authority to offer discounts; the alternatives evaluation creates the escalation path to decision-makers who can approve below-standard pricing.
Our negotiating with Broadcom: new playbook article covers the tactical detail, and the VMware Broadcom Survival Guide provides the full strategic framework including timing, escalation paths, and benchmark pricing data from our ongoing client engagements.
VMware Compliance and Audit Risk Under Broadcom
Broadcom has indicated that VMware compliance reviews — previously limited in scope and rarely punitive — will increase in frequency and consequence under its ownership. Enterprises that continue running perpetual VMware licences beyond their support end dates, or that deploy VMware software beyond contracted entitlements, face genuine audit risk in a way that was less common under VMware's prior commercial culture.
The specific audit risk areas to manage are: perpetual licences with expired support still in active production use; deployments that exceed the enrolled host count in a VCF subscription; use of VCF features included in a higher bundle tier than purchased; and affiliate or acquired entity deployments not covered by the enterprise's VCF agreement. See our VMware audit risk under Broadcom article and our virtualisation licensing audit risk guide for the detailed compliance framework.
Support Model Changes: What You Need to Know
Broadcom's changes to VMware support are as commercially significant as the licensing changes, and less well understood. Broadcom reduced VMware's support tier offering, changed response time SLAs for some configurations, and modified the technical support model in ways that affect enterprises with large, complex VMware environments.
The most important change for enterprise operations is the elimination of Broadcom's on-site VMware support for most environments — replaced by remote support delivered through Broadcom's consolidated support organisation. Enterprises with business-critical VMware environments that previously relied on on-site VMware technical support should reassess their support coverage and consider third-party VMware support options. See our Broadcom VMware support changes guide for the full analysis.
All Topics in This Cluster
This guide is the foundation article for The Negotiation Experts' VMware & Broadcom cluster. The following articles provide deep-dive treatment of specific aspects of the Broadcom VMware transition: