VMware Broadcom Guide 2026:
The Enterprise Licensing Playbook

In November 2023, Broadcom completed its $61 billion acquisition of VMware — the largest technology deal in history at that time. Within three months, Broadcom had eliminated perpetual licensing, cancelled most standalone VMware products, replaced them with mandatory bundled subscriptions, terminated thousands of channel partners, and announced price increases that left virtually every VMware enterprise customer facing a bill two to ten times higher than before.

This guide is built on direct advisory engagement with over 60 enterprises navigating Broadcom's new VMware commercial model since the acquisition closed. The patterns are consistent: customers who approach this reactively pay maximum price; customers who plan their response commercially — whether negotiating VCF terms or credibly executing migration — recover most of the forced increase. The playbook is here.

What Broadcom Changed — and Why It Matters

Broadcom's transformation of VMware followed a well-established pattern the company has applied to CA Technologies, Symantec, and other acquired software businesses: rationalise the product portfolio, eliminate the channel, move all customers to subscription, and extract maximum commercial value from the installed base. Understanding the specific changes is essential before any commercial strategy can be designed.

End of Perpetual Licensing

In February 2024, Broadcom formally discontinued all VMware perpetual licenses. Products including vSphere, vSAN, NSX, vCenter, and all Aria (formerly vRealize) management tools are now sold exclusively as subscriptions through two primary bundles: VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF). Existing perpetual license holders retain the right to run their software under original license terms, but cannot renew perpetual licenses, purchase new perpetual licenses for expansion, or access new versions without transitioning to subscription.

Product Portfolio Rationalisation

Broadcom cancelled approximately 56 standalone VMware products, including vSphere Standard, vSAN Standard, Horizon (standalone), Workspace ONE (standalone), NSX Standard, and numerous specialist products. Customers using these products are directed to VMware Cloud Foundation as the primary replacement — a significantly broader bundle that includes capabilities many customers do not need, at a significantly higher price than the standalone products they are replacing.

Partner Channel Elimination

Broadcom terminated approximately 2,200 VMware channel partners within 60 days of the acquisition closing, consolidating the partner network to approximately 50 global elite partners. For enterprise buyers, this means that long-standing reseller relationships that provided pricing flexibility, implementation support, and commercial negotiation assistance are largely gone. Negotiation now happens directly with Broadcom's enterprise sales organisation or through a small number of remaining elite partners.

Support Model Changes

VMware's Basic and Production support tiers were discontinued. All subscriptions include what Broadcom calls "Production Support" as standard, but the practical effect for many customers has been degraded support quality during the transition period as Broadcom restructured VMware's support organisation. Customers with mission-critical VMware deployments should specifically negotiate support response time SLAs and escalation procedures into their VCF agreements.

Understanding VCF Subscription Pricing

VMware Cloud Foundation is now Broadcom's primary product for enterprise datacenter virtualisation. Understanding how VCF is structured and priced is the foundation of any commercial analysis.

VCF Bundle Components

VMware Cloud Foundation includes vSphere (compute virtualisation), vSAN (software-defined storage), NSX (network virtualisation and security), and Aria Suite (formerly vRealize — cloud management, operations, automation, and log analytics). The bundle is designed to be comprehensive but this comprehensiveness is also the primary source of pricing controversy: most organisations use vSphere as their core platform and have separate, often superior solutions for storage, networking, and management. Paying for the full VCF bundle when only vSphere is needed is a significant inefficiency.

VCF Pricing Structure

VCF is priced per physical CPU core, not per socket or per virtual machine. Broadcom list pricing for VCF Standard is approximately $90 per core per year; VCF Advanced is approximately $130 per core per year. These are list prices — enterprise customers with multi-year commitments and significant core counts negotiate discounts of 20–40% off list in competitive situations.

To illustrate the practical impact: a standard enterprise rack server contains 2 physical CPUs with 32 cores each — 64 cores per server. At VCF Standard list pricing, that server costs $5,760 per year. A 50-server datacenter carries a VCF cost of approximately $288,000 per year at list, increasing to approximately $580,000 per year for 100 servers. Before Broadcom's changes, the same 100-server deployment running vSphere Enterprise Plus with perpetual licenses and annual support typically cost $100,000–$180,000 per year.

