Italian luxury brand. Twenty five percent saved on Broadcom VMware.

How an Italian luxury group cut its Broadcom VMware subscription migration 25 percent: host consolidation before core counts, bundle tier fit, and an exit scenario the vendor believed.

What was the situation at this Italian luxury brand?

An Italian luxury group running a virtualized estate across retail, logistics, and design workloads faced its first Broadcom era VMware renewal: a subscription migration proposal with a multiple of the prior annual cost. The perpetual estate had active support expiring within two quarters, and the proposal bundled the full software stack across every host.

The board asked a simple question nobody could answer: what do we actually run, and what would leaving cost? The engagement started six months before support expiry.

The starting position

• Contract: perpetual licenses with support lapsing, no subscription terms agreed.
• Estate: mixed density hosts across three data centers, no current core inventory.
• Proposal: top tier bundle, every host, multi year, at a multiple of prior spend.

What did the estate analysis find?

The core inventory found a quarter of hosts idle or consolidation ready, measured feature use mapping to a mid tier bundle rather than the proposed top tier, and a workload subset that could credibly move to an alternative hypervisor. Those three findings became the entire negotiation.

1. Core inventory: sockets, cores, and utilization per host, against the per core terms on Broadcom's VMware product pages.
2. Feature mapping: running components mapped against VMware Cloud Foundation tiers, with support lifecycle checked on the Broadcom support portal.
3. Consolidation model: idle and low utilization hosts retired or merged before any subscription count was accepted.
4. Exit scenario: a priced, dated migration plan for the workload subset where alternatives were viable.

Counting cores before counting money

The inventory ran first because every other number depends on it. Idle hosts found in week three would have been subscribed for five years had the proposal been accepted in week one.

Where the common advice on Broadcom migrations is wrong

The standard advice is that Broadcom does not negotiate, so take the best discount offered and sign the longest term to lock it. We disagree. In roughly 15 of the 20 to 30 Broadcom negotiations Fredrik Filipsson advised in 2024 to 2025, consolidated estates with a credible exit scenario settled 20 to 30 percent below the opening proposal, and shorter terms preserved the leverage for the next cycle. The buyer side move is to shrink the estate first, match the bundle tier to measured use, and let the funded alternative do the talking. Lock in at a discount is still lock in.

The proposal priced the estate as it stood. The negotiation priced the estate as it should have stood. The difference was twenty five percent.

What were the results and what transfers to other estates?

The migration closed roughly 25 percent below the opening proposal, on a mid tier bundle, a consolidated host base, and a shorter term with price protection. The exit scenario was never executed, but it was funded, dated, and visibly real, which is why it worked.

Why the exit scenario worked

It was specific: named workloads, a named platform, a budget line, and a start date. Vendors discount certainty, not threats, and the scenario read as a plan, not a posture. Lifecycle milestones were tracked against Broadcom knowledge base data throughout.

What transfers: consolidate before counting, match the tier to measured features, and fund the alternative scenario even if you intend to stay.

The transferable sequence

• Months 1 to 2: core inventory and feature mapping.
• Months 3 to 4: consolidation execution and exit scenario pricing.
• Months 5 to 6: commercial negotiation and signature before support lapse.

What to do next

1. Build the core inventory: sockets, cores, utilization per host.
2. Map running components to bundle tiers before accepting any proposal tier.
3. Retire or consolidate idle hosts before any core count is agreed.
4. Price one credible exit scenario for the workloads where it is viable.
5. Negotiate the support bridge so coverage never lapses mid negotiation.
6. Prefer shorter terms with price protection over discounted lock in.
7. Start at least six months before support expiry.

The Broadcom VMware practice runs migration negotiations end to end, and the audit defense guide covers the compliance side. More outcomes are in our case studies.

Frequently asked questions

How much did this Broadcom VMware negotiation save?

About 25 percent against the opening subscription migration proposal, on a consolidated host base, a mid tier bundle, and a shorter term with price protection.

What produced the savings?

In order: host consolidation cut the subscription base about a quarter, the bundle tier was matched to measured feature use, and a funded exit scenario established settlement leverage.

Does Broadcom actually negotiate?

Yes, when the estate is consolidated and the alternative is credible. Estates with funded, dated exit scenarios settled 20 to 30 percent below opening proposals in our 2024 to 2025 engagements.

Was the exit scenario ever executed?

No. It was funded, dated, and visibly real, which is what made it work as leverage; execution was never required.

How long did the engagement take?

Six months from start to signature, timed to close before support lapsed: two on inventory, two on consolidation and exit pricing, two on the commercial close.