VMware Subscription Conversion: Pricing Guide

The conversion from perpetual VMware to Broadcom subscription is the largest single licensing decision most enterprises will make this decade. The arithmetic is unfamiliar — it moves the customer from a known per-CPU position to a per-core position at a negotiated conversion ratio, applies subscription pricing, and locks the result in for three-to-five years. The variables interact in non-obvious ways and the final price can range across a factor of three depending on how the negotiation is conducted.

This guide is the pricing explainer. It covers how the conversion arithmetic actually works, what list pricing looks like in practice, what discount ranges are achievable, and what realistic conversion outcomes look like in 2026.

The three variables that determine conversion cost

Conversion economics turn on three variables, in descending order of magnitude.

The per-CPU to per-core conversion ratio

The single largest determinant of conversion cost. Per-CPU entitlements convert to per-core entitlements at a published ratio. Early conversions used eight cores per CPU; later conversions moved to sixteen cores per CPU. Negotiated outcomes in the field have ranged across the published range, with well-prepared customers securing ratios closer to the more favourable end.

The arithmetic effect is large. A customer with one thousand per-CPU entitlements converting at sixteen cores per CPU is acquiring sixteen thousand per-core entitlements. The same customer converting at eight cores per CPU is acquiring eight thousand per-core entitlements. At any given per-core price, this is a two-times difference in subscription cost. The conversion ratio is the variable to negotiate hardest.

The per-core discount against list

The second-largest variable. Published list pricing for VVF and VCF per core is well in excess of what most customers actually pay. Discount ranges in our engagement data:

• Small deployments (under 500 cores): typical discounts of 10-20% against list
• Mid-size deployments (500-3,000 cores): typical discounts of 20-35% against list
• Large deployments (3,000-10,000 cores): typical discounts of 30-50% against list
• Strategic deployments (10,000+ cores or named-account status): typical discounts of 40-60% against list, occasionally higher

Discount levels are negotiated and depend on deal size, term length, the credibility of the customer's migration alternatives, the timing of the deal relative to Broadcom's fiscal-year-end (last week of October), and the strategic value of the customer to Broadcom.

The renewal-time uplift cap

The third variable matters at the next renewal but is negotiated in this one. Without an explicit uplift cap, the renewal-time price is set by Broadcom at the renewal moment, with little customer constraint. Customers who have negotiated explicit annual uplift caps — typically in the 5-10% per year range, with a multi-year cumulative cap — protect themselves from open-ended renewal-time pricing. The value of this protection compounds over the second term and is among the most consequential contractual provisions.

How the arithmetic works: a worked example

Consider a mid-size customer with 200 dual-socket servers, each with two 16-core CPUs. The customer has 400 per-CPU perpetual entitlements on vSphere Enterprise Plus with active SnS.

Per-core entitlement after conversion

At a 16-cores-per-CPU conversion ratio: 400 CPUs × 16 cores = 6,400 cores entitled.

At an 8-cores-per-CPU conversion ratio: 400 CPUs × 8 cores = 3,200 cores entitled.

The actual physical core count of the estate is 400 CPUs × 16 cores = 6,400 cores. At the 16-cores-per-CPU ratio, the conversion matches the deployment. At the 8-cores-per-CPU ratio, the customer would acquire enough cores to cover half the deployment — requiring an additional purchase of 3,200 cores to cover the full estate.

Subscription cost under VVF

Assuming a list per-core price of $135 per core per year for VVF (the publicly cited list range, which has moved in catalogue revisions). Under a 30% discount: $94.50 per core per year. Across 6,400 cores: $604,800 per year, or $1,814,400 across a three-year subscription.

For comparison, the pre-acquisition annual SnS on 400 per-CPU vSphere Enterprise Plus entitlements at a typical SnS rate of $1,200 per CPU per year would have been approximately $480,000 per year. The conversion produces an increase of roughly 26% per year for this customer on VVF — meaningful but not extreme. Under VCF the equivalent calculation produces a larger increase, typically two to three times the SnS baseline.

The sensitivity to the conversion ratio

If the customer negotiates the conversion ratio down to 12 cores per CPU instead of 16, the entitled core count drops to 4,800 cores. At the same per-core price the annual cost drops to $453,600 per year — below the pre-acquisition SnS rate. This is the financial leverage of the conversion ratio negotiation.

If the customer instead accepts a 16-cores-per-CPU conversion with no discount negotiation (list at $135 per core per year), the cost rises to $864,000 per year — an 80% increase over the SnS baseline. The variance between worst-case and best-case is large.

List pricing as published, in practice

Broadcom does not publish official list pricing for VCF and VVF; the published-list figures cited in the market are derived from customer-shared proposals, partner discussions, and analyst publications. The figures most commonly cited in 2026 fall in the following ranges:

• VVF: $130-160 per core per year, varying by edition and term length
• VCF Standard: $200-260 per core per year
• VCF Advanced: $260-320 per core per year
• VCF Enterprise: $320-400 per core per year

These ranges are estimates and are subject to catalogue revisions and regional variation. Specific customer proposals routinely arrive at different headline numbers, which is part of why the negotiation is consequential. The published ranges are best treated as a baseline against which the negotiated outcome can be measured, not as the price a customer should expect to pay.

Negotiating levers that move conversion cost

Five levers, beyond the three core variables above, materially affect conversion outcomes.

Timing

Broadcom's fiscal year ends in late October. The final two months of the fiscal year are the period of maximum negotiating leverage for customers, particularly on larger deals where the Broadcom sales organisation has quota incentives to close. Deals signed in November typically see different pricing than identical deals signed in March.

