VMware renewal checklist: how to prep before Broadcom sets your quote

A VMware renewal under Broadcom is a negotiation, and whoever brings the defensible number sets the anchor. The work is to know your real position before the quote arrives — not to react to it. Here is what to verify, and which of these checks RenewalIntel runs for you.

Start before the quote lands

Begin nine to twelve months ahead. Entitlement questions take time to resolve, and the worst time to discover a gap is the week the renewal quote arrives.

The checklist

• Inventory the hosts. Capture every ESXi host, its populated CPUs, and physical cores per socket.
• Apply the 16-core floor. For each socket, license the greater of its physical cores or 16 — and confirm the quote reflects the 16-core rule, not the reversed 72-core figure.
• Map the editions. Determine which clusters belong on VVF versus VCF based on what you actually run, not a default.
• Check vSAN capacity. Compare vSAN consumption per core against the bundled allowance; note any add-on exposure.
• Reconcile against entitlements. Compare required cores to what you are entitled to, per cluster, to find the net position.
• Build the evidence. Tie every number to a host, socket count, and edition so the position holds up under scrutiny.

Negotiate from your number

With a reconciled position in hand, the renewal stops being a reaction. You know whether you are over- or under-licensed, by how much, and exactly why — so you can true up only what is real and push back on what is not.

How RenewalIntel runs the checklist

Each step above is what RenewalIntel does for VMware automatically: it inventories hosts, applies the 16-core floor per socket, maps editions and vSAN consumption, reconciles per cluster and product line, and generates an evidence-backed position with the calculation shown — so the defensible number is ready before the quote is, not assembled under deadline after it arrives.