The situation.
The client is a US regional healthcare system operating 14 hospitals and 40+ ambulatory sites across two states. Its VMware footprint had grown to 6,800 cores across 410 hosts supporting EHR workloads, PACS imaging archives, clinical decision support, and the back-office estate. The bulk of the estate ran on vSphere Enterprise Plus perpetual licences, with a vSAN subscription overlay on the EHR cluster purchased eighteen months before the post-acquisition shift to subscription-only.
At the renewal window for the trailing Support & Subscription contract, Broadcom presented a single forward-only option: full conversion to VMware Cloud Foundation subscription, priced at $18.7 million for a three-year term. The quote was framed as the only available path; Broadcom's account team stated that vSphere standalone subscription was not available at the client's scale and that perpetual extension would not be offered.
The complication.
The client's clinical operations leadership had a hard requirement that any platform change could not introduce uncertainty into EHR availability during the open-enrolment cycle. That ruled out aggressive workload migration off VMware on the renewal timeline, which limited the client's perceived leverage. Broadcom's account team had built the quote around this assumption.
The underlying VCF quote priced 100% of the 6,800 cores at the full VCF bundle, including NSX, vSAN, Aria Operations, and HCX components the client did not deploy and did not plan to deploy in the next three years. Roughly 3,100 cores in the estate hosted workloads that had no functional dependency on the VCF differentiated components.
The response.
The defence team approached the conversion as a negotiation rather than an audit, but with the same evidence discipline. The first work-stream was a workload-level inventory cross-referencing vCenter inventory data against the application portfolio management system, classifying every host into one of three categories: VCF-dependent, VCF-eligible-but-not-dependent, and vSphere-only sufficient.
The classification produced a defensible 3,700-core VCF-justified subset against the 6,800-core total, with the remaining 3,100 cores documented as not requiring the VCF differentiators. The team built a parallel pricing model based on the client's contractual right to maintain perpetual licences in support for the trailing renewal period, alongside subscription pricing only on the VCF-justified subset.
The contractual challenge centred on two clauses in the existing master agreement: a clause preserving perpetual licence ownership independent of support status, and a clause requiring Broadcom to offer "comparable subscription products" at renewal where a product line is restructured. The team argued that vSphere standalone subscription remained a comparable product and that Broadcom's refusal to quote it created a contractual gap.
After four rounds of negotiation, the converted deal closed at $8.9 million over three years. The structure: VCF subscription on 3,400 cores covering the VCF-justified workloads, vSphere standalone subscription on 3,400 cores covering the rest, and the existing vSAN subscription preserved at renewal pricing. The settlement included a 30-day rebalance window each year allowing the client to shift the VCF/vSphere mix as workloads evolve.
The outcome.
The healthcare system reduced its three-year Broadcom spend by $9.8 million against the opening quote, a 52% reduction. The flex-rebalance clause materially improves the client's optionality for the next renewal cycle and creates a contractual reference for the parent organisation's other Broadcom-licensed business units.
The internal lesson is the workload-classification discipline. The client now maintains a quarterly host-to-workload-to-edition mapping, owned jointly by the cloud platform team and IT asset management, which feeds directly into the renewal-readiness pack twelve months ahead of any future contract event.
