A Broadcom renewal at two to five times the prior bill is a negotiation, not a fait accompli. The Admodum read on how a credible, costed alternative is the only real leverage, when to migrate versus negotiate, and how to sequence the decision into a planned outcome rather than a forced signature.
An exit and renegotiation strategy is the framework for deciding what to do when a Broadcom VMware renewal arrives several times higher than the prior bill. It is not a single choice between staying and leaving; it is a structured decision about which workloads to keep on VMware, which to move, which to run unsupported for a defined window, and how to use all of that to negotiate the part that remains. Admodum is an independent, buyer-side software licensing advisory, and this pillar sets out that decision in full for procurement and infrastructure leaders facing a Broadcom renewal.
The strategy exists because the renewal is usually framed by the vendor as binary: subscribe now at the quoted figure, or lose VMware. That framing is false, and accepting it forfeits the buyer's strongest position. An organisation owns its existing perpetual licences and can keep running them; it can move workloads to other platforms; and it can negotiate the subscription on the part it chooses to keep. The pricing model that produces the increase is set out in the companion pillar, Broadcom VMware licensing: VCF, VVF and per-core subscription, and the cluster index sits at the Broadcom and VMware hub. This page is about what to do once that model has hit the renewal desk.
The distinction worth holding from the outset is between price and structure. Some of the increase is negotiable discount; much of it is structural, driven by the move to subscription, the per-core minimum and bundle consolidation. A sound strategy attacks both: it corrects the structural drivers where the estate allows, and it brings genuine leverage to the negotiable remainder. Treating the whole increase as a discount problem leaves the structural drivers untouched, which is where most of the cost actually sits.
It is worth naming who the strategy is for. The decision sits jointly with procurement, which owns the commercial relationship, and infrastructure, which owns the technical estate and the migration risk. A strategy built by procurement without infrastructure underestimates migration effort; one built by infrastructure without procurement underestimates the negotiating room. The strongest outcomes come from a single team that holds both the technical inventory and the commercial mandate, supported where useful by independent advice that has seen the same renewal play out across many organisations. That cross-functional ownership is itself a precondition for the credibility the rest of the strategy depends on.
In any software renegotiation, leverage is the buyer's credible ability to walk away. With Broadcom, that ability is unusually concrete, because the alternatives to VMware are mature and the buyer owns perpetual licences that keep running. The single largest source of leverage in a Broadcom renewal is a costed, documented migration plan the organisation is genuinely able to execute.
The word that matters is credible. A vendor account team has seen every form of bluff. An abstract threat to leave, unaccompanied by a target platform, a migration cost, a timeline and an internal sponsor, moves nothing. What moves the discount is evidence: a named alternative platform, a costed migration, a pilot already running, a board paper that contemplates the spend. The difference between those two postures is the difference between a renewal that improves and one that does not.
This is why exit and renegotiation are one subject rather than two. The buyer who builds a real alternative is also the buyer who negotiates the best subscription, because the alternative is what gives the negotiation force. Even an organisation that fully intends to stay on VMware should build the alternative far enough to be credible, because that work pays for itself in the renewal regardless of whether the migration is ever executed. The negotiation mechanics that convert this leverage into a number are set out at the VMware renewal negotiation playbook.
There is a second dimension to leverage that buyers often overlook: timing. A vendor's appetite to discount is not constant through its financial year, and a renewal that can be timed to a quarter-end or year-end when the account team is under quota pressure tends to attract a better offer. A buyer who has started early, as the playbook urges, retains the freedom to choose that timing; a buyer negotiating against an imminent expiry has surrendered it. Leverage is therefore a combination of a credible alternative and the freedom to walk away from a particular date — both of which are built in preparation rather than found at the table.
The most common error in a Broadcom renewal is to treat the renewal date as the deadline. It is not. The real deadline is the expiry of the existing Support and Subscription contract — the point at which the estate stops receiving patches and support — not the loss of the right to run the software.
A perpetual licence bought before Broadcom withdrew perpetual sales confers a permanent right to run the software, and that right does not expire. What lapses is Support and Subscription (SnS), the annual maintenance that delivered updates and technical support. Once SnS ends it cannot be renewed standalone, so the estate keeps running but unpatched. The full licence-side change is set out at the end of VMware perpetual licences, and the support change at VMware support, SnS and the named-account model.
Reading the timeline correctly transforms the negotiating position. The buyer is not choosing between signing today and losing VMware tomorrow; the buyer is choosing how long it is willing to run unsupported while it builds an alternative or negotiates better terms. For an isolated, stable workload, running unsupported for a defined window is a deliberate and defensible bridge. For an internet-facing or compliance-bound estate, the unsupported window is short and the security exposure real, which tightens the timeline but does not eliminate the option. Either way, the decision is planned against SnS expiry, not surrendered to a renewal date the vendor sets.
The timeline also has a legal edge that should be understood before any unsupported period begins. Running a perpetual licence beyond its SnS term is lawful for the entitlement owned, but it is not a licence to expand usage: deploying additional instances, adding cores or enabling features beyond the original entitlement is use the organisation has not paid for, and the heightened compliance scrutiny under Broadcom makes that a live risk. The unsupported bridge is a way to hold a known position, not to grow into an unlicensed one, and the inventory that governs the timeline must therefore be exact rather than approximate.
A VMware estate is rarely uniform, and treating it as a single block to be renewed or migrated wholesale forfeits both cost savings and leverage. The estate should be segmented by workload so each portion takes the route that suits it.
A typical segmentation produces three groups. The first is workloads that genuinely depend on VMware-specific capability — features such as vMotion (live migration of a running virtual machine between hosts with no downtime), mature distributed storage, or a hardened operational tooling chain — where the cost and risk of moving outweigh the subscription. These subscribe. The second is workloads that are platform-agnostic — standard virtual machines with no special dependency — which are the natural candidates to migrate to an alternative and which carry the lowest migration risk. The third is workloads with a known end date or low risk profile, which can run on existing perpetual licences for a defined window while replacements are built.
Segmenting this way does two things at once. It lowers the subscription footprint that must actually be renewed, attacking the cost structurally rather than only through discount. And it strengthens the negotiation, because it demonstrates to the vendor that the buyer has measured, costed alternatives at the workload level rather than an abstract threat to leave. A segmented estate is itself evidence of a credible exit. The cost modelling that supports the segmentation sits at building the VMware exit business case.
The segmentation is driven by dependency mapping rather than by gut feel. The practical work is to inventory each application, record which VMware-specific features it actually relies on, and rate the cost and risk of moving it. Most estates discover that the proportion genuinely locked to VMware is smaller than assumed: a large share of workloads are standard virtual machines that any modern hypervisor can host. Surfacing that share is often the single most persuasive piece of evidence in the renewal, because it converts an abstract claim that the buyer could leave into a concrete count of workloads that would move first, second and third.
For the portion of the estate that stays on VMware, the task is to negotiate the subscription down from the quoted figure. This is a structured process, not a single conversation, and it begins long before any discount is discussed.
The first move is to correct the quote itself. A verified core count removes cores that should not be billed; a bundle matched to actual usage removes products the estate does not run; the term and any co-termination or true-forward clauses are read for traps before the discount is even raised. Only once the list quantum is correct does the discount percentage become meaningful, because a large discount on an inflated list is worse than a modest discount on a correct one. The line-by-line method is set out at how to read a Broadcom VMware renewal quote.
The negotiation then runs on the leverage built elsewhere: the segmented estate, the costed migration, the willingness to run a portion unsupported. The choreography — who is approached, in what order, with what concessions held in reserve and what deadlines respected — is the subject of the VMware renewal negotiation playbook. The point for the strategy is that renegotiation is not an alternative to exit; it is the route that the exit work makes succeed.
A renegotiation also has to look beyond the headline discount to the terms that determine cost over the full period. A discount that looks generous can be eroded by a term that locks an inflated core count, by a co-termination clause that removes future flexibility, or by price-protection language that caps year-on-year increases only loosely. The renegotiation therefore secures three things at once: the corrected quantum, the discount against it, and the contractual terms that prevent the negotiated price from drifting upward through the term. Treating price and terms as a single package, rather than conceding terms to win a headline number, is what makes a renegotiated outcome hold.
For the portion of the estate that moves, the question is where to. The alternatives to VMware are mature, and each carries a distinct cost, operational model and feature trade-off, so the right answer is usually a mix matched to workload rather than a single replacement.
The principal targets are Nutanix, which offers an integrated hyperconverged platform closest to VMware's operational model; Microsoft Hyper-V, attractive where the organisation already runs Windows Server and System Center; open-source Proxmox, which removes licensing cost entirely at the price of a different support and operational model; and re-platforming workloads to a public cloud, which suits applications already moving toward cloud-native architectures. Each is examined, with its migration cost and trade-offs, at VMware alternatives: Nutanix, Hyper-V, Proxmox and cloud.
A full migration off VMware typically takes twelve to thirty-six months depending on estate size, application dependencies and the target platform — longer than a single renewal cycle. That timeline shapes the strategy: the credible position at the next renewal is rarely a completed migration but a migration in progress or fully planned and costed, with existing perpetual licences bridging the workloads not yet moved. The migration does not have to finish to deliver leverage; it has to be real and underway.
The choice of target is rarely uniform across the estate. A compute-heavy tier of standard virtual machines may move cleanly to Nutanix or Proxmox; a Windows-centric tier may be cheapest to land on Hyper-V where Software Assurance is already held; a tier of applications already being modernised may be re-platformed to public cloud as part of work that was happening anyway. Matching each tier to the target that fits it, rather than forcing the whole estate onto one platform, lowers both migration cost and operational disruption. The trade-offs that drive those matches — operational maturity, storage model, support arrangements and exit cost from the new platform — are exactly what the alternatives sub-page sets out to compare.
A migration is also de-risked by proving it before committing to it. A pilot that moves a representative slice of the estate to the chosen target validates the migration tooling, exposes the real labour cost per workload, and surfaces the dependencies that desk research misses. It also converts the alternative from a proposal into demonstrated capability, which is the most credible form of leverage a buyer can bring to a renewal: not a claim that the organisation could move, but evidence that it already has. The pilot need not be large; it needs to be real enough that the migration cost in the business case is measured rather than estimated, and that the vendor understands the buyer can execute what it describes.
Every route — renegotiate, migrate, bridge on perpetual — has a cost, and the decision has to be made on a like-for-like comparison of those costs rather than on the headline of the renewal quote. Building that comparison is the business case, and it is the artefact that converts a strategy into a board decision.
The business case sets the multi-year subscription cost against the one-off migration cost plus the lower ongoing cost of the alternative, and against the cost and risk of running unsupported. It accounts for the things that do not appear on the renewal quote: migration labour, retraining, parallel running during transition, the value of escaping a vendor whose pricing has proven volatile, and the risk premium of an unsupported window. A migration that looks expensive against a single year's subscription often looks decisively cheaper across a three-to-five-year horizon, which is why the comparison must be multi-year. The full method, including the cost lines that are routinely missed, sits at building the VMware exit business case.
The business case also disciplines the negotiation. A buyer who knows precisely what migration costs knows precisely how much subscription premium it is willing to pay to avoid it, and therefore knows when to accept Broadcom's offer and when to walk. Without the business case, the buyer negotiates blind; with it, every concession can be tested against a number.
The business case is also where the soft costs that decide real outcomes are forced into the open. Migration carries risk, disruption and a learning curve that a spreadsheet of licence fees ignores, and a subscription carries the less visible cost of dependence on a vendor whose pricing has proven volatile. A rigorous case prices both: it applies a risk premium to the migration and a volatility premium to the subscription, so the comparison reflects not only this year's numbers but the exposure each route carries forward. A case built this way survives challenge from a finance committee precisely because it has already accounted for the objections that committee will raise.
A period of change is the period of greatest compliance exposure, and Broadcom's acquisition of VMware has been accompanied by increased attention to licence compliance. An exit or renegotiation strategy has to account for the audit risk that the transition itself creates.
The exposures are specific. A buyer running existing perpetual licences must be sure it is running only what it owns, because the move to subscription has sharpened scrutiny of perpetual entitlements. A buyer mid-migration may briefly run workloads on both VMware and the new platform, and that parallel running must be licensed correctly on both sides. A buyer that has let SnS lapse must understand the difference between the lawful right to run perpetual licences unsupported and any use beyond the entitlement, which is not lawful. The full exposure map and the defensive posture are set out at VMware audit and compliance under Broadcom, and the wider audit-defence engagement at the Audit Defence programme.
The defensive discipline is the same one that underpins the whole strategy: a verified inventory. An organisation that knows exactly what it owns, what it runs and where, can defend an audit, license a migration correctly, and negotiate from fact. The inventory is not merely a compliance artefact; it is the foundation of every part of the exit and renegotiation decision.
There is a tactical point here that buyers should hold in mind. An audit or a compliance enquiry that arrives in the middle of a renewal negotiation is not a coincidence to be panicked by; it is a pressure that a verified inventory neutralises. An organisation that can demonstrate, from its own records, exactly what it owns and runs removes the uncertainty an audit is designed to exploit, and keeps the commercial negotiation on the footing it has prepared. The defensive posture and the negotiating posture are therefore the same work: both rest on knowing the estate precisely enough that no party can introduce doubt the buyer cannot immediately answer.
The contract mechanics that sit beneath a Broadcom subscription can quietly undo a well-negotiated price, and an exit strategy has to read them before signing. The two that most often surprise buyers are co-termination and true-forward.
Co-termination aligns the end dates of multiple subscriptions to a single renewal date. It simplifies administration but concentrates the buyer's entire VMware spend into one renewal event, which removes the ability to renegotiate pieces independently and hands the vendor a single high-leverage moment. True-forward is the mechanism by which capacity added during a term is charged — typically at the next renewal rather than immediately, which sounds benign but means mid-term growth accumulates into a step change at renewal that the buyer may not have modelled. Both mechanics are set out in full, with the clauses to watch and the language to negotiate, at VMware co-term and true-forward mechanics.
For the strategy, the lesson is that the negotiated price is only as good as the contract that carries it. A favourable discount attached to a co-termination clause that removes future flexibility, or a true-forward clause that prices growth punitively, can cost more over the term than a higher headline discount on cleaner terms. The contract is read as carefully as the quote.
The strategy comes together as a sequence, and the order matters because each step depends on the one before it. Done in the right order, a renewal that arrived as a forced signature becomes a planned, evidenced decision.
The sequence begins with the inventory: a verified record of perpetual entitlements, SnS expiry dates, and physical cores per host. From the inventory comes the segmentation: which workloads stay, move, or bridge. From the segmentation comes the business case: the multi-year cost of each route. From the business case comes the leverage: a costed, credible alternative. And from the leverage comes the negotiation, conducted against a corrected quote and a clean contract. At every step the SnS expiry date governs the timeline, ensuring the decision is made on evidence rather than under pressure.
The sequence is also resilient to changing circumstances, which matters because the decision rarely resolves in a single pass. A migration that looked marginal in one year's business case can become compelling if Broadcom raises prices again, and a subscription accepted this cycle does not foreclose an exit at the next. Because the inventory and segmentation are reusable assets, an organisation that builds them once can re-run the comparison cheaply at each renewal rather than starting from scratch. The strategy is therefore not a one-off project but a standing capability: the buyer that maintains a verified inventory and a costed alternative holds durable leverage over every future renewal, not merely the one in front of it.
One caution is worth stating plainly. None of this rests on manipulation or brinkmanship; it rests on facts the organisation can stand behind. The alternative must be genuinely executable, the inventory genuinely accurate, the business case genuinely defensible. A strategy built on a bluff collapses the moment it is tested, and tends to leave the buyer worse off than an honest negotiation would have. The reason the approach works is precisely that it is real — and that is also why it survives scrutiny from a board, an auditor or a vendor alike.
The work is substantial, but it is the work that converts a two-to-five-times increase into a managed cost. The wider engagement sits at the Broadcom / VMware practice, the aggregated reading at the Broadcom knowledge hub and the cluster index at the Broadcom and VMware hub; a renewal moment routes to the Renewal Programme and engagement opens at contact. The detailed routes — the playbook, the alternatives, the business case, the audit posture and the contract mechanics — are the five sub-pages below.
For most organisations the question is not exit versus renegotiate but how to use a credible exit to improve the renewal. A costed, documented migration plan is the single largest source of leverage in a Broadcom negotiation, so the two routes are pursued together: the alternative is built far enough to be real, and that reality is what makes the renegotiation succeed or the exit worthwhile.
The only durable leverage is a credible alternative the buyer is genuinely able to execute. A verified core count and a right-sized bundle correct the quote, but the willingness and ability to migrate part or all of the estate is what moves the discount. Leverage comes from a costed migration plan, not from expressing dissatisfaction.
No. The estate rarely needs to move as a single block. A portion can migrate to an alternative platform, a portion can subscribe where the workload genuinely depends on VMware-specific features, and a portion can run on existing perpetual licences while its replacement is built. Segmenting the estate lowers the subscription footprint and strengthens the negotiation.
The real deadline is the expiry of the existing Support and Subscription contract, not the loss of the right to run. A perpetual licence keeps running after SnS lapses; it simply stops receiving patches and support. Reading the timeline against SnS expiry rather than the renewal date converts a decision under pressure into a planned one.
A full migration off VMware typically takes twelve to thirty-six months depending on estate size, application dependencies and the target platform. Because that exceeds a single renewal cycle, the credible position at the next renewal is a migration in progress or fully planned and costed, with existing perpetual licences bridging the workloads not yet moved.
The principal alternatives are Nutanix, Microsoft Hyper-V, open-source Proxmox, and re-platforming workloads to a public cloud. Each carries a different migration cost, operational model and feature trade-off, so the right answer is usually a mix matched to workload rather than a single replacement for the whole estate.
The Admodum white paper on the Broadcom VMware exit architecture sets out the leverage equation, the migration routes and the business case in full. A senior advisor will read your estate, SnS expiry dates and renewal quote against it on a private call.
Renewal approaching? Join the newsletter or route the moment to the Renewal Programme.