$16 Million Saved:
Exiting Broadcom VMware Licensing

The Situation: A 230% Renewal Demand

In early 2024, the client — a Fortune 500 global logistics company operating 12 data centres across North America, Europe, and Asia-Pacific — received their VMware renewal proposal from Broadcom. The numbers were staggering.

Under the legacy VMware model, the company had maintained a suite of perpetual licences with annual support and subscription (SnS) contracts covering vSphere Enterprise Plus, vSAN, NSX, and vRealize across 4,200 ESXi hosts running approximately 38,000 virtual machines. Their annual VMware expenditure was approximately $6.9 million, a figure that had been relatively stable for years with modest annual increases.

Broadcom’s renewal proposal replaced the granular, per-socket perpetual licensing model with the new VMware Cloud Foundation (VCF) bundled subscription. Instead of licensing individual products on a per-socket basis, the client was required to purchase VCF — which bundled vSphere, vSAN, NSX, Aria, and other components — on a per-core subscription basis with a minimum 16-core-per-socket commitment. The proposed annual cost: $15.9 million — a 230% increase.

The proposal also eliminated the client’s perpetual licence entitlements. Under Broadcom’s new terms, existing perpetual licences would no longer receive security patches or support after the SnS expiration date. The client faced a binary choice: accept the 230% increase and migrate to the subscription model, or lose support on their entire virtualisation estate.

Why the Client Engaged Redress Compliance

The client’s IT procurement team had already attempted direct negotiation with Broadcom’s VMware sales organisation. The response was clear: VCF subscription was the only path forward, with minimal pricing flexibility. Broadcom offered a 12% discount from the $15.9M proposal — still representing a 190% increase over their current spend.

The client engaged Redress Compliance’s Broadcom Advisory practice to evaluate every available option: negotiate harder with Broadcom, migrate to alternative virtualisation platforms, adopt third-party support for their existing VMware estate, or implement a hybrid strategy. The engagement objective was straightforward: contain virtualisation costs as close to the historical $6.9M baseline as possible while maintaining full operational capability and security posture.

The Analysis: Mapping the VMware Estate

Our first action was a comprehensive audit of the client’s VMware environment. Before evaluating alternatives, we needed to understand exactly what was deployed, what was actively used, and what was contractually entitled.

Licence Entitlement Audit

We mapped every VMware licence the client held against their actual deployment. The findings were significant:

• 4,200 ESXi hosts running vSphere Enterprise Plus across 12 data centres
• 2,800 hosts utilising vSAN for hyper-converged storage (67% of estate)
• 1,400 hosts running NSX for network virtualisation (33% of estate)
• vRealize / Aria deployed on 3,100 hosts for operations management
• 820 hosts (19.5%) running only base vSphere — no vSAN, no NSX, no Aria — yet Broadcom’s VCF proposal required them to pay for the full bundle
• 340 hosts (8%) with utilisation below 15%, candidates for consolidation and decommission

The audit revealed that under Broadcom’s VCF model, the client would be paying for vSAN, NSX, and Aria capabilities on 1,400 hosts that didn’t use them — and paying for 340 hosts that could be eliminated entirely through consolidation. The forced bundling alone inflated the cost by approximately $3.2 million annually for unused capabilities.

Workload Classification

We classified every virtual machine by criticality, performance requirements, and migration complexity:

• Tier 1 — Mission-Critical (22%): Production ERP, global logistics platform, financial systems. Zero tolerance for migration risk. 8,360 VMs across 920 hosts.
• Tier 2 — Business-Important (41%): Customer-facing applications, business intelligence, middleware. Short maintenance windows acceptable. 15,580 VMs across 1,720 hosts.
• Tier 3 — Standard (37%): Development, testing, internal applications, non-production environments. Flexible migration windows. 14,060 VMs across 1,560 hosts.

The Strategy: A Three-Phase Exit

Based on the audit findings and workload classification, we designed a three-phase strategy that balanced cost reduction, operational risk, and execution feasibility. The strategy was not a single-vendor replacement — it was a portfolio approach that matched each workload tier to the optimal cost and risk profile.

The Savings Breakdown

Why Third-Party Support Was the Critical Lever

The strategy’s success hinged on third-party VMware support — the ability to continue running existing VMware software with full enterprise-grade support without paying Broadcom’s subscription fees. This is the single most important tool available to enterprises facing Broadcom’s VMware pricing escalation, and it is widely misunderstood.