Term length

Five-year terms attract larger headline discounts than three-year terms, typically by five-to-ten percentage points. Customers confident about VMware direction can capture the longer-term discount; customers uncertain should preserve flexibility at the cost of the discount.

Deal size and consolidation

Larger deals attract larger discounts. Customers with multiple business units or geographies should consider consolidating purchases into a single deal to access size-based discounting, rather than fragmenting purchases.

Migration alternative credibility

Customers with a credible, costed migration alternative — not necessarily an alternative they intend to execute, but one that is sufficiently developed to be commercially credible — consistently land better conversion economics than customers without one. The cost of building a credible alternative analysis is small relative to the negotiation value it generates.

Edition selection

VCF Standard is meaningfully cheaper than VCF Advanced, which is meaningfully cheaper than VCF Enterprise. Customers should negotiate at the edition that matches their deployment, not the edition Broadcom defaults to in initial proposals.

What the contract should include

Beyond pricing, the contractual provisions that matter most in a conversion deal:

Explicit conversion ratio language

The ratio used should be stated in the contract, not left to interpretation against published policy. Customers who do not specify see surprises in subsequent true-up calculations.

Annual uplift cap with a cumulative cap

The renewal-time pricing should be capped at a defined annual percentage with a multi-year cumulative cap. Without this, the second term is open-ended.

Audit-rights clarification

The conversion contract is a good moment to clarify audit-rights language — what data Broadcom can request, on what notice, with what dispute mechanism. The clarification is generally easier to secure inside a substantial commercial transaction than outside one.

Divestiture provisions

For customers expecting divestiture or substantial scope reduction inside the term, contractual provisions for reducing the committed core count are valuable. These provisions are typically not in the initial template and have to be negotiated in.

What to do before signing

Three actions are appropriate before signing any conversion deal of meaningful size.

First, reconstruct the entitlement position. The conversion arithmetic depends on the perpetual entitlement count, which should be verified against contracts and procurement records, not against Broadcom's interpretation.

Second, model alternatives. Run the cost of conversion at the proposed ratio and discount; run it at one ratio better and at one discount level better; run the equivalent cost under the alternative platforms. The comparison frames the negotiation.

Third, secure independent negotiation support. Broadcom's commercial organisation is sophisticated and well-prepared. Customer-side preparation generally is not. The asymmetry is the source of the variance in negotiated outcomes, and it is closeable with the right preparation.

The role of Broadcom's named-partner channel

The Broadcom Advantage Program partner is a meaningful actor in the conversion negotiation, particularly for mid-market deals. The partner's commercial latitude is constrained — they cannot typically improve materially on the directly negotiated Broadcom pricing — but the partner can provide negotiating support, deal-shaping advice, and (for sophisticated partners) real intelligence on what comparable deals are settling at.

The partner's incentives are not perfectly aligned with the customer's. The partner is compensated on deal close and has limited incentive to extend a negotiation in pursuit of better terms; the partner also has an ongoing commercial relationship with Broadcom and cannot push too hard against vendor interests without risking that relationship. The customer should engage the partner with this in mind — useful for some commercial intelligence and contracting support, not a substitute for independent buyer-side advisory.

Customers in larger named-account segments often work directly with Broadcom without partner involvement on the commercial side. The partner may still play an implementation or managed-services role but does not mediate the commercial negotiation. For these customers, the dynamic is direct customer-versus-vendor, with the asymmetry of preparation between Broadcom's commercial team and a typical customer team being the principal negotiation challenge.

The audit-trade in conversion negotiations

A pattern that has emerged across multiple engagements: customers facing an audit finding negotiate the finding settlement as part of a subscription conversion. The audit finding is structured as a credit against the conversion deal, effectively trading future subscription commitment for resolution of the historic compliance position.

The economic mechanics are favourable to both sides. Broadcom secures a multi-year subscription commitment and resolves the audit case. The customer resolves the audit liability at typically more favourable terms than a standalone settlement would have produced, in exchange for a commitment they were likely going to make anyway. The trade is one of the most common ways audit findings are settled under the current model.

The customer-side caution: the trade only works in the customer's favour if the conversion was already commercially desirable on its own terms. Using a subscription conversion as a vehicle to settle an audit finding can produce a strategically unsound commitment if the conversion was not the right answer absent the audit. The audit pressure should not drive the strategic choice; the strategic choice should drive the conversion, and the audit can be settled inside it if favourable terms are achievable.

Multi-product conversion economics

For customers converting multiple legacy entitlements — vSphere Enterprise Plus, standalone vSAN, standalone NSX, vRealize Operations — the conversion arithmetic is more complex than the single-product case. The bundle structure of VCF means that multiple legacy entitlements roll into a single VCF subscription.

The customer-side analysis should compare the conversion economics under three scenarios. First, what does the customer's existing multi-product entitlement set cost at current SnS rates if all SnS contracts are renewed (where renewal is still permitted)? Second, what does the equivalent VCF subscription cost at negotiated pricing? Third, what does VVF plus standalone NSX (where available) plus alternative tooling for the other components cost? The comparison frames the bundle decision.

Multi-product customers also have more leverage in the conversion negotiation than single-product customers. The deal size is larger, the strategic value to Broadcom is higher, and the commercial latitude on conversion ratios and discount levels is wider. Multi-product customers who do not capture this leverage typically pay materially more than necessary.

Related reading

For broader context, see the VMware licensing complete guide, the end of perpetual licensing, Broadcom VMware pricing 2026, and VCF licensing explained.