VMware vSphere Foundation (VVF)

Broadcom also offers VMware vSphere Foundation (VVF) as a lower-cost option that includes vSphere and vCenter but excludes vSAN and NSX. VVF list pricing is approximately $50–$65 per core per year. VVF is appropriate for organisations that have independent SAN storage solutions and separate network virtualisation capabilities and genuinely do not need vSAN or NSX included in the bundle. It is worth noting that Broadcom's sales team will consistently steer customers toward VCF — VVF requires a deliberate commercial argument.

Subscription Term and Renewal Mechanics

VCF and VVF subscriptions are sold in 1-year, 2-year, and 3-year terms. Multi-year commitments attract meaningful discounts: 2-year terms typically unlock an additional 10–15% beyond negotiated annual pricing, and 3-year terms an additional 20–25%. The trade-off is contractual lock-in during a period when the alternative landscape is evolving rapidly. A well-negotiated 3-year VCF agreement should include technology refresh rights, exit provisions if Broadcom materially changes the product, and price caps on the renewal following the initial term.

Calculating Your True Cost Increase

The headline "200–1,200% price increase" is accurate but requires context to be actionable. Your actual cost increase depends on four variables: your existing licensing baseline, your current core count, how Broadcom maps your products to VCF or VVF, and what discount you can negotiate.

Establishing Your Baseline

Your licensing baseline is the total annual cost of your VMware software under the previous model — perpetual license amortisation (typically 7-year straight-line) plus annual support and subscription (SnS). For a 100-socket deployment running vSphere Enterprise Plus (the most common enterprise edition), annual SnS cost before the acquisition was typically $80,000–$150,000 per year, with the perpetual license already amortised. The transition to VCF subscription eliminates the concept of "paid-up" perpetual value and requires full annual payment for all capabilities.

Core Count Accuracy

VCF is priced on physical CPU cores, which means your actual server hardware specification directly drives cost. A common error in initial VCF cost projections is using socket counts rather than core counts, or failing to account for future hardware refreshes. Modern server CPUs carry 32–64 cores per socket; a 4-socket server from 2024 may have 256 physical cores. Validate your actual core counts through your CMDB or infrastructure management platform — Broadcom's initial quotes frequently use estimated core counts that can be challenged.

Product Mapping Disputes

When Broadcom maps your existing products to their new portfolio, they have a commercial incentive to assign you to VCF even if VVF accurately covers your requirements. A disciplined product mapping review — comparing every VMware product you use against both VCF and VVF feature sets — frequently reveals that VVF adequately covers the majority of your workloads. Organisations that accept Broadcom's initial product mapping without challenge consistently overpay by 20–40% relative to what an accurate mapping would require.

Perpetual License Holders: Your Options

If your organisation holds perpetual VMware licenses, your commercial position is more nuanced than those already on subscription. Understanding your rights is the foundation of your negotiating position.

Continued Use Rights

Perpetual licenses grant the right to run the licensed version of the software indefinitely without additional payment. Broadcom cannot force you to transition to subscription immediately — your perpetual license rights are contractually protected. However, you will eventually face the need to upgrade vSphere and supporting products, and new versions are only available through subscription. The practical window for perpetual-only operation is 3–5 years from the acquisition closing, after which underlying hardware, security, and compatibility requirements will drive a transition decision.

Support Transition Decisions

Broadcom is offering time-limited support for perpetual license holders, but the support terms have changed. General Support for vSphere 7 runs through October 2025; vSphere 8 perpetual general support runs through October 2027. After these dates, customers require subscription for support access. The support end date is often the most important commercial trigger — many organisations will prefer to negotiate VCF terms or complete a migration before their support coverage lapses rather than operating unsupported infrastructure.

The Leverage Window

Perpetual license holders have a leverage window that pure subscription customers lack: the credible threat of "staying on perpetual until migration is complete" is a genuine commercial alternative that reduces Broadcom's urgency to close a subscription deal. Use this window strategically. The most commercially effective approach is to begin a genuine competitive evaluation of alternatives, develop a credible migration plan with timeline and cost, and then approach Broadcom for subscription pricing with that plan as documented evidence of your BATNA (Best Alternative to a Negotiated Agreement).

