Home / Case Studies / Broadcom VMware Relicensing
Broadcom / VMwareTelecomVCFPer-Core

VMware re-license capped at $18.7M below the opening Broadcom position.

A European telecom operator faced the Broadcom transition mid-cycle: a vSphere estate of roughly 9,000 cores rolled into a VCF per-core subscription, with an opening proposal that priced the same workload at nearly 4x the prior perpetual TCO. Twenty weeks later, the operator signed a 36-month VCF subscription $18.7M below the opening number and kept a documented exit path on two alternative hypervisors.

Data centre server racks at scale
$18.7M
Three-year saving
42%
Reduction vs. opening proposal
20 wk
Kick-off to signature
2
Hypervisor exit paths preserved
The contract going in

Perpetual vSphere, support drift, no leverage.

The operator's estate had been built on perpetual vSphere licences with predictable Support & Subscription. The Broadcom acquisition removed both the perpetual option and the SnS continuity, replacing them with a per-core VCF subscription priced against a workload model the operator had never validated.

  • 9,200 vSphere cores across two production regions and a DR site.
  • NSX in production on a subset of the estate; vSAN deployed for tier-2 workloads only.
  • SnS lapsing inside the renewal window with no grace beyond the published cut-off.
  • Internal modernisation roadmap that already named two alternative hypervisors as 24-month candidates.
Broadcom's opening position

Full estate to VCF, uplift, three-year lock.

Broadcom proposed VCF per core across the entire 9,200-core estate, on a three-year term with an annual uplift inside the term and a renewal uplift that would have re-priced cores against then-current list. The proposal bundled NSX and vSAN into the per-core unit irrespective of whether the operator used them.

What we flagged

The proposal sized VCF against the whole estate, not the workload that actually required VCF capability. Two-thirds of the cores were running workloads that vSphere Foundation, or even a third-party alternative, could absorb without operational compromise.

The work

Twenty weeks. Five workstreams.

1. Workload segmentation

We segmented the 9,200 cores by workload type, regulatory tier and feature dependency. The output: a defensible split between cores that genuinely required VCF, cores that fit vSphere Foundation, and cores that could move to an alternative hypervisor without operational risk.

2. Per-core uplift cap

Negotiated a hard cap on per-core list price for the term, separate from the per-core unit price, removing the renewal uplift risk that the opening proposal would have created in year four.

3. Alternative hypervisor evidence

Built a documented exit path covering two alternative hypervisors, with a partner-validated migration runway and indicative costs. The path did not have to be executed; it had to be credible enough to anchor the negotiation.

4. NSX and vSAN unbundling

For the cores that did not need NSX or vSAN, secured a separate SKU at a defensible unit price rather than the bundled VCF rate.

5. Commercial position

We drafted the position paper. The operator's procurement director presented it. Our team ran the four follow-up sessions across legal, technical and commercial reviews.

Lesson

The Broadcom transition has a default answer: VCF across the estate. That default is rarely the right answer. Workload segmentation moves the conversation from a per-core price debate to a scope debate, and scope is where the leverage lives.

The contract going out

Right-sized VCF, capped uplift, exit path preserved.

The signed contract moved approximately one-third of the estate to VCF against a justified workload model, held one-third on vSphere Foundation at an unbundled SKU, and explicitly named two alternative hypervisors as approved targets for the remainder. Per-core list price was capped for the term.

$18.7M
Saved
Versus the opening Broadcom proposal, measured over the 36-month term.
Capped
Per-core uplift
List-price ceiling held for the term, independent of unit-price negotiation.
2
Exit paths
Alternative hypervisors documented as approved targets in the master agreement.
“We went in expecting a price negotiation. The advisor turned it into a scope negotiation. That was the difference. The exit-path documentation alone changed the tone of the final two sessions.”
Director of Infrastructure Procurement · Telecom · Anonymised by client request
Related resources

More on Broadcom and VMware strategy.

White paper

Broadcom VMware Relicensing

How to structure a VCF transition when the opening proposal prices the whole estate as a single block.
Vendor practice

Broadcom / VMware Practice

How we advise on the post-acquisition relicensing path, VCF scope and alternative hypervisor leverage.
Service

Renewal Advisory

Independent representation for renewal cycles that determine three to five years of infrastructure spend.
← Back to all case studies

Inside the Broadcom relicensing window?

Tell us the core count, the SnS date and the modernisation roadmap. We will respond within one business day with the lead and the most relevant precedent.

Contact Us →Broadcom practice