Broadcom didn't just change VMware licensing — it rebuilt the support model around it. Production support is bundled inside subscription, the old SnS rate is gone, and three new line items have appeared on renewal proposals that were never there before. This article maps the change end to end, with the uplift patterns we see in real deals and the levers that still produce pushback.
Under pre-acquisition VMware, customers bought a perpetual licence and a separate Support & Subscription Services (SnS) contract priced at a percentage of licence value — typically around 22% annually for Production support. The two were procured separately, renewed separately, and could be cancelled independently if a customer wanted to run unsupported. Broadcom removed that decoupling entirely. Subscription bundles include Production support by default; there is no separate SnS to renew, and no option to drop support while keeping the subscription.
Across our renewal book, the all-in cost increase from "perpetual + SnS" to "VVF or VCF subscription" runs between 35% and 220%, depending heavily on which bundle the customer ends up in and how their previous footprint maps. The median we see is around 70% all-in over the first three-year term, compared to maintaining the prior perpetual estate under SnS. A meaningful share of customers see lower per-year cost but on much shorter terms than they previously paid for.
The first place support cost compounds is bundle inflation. A customer who previously bought vSphere Standard + SnS now needs VVF (which costs more than vSphere Standard + SnS). A customer who previously bought vSphere Enterprise Plus + vSAN Advanced now needs either VVF + add-on vSAN or VCF. The subscription support cost is bundled, but the SKU shift is what drives the headline number.
Broadcom's discount structure is heavily weighted toward longer terms. A 1-year subscription is typically 40–60% more expensive per year than a 3-year subscription, which is in turn 8–18% more expensive per year than a 5-year subscription. The headline support cost depends almost entirely on which term length customers commit to, and the term decision is often made under time pressure with insufficient analysis.
That number is negotiable. The question is what data and term structure produces the lower outcome.
VVF and VCF subscriptions include Production support by default. Customers needing higher service levels — Mission Critical support, dedicated TAM (Technical Account Manager), faster SLAs — pay incremental amounts on top. Mission Critical support add-on typically runs 20–35% on top of the subscription base price. Customers who previously had Mission Critical SnS on perpetual are not informed at renewal that Mission Critical is no longer the default; it has to be priced in separately.
Broadcom has progressively closed the option to continue paying SnS on perpetual licences. Customers whose SnS renewals fell after October 2024 in most regions were not offered a renewal; existing SnS contracts continue until expiry but cannot be extended. The binary choice at SnS expiry is convert to subscription or run unsupported. Some customers are choosing to run unsupported on stable estates and self-insure the risk; this is a defensible commercial choice but requires explicit board-level sign-off on the operational risk profile.
Under pre-acquisition VMware, renewal price-protection clauses (typically CPI-capped uplifts) were common in enterprise agreements. Broadcom's standard subscription paper does not include price-protection language by default. The first renewal of a Broadcom subscription is therefore exposed to whatever the price book looks like at that time — with no contractual ceiling. This is one of the most consequential drafting differences between pre- and post-acquisition agreements, and one of the most overlooked.
Five levers consistently move the support uplift number downward in our experience. First, term length: committing to 5 years compresses per-year cost meaningfully where the deployment is stable. Second, bundle right-sizing: VVF instead of VCF where consumption supports it. Third, core consolidation pre-renewal: fewer cores under licence means less subscription. Fourth, ramp structures: lower Year 1 commitment scaling to higher Year 3 commitment, particularly where growth is uncertain. Fifth, price-protection language: re-introducing a CPI-capped uplift on renewal, which Broadcom will accept when raised correctly even though it is not standard.
Includes the full support-cost decoder, term-length sensitivity tables, and renewal scripts.
Three arguments consistently fail to move support cost. First, citing prior SnS rates as a benchmark — Broadcom does not commercially recognise the old book and references to it waste meeting time. Second, escalating to Broadcom executive levels on commercial terms — the commercial model is centralised and disciplined, and executive escalation rarely produces additional discount. Third, threatening to drop to Basic or self-service support — the lower tier doesn't exist as a meaningful alternative in the new model.
Customers who previously had a Technical Account Manager under Mission Critical SnS should specifically ask about TAM continuity at renewal. Broadcom has not preserved TAM coverage uniformly across the customer base; some named-account customers retain a TAM, many do not. The TAM is one of the few support deliverables that is meaningfully different across tiers, and it is worth specifically pricing in the renewal proposal.
Treat support cost as a derived number, not a primary one. The primary numbers are bundle, term, core count, and price-protection language. Support cost falls out of those decisions. Customers who walk into a renewal trying to negotiate "support uplift" as a line item rarely move the number; customers who walk in with bundle alternatives, consolidation plans, and term flexibility move the all-in number by 25–40% routinely.
Our VMware practice is led by former VMware and Broadcom commercial veterans. We work for buyers only.
Weekly compliance intelligence for IT leaders.