How to Negotiate with Broadcom VMware

Broadcom has a fundamentally different commercial philosophy than legacy VMware. Pre-acquisition VMware was relationship-oriented, with significant flexibility on pricing, bundling, and terms. Post-acquisition Broadcom operates with more rigid pricing floors, less empowered sales representatives, and greater emphasis on account-level revenue targets. Effective negotiation requires adapting to this new environment.

Develop a Credible BATNA First

The most effective single action you can take before engaging Broadcom on pricing is to develop a documented, costed migration alternative. This does not mean committing to migration — it means being able to demonstrate, with specificity, that you have evaluated an alternative, have a migration plan with timeline and budget, and are prepared to execute it. Without a credible alternative, you are negotiating from a position of dependency. With a credible alternative, the commercial conversation changes materially. Organisations that have invested 4–8 weeks in a genuine alternative evaluation consistently achieve 25–35% better pricing than those who negotiate without one.

Multi-Year Commitments as Leverage

Broadcom values revenue certainty. Offering a 3-year VCF or VVF commit in exchange for a significant price reduction is a genuinely effective tactic — Broadcom will typically respond with 20–30% discounts on multi-year terms relative to their initial annual pricing. The contract must include escalation caps (no more than 3–5% per year on renewal), exit provisions for material product changes, and technology refresh rights so you are not locked into paying for obsolete hardware core counts as your infrastructure evolves.

Right-Size Your Core Count

Before accepting any VCF quote, conduct a thorough workload consolidation exercise. Server virtualisation ratios have improved dramatically with modern hypervisors, and many enterprise deployments carry legacy over-provisioned physical infrastructure. Reducing your licensed core count by 15–25% through consolidation before the VCF negotiation is legitimate, commercially significant, and entirely within your rights. Broadcom cannot force you to license more cores than you actually deploy.

Challenge the Product Mapping

As noted above, Broadcom's initial product mapping consistently targets VCF. A formal written challenge to the product mapping — specifying which VCF components you do not use, with evidence from your current environment — frequently results in acceptance of VVF pricing for a significant portion of your deployment. This challenge must be documented and provided to Broadcom in writing, not merely raised verbally in a sales call.

Engage at the Right Level

Broadcom's field sales representatives have limited pricing authority — meaningful discounts require approval from regional or global deal desk. Structure your engagement to trigger this escalation from the outset: submit a formal deal request with competitive alternatives documented, request escalation to the deal desk directly, and ensure your request is framed in terms of total account value and multi-year commitment rather than individual product pricing. Advisory firms including Redress Compliance, who specialise in enterprise VMware negotiations, maintain current deal benchmarks that establish what sophisticated buyers actually pay — independent benchmarking provides significant leverage in these conversations.

When Migration Makes Commercial Sense

Migration away from VMware is the right answer for some organisations and the wrong answer for others. The decision framework is based on three calculations: the cost increase multiple, the migration cost, and the strategic direction of your infrastructure.

The Cost Increase Multiple Threshold

Migration makes financial sense when the net present value of migration costs (including professional services, testing, retraining, and productivity loss) is less than the net present value of the additional VMware cost over a 5-year period. As a practical rule of thumb, if your Broadcom VMware cost increase is less than 3× your previous spend, migration rarely makes financial sense when fully costed. Above 5× increases, migration is almost always financially justified over a 3–5 year horizon even accounting for significant migration complexity. The 3–5× range requires detailed analysis.

Strategic Cloud Direction

Organisations executing a significant cloud migration (moving 40%+ of workloads to AWS, Azure, or GCP within 3 years) face a different calculation. If on-premises VMware is a diminishing base that will be replaced by cloud infrastructure, the argument for investing significant migration effort into an alternative hypervisor is weaker — the better investment may be accelerating the cloud migration itself. Organisations with large, stable on-premises footprints that are not cloud-migrating are the clearest candidates for hypervisor migration.

Migration Complexity Factors

