Every VMware renewal is now a forced migration. Broadcom ended new perpetual licensing in December 2023, so when your support contract runs out, there is nothing to renew onto except subscription bundles, priced per core, sold in packages that include products you may never use. The organizations paying multiples of their old bill are not the ones with the biggest estates. They are the ones who treated the renewal as a rollover and started thinking after the quote arrived.
What actually changed under Broadcom?
Three structural changes, all announced within months of the acquisition closing.
Perpetual licensing ended. Broadcom announced the end of availability of perpetual VMware licenses and support-and-subscription renewals in December 2023. Existing perpetual licenses continue to function, but they can no longer be bought, and expiring support contracts convert the relationship to subscription at renewal.
The catalog collapsed into bundles. A sprawling catalog became two primary offers, in Broadcom’s own framing: VMware Cloud Foundation (VCF), the flagship full private-cloud stack, and VMware vSphere Foundation (VVF), which pairs vSphere with operations management for traditional environments. You no longer buy the piece you use. You buy the bundle it lives in.
Pricing moved to per-core subscription. Licensing is priced per CPU core across your estate, with a 16-core minimum per processor. In 2025, a 72-core minimum purchase requirement surfaced through partner channels and was walked back within weeks after industry backlash, which tells you two things: the direction of travel, and the fact that pressure works.
The compounding effect is what surprises CFOs. Industry analyses have documented smaller environments seeing three to five times their previous costs once subscription pricing, per-core counting, and mandatory bundling stack together. Your exact multiple depends on how your estate was licensed before, and on how much of it is priced without being optimized first.
What are your five options at renewal?
| Option | Time needed | What it buys |
|---|---|---|
| Renew consolidated, negotiated | 3 to 6 months | Best available terms on the estate you keep |
| Shrink before you price | 3 to 6 months | Removes cores and bundles you should not pay for |
| Run perpetual on self or independent support | Immediate | Buys migration time, at a security and compliance cost |
| Segment and partially migrate | 6 to 18 months | Smaller VMware bill plus real negotiating credibility |
| Full migration | 12 months or more | Exit, at real cost and risk, rarely the fast answer |
These are not mutually exclusive. The strongest renewal positions we see combine shrinking the estate before it is priced with a credible alternative for the workloads that could leave.
The bridge option deserves its own honest paragraph, and this guide gained it on August 10, 2026, after practitioners rightly raised it. If you own perpetual licenses, they keep working when support lapses. Some organizations run them on self support, or on independent third-party support, as a bridge that buys a longer migration runway than a renewal deadline allows. The trade-offs are exactly as real as the benefit: no vendor patches or updates beyond emergency security fixes, a security and compliance posture that needs active management rather than a support contract, and Broadcom has shown it watches support entitlements closely. As a bridge to a planned destination, it can buy years. As a destination in itself, it is a risk position, not a strategy.
Renewing as-is without negotiation is the option nobody should pick, and it is the default outcome of starting late. The bundle level, the core count, the term length, and the price protection through the term are all negotiable, but only for customers who arrive with their own numbers before the quote hardens.
What drives the size of your quote?
Cores, bundle level, and term. Every one of them rewards preparation.
Cores. The quote is built on your total licensed core count. Clusters sized years ago, hosts with high-core processors running light workloads, environments kept for convenience: all of it gets priced. Right-sizing before renewal, consolidating workloads onto fewer, appropriately sized hosts, is the single most direct lever on the number.
Bundle level. VCF carries the full stack. If your estate is traditional vSphere with no meaningful use of the broader components, the difference between VCF and VVF pricing across every core is a negotiation in itself, and the mapping between what you use and what you are quoted deserves the same scrutiny as the core count.
Term. Broadcom’s commercial model wants long, consolidated commitments. That is your trade, not your concession. Multi-year term in exchange for locked pricing, protection against mid-term changes, and flexibility on estate reduction is a deal. Multi-year term at list because the quote assumed it is a donation.
Does the migration threat actually work?
Only if it is real. Vendors price the probability that you stay, and a renewal conversation where leaving is obviously impossible is a conversation about how much more you will pay.
That is why segmentation matters more than bravado. A documented assessment showing which workloads genuinely depend on VMware and which could run on alternatives, with real timelines and costs attached, changes the negotiation even if you never execute it, because it converts “we could leave” from a bluff into a plan. And if the renewal economics stay hostile, the plan is already on the shelf.
Full migration is the right answer for some estates, and VMware Broadcom migration work is a named UMS practice for exactly that path. But it is a program, not a threat, and pretending a twelve-month program can happen before a ninety-day renewal deadline convinces nobody.
Where UMS fits
We negotiate against software vendors for a living, and we spent years on the other side of the table learning how these quotes get built. On a VMware renewal, we rebuild your position from the estate up: actual core counts, actual component usage, the right bundle mapping, the segmentation case, and then the negotiation itself, run from evidence instead of hope.
We are paid only from the savings we find. No savings, no fee. If your VMware renewal lands in the next 12 months, give us 30 minutes before the quote defines the conversation.
Frequently asked questions
Can I still buy or renew perpetual VMware licenses? No. Broadcom announced the end of availability of perpetual VMware licensing in December 2023. New sales are subscription only, primarily VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF). Existing perpetual licenses keep working, but when your support contract ends, the renewal conversation becomes a transition onto subscription.
What happens at my VMware renewal now? Your renewal is a repricing event, not a rollover. Your existing licenses and support map onto new subscription bundles, priced per core with a 16-core minimum per CPU, and the bundles include components you may not use. That is why quotes arriving at renewal are often multiples of the old support bill.
Why did my VMware quote go up so much? Three drivers stack: the move from support renewal pricing to full subscription pricing, per-core licensing across your estate, and mandatory bundling that includes products you may never deploy. Industry analyses have documented small environments seeing three to five times their previous cost, and the increase compounds if your core counts were never optimized.
Can we keep running our perpetual VMware licenses without a Broadcom subscription? Often, yes. Perpetual licenses you already own keep working after support lapses, and some organizations run them on self support or independent third-party support to buy migration time. The trade-offs are real: no vendor patches or updates beyond emergency security fixes, a security and compliance position that needs active management, and Broadcom has shown it watches support entitlements closely. Treat it as a bridge with a destination, not a permanent answer.
Is migrating off VMware a realistic option? For part of your estate, often yes. For all of it, rarely quickly. Full migrations of complex estates typically take a year or more and carry their own cost and risk. The practical play for most enterprises is segmentation: identify workloads that genuinely need VMware, move commodity workloads where alternatives are credible, and let that credible option discipline the renewal price on what remains.
What leverage do VMware customers actually have? Term length, estate size, and credibility. Broadcom’s model wants large, long, consolidated commitments, so multi-year term and consolidation are things you can trade for price protection and flexibility rather than give away. And a documented, credible migration plan for part of your estate changes the tone of the negotiation even if you never execute it.
When should we start preparing for a VMware renewal? At least six months before the date, and earlier for large estates. You need time to inventory actual core counts and usage, right-size clusters before they are priced, evaluate alternatives seriously enough to be credible, and run the negotiation without a deadline at your back. Preparation started after the quote arrives is triage, not strategy.
Source notes
- VMware End of Availability of Perpetual Licensing (VMware/Broadcom): the December 2023 end of perpetual licensing and the transition path for existing customers, in the vendor’s own words.
- VMware by Broadcom Simplifies Offer Lineup and Licensing Model (Broadcom): the consolidation of the catalog into VCF and VVF subscription offers.
- VMware Licensing Changes: The 72-Core Reversal and Migration Paths (StarWind): third-party analysis of the 2025 72-core minimum episode, the 16-core per-CPU minimum, and the three to five times cost increases observed in smaller environments.
- VMware Walks Back 72-Core Licensing Change After Backlash (Licenseware): corroborating account of the partner-channel 72-core requirement, its retraction, and the retained 16-core minimum.
- UMS VMware Broadcom migration: the UMS practice page for VMware estate assessment, segmentation, and migration.