How Third-Party VMware Support Works

Third-party support providers (Rimini Street, Spinnaker Support, and others) deliver the same core support services that Broadcom’s SnS programme provides: security patching, bug fixes, configuration guidance, and 24/7 technical support. They maintain teams of former VMware engineers who develop and test patches independently of Broadcom. The client continues running their existing VMware software versions — vSphere, vSAN, NSX — with no changes to the production environment.

What Third-Party Support Does Not Provide

Third-party support does not provide access to new VMware product versions or feature updates. If Broadcom releases vSphere 9, third-party-supported customers cannot upgrade to it. This is acceptable for enterprises running stable, mature VMware environments where the current version meets all operational requirements — which describes the vast majority of large VMware deployments. The client’s Tier 1 workloads had been running on the same vSphere version for two years with no planned version upgrades.

The Risk Assessment

Our engagement included a comprehensive risk assessment of the third-party support model. Key findings:

• Security patching: Third-party providers have demonstrated track records of delivering critical security patches within 24–72 hours of CVE disclosure, comparable to Broadcom’s response times
• SLA commitments: 15-minute initial response for critical severity issues, 24/7/365 coverage, named account engineers — matching or exceeding Broadcom’s standard support tiers
• Regulatory compliance: Third-party support satisfies SOC 2, PCI-DSS, and HIPAA compliance requirements for software maintenance and patching obligations
• Contract flexibility: Annual terms with no multi-year lock-in, allowing the client to return to Broadcom or migrate further at any point without penalty

The Migration Execution

Workload migration — moving virtual machines from VMware to Nutanix AHV and Red Hat OpenShift — was the most operationally complex element of the engagement. We managed this through a structured approach that prioritised zero-downtime outcomes.

Migration tooling: We deployed Nutanix Move for VMware-to-AHV migrations, which provides near-zero-downtime VM migration through continuous data replication. VMs are replicated in real time to the target AHV cluster, with a final cutover window of under 30 seconds. For the Red Hat migrations, we used virt-v2v tooling with pre-staging to minimise cutover windows.

Validation framework: Every migrated workload passed through a four-gate validation process: pre-migration compatibility assessment, post-migration functional testing, 48-hour burn-in monitoring, and production sign-off by the application owner. No workload was declared “complete” until all four gates were passed.

Rollback capability: Throughout the migration, original VMware VMs were retained in a suspended state for 30 days post-cutover, providing instant rollback capability if any issue emerged in the migrated environment. Zero rollbacks were required during the engagement.

Client Testimonial

Lessons for Enterprises Facing Broadcom’s VMware Pricing

This engagement reinforced several principles that apply to any enterprise navigating Broadcom’s VMware licensing restructuring:

You have more options than Broadcom wants you to believe. Broadcom’s sales narrative is binary: accept VCF or lose support. The reality is that third-party support, alternative platforms, and hybrid strategies provide credible, enterprise-grade alternatives that can reduce costs by 50–70% compared to Broadcom’s proposals.

Audit before you negotiate. This client was overpaying for capabilities they didn’t use even before Broadcom’s increase. The forced VCF bundle amplified the waste. A thorough estate audit identifies the actual cost of what you need versus what you are being asked to buy. Download our Broadcom VMware Renewal Survival Kit for the audit framework.

Phase the transition. Moving 4,200 hosts overnight is neither feasible nor necessary. A phased approach — third-party support for critical workloads first, alternative platform migration for flexible workloads second — manages risk while delivering savings immediately. Phase 1 of this engagement delivered savings from Month 1 while Phases 2 and 3 were still in execution.

Third-party support is not a temporary fix. Enterprises often view third-party support as a stop-gap. For mature, stable VMware environments, it is a permanent, cost-effective strategy. This client’s 2,300 hosts on third-party support have experienced no degradation in support quality, security posture, or operational capability in the 12 months since transition.

The competitive landscape is your ally. Nutanix, Red Hat, Microsoft Hyper-V, and Proxmox are all investing aggressively in VMware migration tooling and competitive pricing specifically to capture enterprises fleeing Broadcom. Use this competitive dynamic to negotiate favourable terms with alternative vendors. For comprehensive guidance on evaluating all options, explore our Broadcom Advisory Services and the Broadcom Knowledge Hub.