VMware-specific capabilities that create migration complexity include vSphere-integrated application platforms (NSX-T networks, vSAN policies embedded in application configurations), vSphere APIs used by backup, security, and monitoring tools, vSphere-specific disaster recovery configurations (Site Recovery Manager), and Horizon VDI deployments. Each of these requires specific migration planning beyond the hypervisor move itself. Organisations with extensive use of these capabilities face materially higher migration costs and timelines than those running vanilla VM workloads.

Migration Planning Framework

For organisations that have determined migration is commercially justified, a structured migration approach significantly reduces risk, cost, and timeline. The following framework reflects best practice from engagements where migration was successfully executed.

Phase 1: Inventory and Dependency Mapping (Weeks 1–4)

Begin with a complete inventory of every virtual machine in your VMware environment, including VM size, OS, application dependencies, network configuration, storage policy, backup method, and any vSphere-specific APIs or integrations in use. This inventory is the foundation of migration scoping — attempting to migrate without this data consistently produces surprises that delay and over-run projects. Tools including Broadcom's own vSphere Replication, Nutanix Move, and Azure Migrate provide automated VM discovery that accelerates this phase.

Phase 2: Wave Planning and Pilot (Weeks 5–12)

Group VMs into migration waves based on complexity and criticality. Wave 1 should be low-complexity, non-production workloads that allow your team to build operational experience on the target platform. Waves 2–4 progress through development, test, and staging environments. Production workloads migrate in final waves once the team has validated the target platform and migration tooling. A typical enterprise migration of 500–2,000 VMs takes 12–18 months for the production wave using this approach.

Phase 3: Parallel Operation and Cutover

Running the VMware and alternative platform environments in parallel during migration is operationally complex but essential for risk management. Define clear cutover criteria — application-level performance benchmarks, backup validation, monitoring coverage — before committing to production cutover. Many organisations discover during parallel operation that specific applications require remediation before migration; identifying these early preserves the migration timeline.

See our detailed guide: VMware Migration Planning: When to Stay, When to Move for wave planning templates and timeline benchmarks.

Frequently Asked Questions

How much did Broadcom increase VMware prices?

Broadcom increased VMware pricing by 200–1,200% for many enterprise customers. Organizations running vSphere on a per-CPU perpetual basis saw effective annual costs rise 3–12× when transitioning to VMware Cloud Foundation (VCF) subscription bundles. A typical 100-CPU deployment that paid $150,000 per year in perpetual plus support now faces VCF subscription costs of $500,000–$900,000 annually.

Did Broadcom end VMware perpetual licensing?

Yes. Broadcom discontinued perpetual VMware licenses in February 2024. All products are now sold exclusively as subscriptions through VCF and VVF bundles. Existing perpetual license holders can continue running their software under original license terms but cannot renew or expand perpetual deployments.

What is VMware Cloud Foundation and how is it priced?

VCF bundles vSphere, vSAN, NSX, and Aria Suite into a single per-core subscription. List pricing is approximately $90–$130 per core per year depending on edition. Enterprise buyers with multi-year commitments and competitive alternatives negotiate 20–40% off list.

Should enterprises migrate away from VMware?

The decision depends on cost increase magnitude, migration complexity, and strategic cloud direction. Enterprises facing 5×+ increases with manageable migration paths should evaluate alternatives seriously. Enterprises with 2–3× increases and complex VMware-dependent applications typically find renegotiation more cost-effective than migration when fully costed.

How do you negotiate with Broadcom on VMware pricing?

Effective tactics include developing a genuine competitive evaluation as BATNA, negotiating multi-year terms (3-year commits unlock 25–35% discounts), right-sizing core counts through consolidation, formally challenging Broadcom's product mapping, and engaging at deal desk level with documented competitive positioning. Specialist advisory firms maintain current deal benchmarks that establish what sophisticated buyers actually pay.

What are the best VMware alternatives?

Leading alternatives include Nutanix AHV (most direct VMware replacement, strong enterprise support), Microsoft Azure Stack HCI (ideal for Microsoft-centric organisations), Red Hat OpenShift Virtualization (Kubernetes-native, cloud-native transformation), and Proxmox VE (open source, lower-complexity environments). Selection depends on existing infrastructure, cloud strategy, and operational team skills. Read our detailed comparison: VMware Alternatives: Nutanix, Hyper-V, OpenShift Compared.