Acquisition Timeline and Immediate Changes
Broadcom's acquisition of VMware closed on 22 November 2023. Within weeks, Broadcom began executing a transformation of VMware's commercial model that was among the most aggressive post-acquisition vendor pivots in enterprise technology history. Unlike many acquisitions that allow acquired companies to operate independently for a transition period, Broadcom moved immediately to implement structural changes that would directly affect every VMware customer's contract and cost position.
Acquisition Close & Immediate Actions
Broadcom closes VMware acquisition. Immediately announces end of perpetual licence sales. All perpetual licence orders in-flight are cancelled or converted. Broadcom CEO Hock Tan publicly states VMware will be restructured around subscription revenue.
Product Portfolio Consolidation Announced
Broadcom announces VMware product catalogue will be reduced from 70+ product families to approximately 4 core bundles. Partners and customers given 30-day notice of catalogue changes. Hundreds of standalone SKUs discontinued.
New Pricing & Bundles Take Effect
VMware Cloud Foundation (VCF) becomes the primary enterprise offering. VMware vSphere Foundation (VVF) introduced as a standalone compute option. New per-core subscription pricing begins. Migration credits offered to existing perpetual customers with conditions.
Support Contract Renewals Discontinued
Broadcom formally ends the sale of perpetual licence support renewals. Customers with active perpetual support contracts are honoured through existing term, but cannot renew. All new support must be via VCF or VVF subscription.
Partner Channel Restructuring Completed
VMware's 4,000+ reseller partner network reduced to approximately 300 selected Broadcom Premier Partners. Many former VMware partners lose authorisation to sell VMware products. Service provider licensing agreements (VSPP) terminated, disrupting hundreds of managed service providers.
End of Perpetual Licences: The Full Picture
The end of VMware perpetual licences is the single most consequential change Broadcom made — but the full implications are more nuanced than most coverage has communicated. Understanding the distinction between licence ownership, support access, and software currency is essential for enterprise planning.
What "End of Perpetual Sales" Actually Means
Broadcom ended the sale of new perpetual VMware licences. This is distinct from voiding existing perpetual licences that customers already hold. If your organisation purchased vSphere Enterprise Plus perpetual licences prior to the acquisition, you still own those licences. Broadcom cannot legally void a licence contract you already hold, and the software continues to function on the hardware you installed it on.
What has ended is your ability to purchase additional perpetual licences, expand your perpetual licence estate, or renew perpetual support contracts. As your existing support contracts expire — and for many organisations this is now imminent — you will either move to VCF/VVF subscription, or continue running without vendor support.
The Support Expiry Problem
The practical mechanism forcing migration is support expiry. VMware perpetual licences remain functional after support expiry — the software will continue to run. But without active support, you lose access to security patches, bug fixes, new hardware compatibility, and technical support cases. For most enterprise environments subject to security compliance frameworks (ISO 27001, SOC 2, PCI DSS, FedRAMP, HIPAA), running unsupported hypervisor software in production is a compliance violation, not just a commercial inconvenience.
"The support contract expiry is the real enforcement mechanism. Broadcom doesn't need to turn off your software — it simply stops patching it, and your compliance team does the rest."
Most enterprise perpetual VMware support contracts were 1–3 year terms. If you renewed last in 2022 or 2023 on a 3-year term, your support likely expires in 2025 or 2026. At that point, the choice between running unsupported VMware or migrating to VCF becomes unavoidable.
Perpetual Licence Versions and End of General Support
Broadcom has also issued formal End of General Support (EOGS) dates for perpetual VMware versions. vSphere 7 reached EOGS in April 2025. vSphere 8 will reach EOGS in October 2027 for customers on perpetual licences. After EOGS, Broadcom provides no patches whatsoever — not even critical security updates. For organisations that want to avoid VCF subscription costs, the time available to plan alternatives is shorter than it may appear.
SKU Consolidation: From 70+ Products to 4 Bundles
One of the least discussed but most disruptive Broadcom changes is the elimination of most of VMware's product catalogue. Enterprises that built detailed, component-level architectural designs around specific VMware products found that many of those products were simply discontinued — forcing re-evaluation of infrastructure plans that had been approved and partially funded.
| Previous VMware Product | Status Under Broadcom | Current Path |
|---|---|---|
| vSphere Enterprise Plus (perpetual) | Discontinued | Migrated to VCF or VVF subscription |
| vSAN (standalone) | Discontinued | Included in VCF; not sold separately |
| NSX (standalone) | Discontinued | Included in VCF; not sold separately |
| vCenter Server (standalone) | Discontinued | Included in VCF and VVF subscriptions |
| Horizon Universal Licence | Discontinued | Merged into VMware Horizon (subscription only) |
| VMware Cloud Foundation (VCF) | Active | Primary enterprise bundle — all core components |
| vSphere Foundation (VVF) | Active | Compute-only subscription without NSX/vSAN |
| vSphere Essentials Plus Kit | Active | SMB offering; 3-host cluster limit |
| vRealize Suite (automation/operations) | Discontinued as standalone | Components absorbed into VCF add-ons or Aria Suite |
| Workspace ONE (standard/advanced) | Discontinued multiple editions | Consolidated to Workspace ONE UEM and Intelligence |
The functional impact of SKU consolidation is that customers who previously purchased components individually — for example, vSphere without vSAN, or NSX without vSphere — are now required to purchase the full VCF bundle regardless of which components they actually use. For organisations with existing vSAN or NSX deployments that had been separately licenced, this has two effects: they may be paying for capabilities they already have; and they lose the ability to renegotiate individual component pricing based on competitive alternatives.
VCF Pricing and the Per-Core Model
VMware Cloud Foundation is priced on a per-core subscription basis. Every physical processor core in a cluster that runs VMware must be licenced — including cores that are not actively running workloads. This is a fundamental departure from the per-socket perpetual pricing model that governed VMware licensing for the previous fifteen years.
How the Per-Core Count Works
Broadcom counts physical processor cores, not logical cores (threads). A modern server with two processors, each with 32 physical cores, requires 64 VCF core licences regardless of whether all cores are in active use. Clusters are licenced in totality — you cannot licence a subset of a cluster's cores. This means that infrastructure right-sizing decisions — which had previously been somewhat decoupled from licensing cost — now directly affect the VCF invoice.
Previous: Per-Socket Perpetual
VMware vSphere Enterprise Plus was licenced per physical processor socket. A 2-socket server required 2 licences regardless of core count. Purchasing support was a separate annual renewal. Licences owned permanently after purchase.
Current: Per-Core Subscription
VCF is licenced per physical processor core, with no perpetual ownership. All cores in a licenced cluster must be covered. Subscription includes support. Annual recurring cost that does not reduce over time.
Migration Credit Mechanics
Broadcom offered migration credits to customers transitioning from perpetual licences to VCF subscriptions. The credits were designed to reduce the first-year cost differential and were presented as a commercial concession. In practice, migration credits are heavily conditioned: they typically require a minimum 3-year VCF commitment; the credit is applied against the first year only; the credit does not transfer to per-core pricing — it reduces the total invoice, creating a lower effective per-core rate in year one that normalises to full VCF pricing from year two; and the credit calculation is often based on Broadcom's own mapping of your perpetual estate to VCF, which frequently over-assigns core requirements.
We have reviewed dozens of Broadcom migration credit proposals, and in the majority of cases the client's actual core requirement was 15–35% lower than Broadcom's proposed licence count. Challenging the core count is typically the highest-value action an enterprise can take before signing a VCF commitment.
Support Model Overhaul
Broadcom fundamentally changed VMware's support model in ways that enterprises are still navigating. The changes affect both the commercial structure of support and the delivery model.
Under legacy VMware, support was a separate annual renewal on top of perpetual licence cost. Under VCF subscription, support is bundled into the subscription — you cannot purchase VCF without support. This is presented as simplification, but functionally it means support cost cannot be benchmarked or negotiated independently from software cost. Broadcom's support tiers are now Premium (standard) and Mission Critical (elevated), with significant price differences between them.
Broadcom also restructured the support delivery model, centralising support through a smaller number of global support centres and reducing the number of dedicated technical account manager relationships available to customers at standard support tiers. Customers who previously had named support engineers are now navigating shared support pools. For enterprises where VMware stability is business-critical, this service level reduction has been a significant friction point in VCF adoption discussions.
Partner Channel Disruption
VMware historically operated one of the largest enterprise software partner ecosystems in the industry — over 4,000 authorised resellers and thousands of service provider partners using the VMware Service Provider Programme (VSPP). Broadcom terminated VSPP entirely in 2024, immediately disrupting managed service providers and cloud hosters who had built service offerings around VSPP licensing. The elimination of the broader reseller network concentrated VMware sales through approximately 300 Broadcom Premier Partners.
For enterprise buyers, this channel restructuring has practical procurement implications. Your existing VMware reseller relationship may no longer be authorised, meaning your procurement team must re-establish relationships with Broadcom's smaller approved partner list. Price transparency also decreased — the reseller ecosystem that previously provided competitive quoting has been replaced by a more controlled distribution model where Broadcom exerts tighter control over pricing floors.
See our full analysis of the VMware/Broadcom complete guide for the negotiation implications of the channel restructure.
What Enterprise IT Must Do Now
The Broadcom VMware changes are not a future concern — they are an active commercial and compliance challenge for every enterprise currently running VMware. The actions below are sequenced by urgency.
Step 1: Audit Your Current Licence Position
Before you can negotiate or plan migration, you need an accurate inventory of what you own: perpetual licence versions and quantities; active support contract expiry dates; which VMware products are deployed in which clusters; and actual core counts per cluster. This baseline is essential both for negotiating with Broadcom and for evaluating migration costs realistically. Many organisations discover their perpetual licence position is more complex than procurement records indicate — particularly where VMware was deployed via OEM agreements with hardware vendors.
Step 2: Model Your VCF True-Up Cost
Using your actual core counts (not Broadcom's proposed counts), calculate what VCF subscription would cost over a 3-year and 5-year horizon. Include the current list price per core, your likely tier (standard VCF vs VCF+), support tier, and any anticipated core count growth. Compare this to your current all-in VMware cost (perpetual amortisation + support). For most mid-to-large enterprises, this comparison will show VCF representing a 200–400% increase in annualised cost.
Step 3: Develop a Parallel Alternatives Track
Even if you intend to stay on VMware long-term, a credible alternatives evaluation is your most powerful negotiating tool. Broadcom knows that organisations with sunk VMware investment and deep integration dependencies are unlikely to migrate quickly — but the credibility of an alternatives assessment (whether to Nutanix, Azure Stack HCI, or cloud-native hypervisors) materially affects what concessions Broadcom will offer. We recommend commissioning a formal alternatives assessment with a migration cost model before entering VCF negotiations.
Step 4: Engage Broadcom with Leverage
The ideal negotiating position combines a realistic migration timeline (not a threat that nobody believes) with a committed multi-year VCF term that gives Broadcom the revenue certainty it wants in exchange for price concessions. Broadcom's primary commercial objectives are subscription revenue scale and multi-year commitment depth. Enterprises that commit to 3–5 year VCF terms and consolidate their VMware estate have achieved 25–40% discounts from list price — but only when the negotiation was structured around Broadcom's objectives rather than simply asking for a discount. Read our VMware Broadcom Survival Guide for the full negotiation playbook.
The Broadcom VMware transition is still evolving. Price adjustments, support model refinements, and product bundle modifications continue to emerge. For organisations navigating a VCF migration or renewal negotiation, current intelligence from advisors with active Broadcom engagement visibility is as important as any published guide. Contact our team for a current assessment of your specific VMware position.