Staying on VMware After Broadcom: How to Do It Well
Almost all the noise since the Broadcom acquisition has been about leaving VMware. For a large number of estates, staying is the better decision. But staying well is not the same as renewing on autopilot. Here is how to keep VMware well: the right bundle, the new version 9 compliance duty, the support lifecycle, and a renewal you can defend.
The honest starting point is this: leaving VMware is real work, and for many organisations it is the wrong answer. If your estate already uses the broad VMware stack, if your operational tooling and your people are built around it, and if the workloads are stable and business critical, then a well negotiated renewal can be a more rational decision than a migration that consumes a year of engineering effort to escape a number you could have brought down at the table. The question worth asking is not just whether to leave, it is whether you are staying on purpose or staying by inertia. Those are very different positions, and only one of them saves you money.
This guide is the deliberate counterpoint to the exit content. If you are still weighing the bigger decision, start with our honest framework on whether to leave VMware at all and come back here once you have decided to stay. What follows assumes the decision is made: you are keeping VMware, and you want to do it well.
C4C is an independent UK technology consultancy that negotiates VMware and Broadcom renewals on the customer’s side, and we do not resell VMware licences. We take no margin on your renewal, so we have no reason to push you into a bigger bundle or off the platform. We are paid a fixed fee, a share of the saving we achieve, or for professional services such as a licence audit. Staying is often the right call, and a well negotiated renewal routinely beats a migration that burns a year of engineering. We spent years on the vendor side pricing these deals, so we know where the give is. Engage us early, before the renewal clock takes your leverage.
Staying on VMware is often the right decision, if you stay on purpose rather than by inertia. Staying well means four things: run the bundle that matches the features you actually use, treat the version 9 compliance report as an operational duty, keep every host on a supported version, and negotiate each renewal on evidence rather than accepting the first quote. If staying still cannot reach a defensible number after that, a planned exit is the better answer.
When is staying on VMware the right call?
Staying is not a default and it is not a failure of nerve. It is the right call in specific, identifiable situations, and the wrong one in others. Being clear eyed about which camp you are in is the whole game.
Staying tends to be right when
The stack is doing real work for you
You genuinely use the broader platform: vSAN, NSX networking, automation, hybrid or Tanzu. Your operations, runbooks, backup and disaster recovery are deeply integrated with vSphere. The estate is large, stable and business critical, and the migration risk outweighs the licensing saving you could otherwise negotiate. In this case the work is to make the renewal efficient, not to escape it.
Staying tends to be wrong when
You are paying for a stack you do not use
You run little more than core virtualisation, the renewal uplift is sharp, your estate is small, edge heavy or lightly featured, and you are being pushed toward a bundle whose capabilities you will never switch on. If that is you, staying on autopilot simply funds the gap. The honest move is to model the alternatives in parallel, even if you expect to stay one more term, purely to restore leverage.
Most organisations sit somewhere between these two, which is exactly why the decision deserves evidence rather than instinct. The rest of this guide is about turning a renewal you have decided to accept into one you have actually optimised.
Which bundle should you stay on, VVF or VCF?
The single biggest lever in staying well is choosing the right bundle and not over buying. Under the subscription model, VMware is sold largely as two packages. VMware vSphere Foundation, VVF, covers core virtualisation and vSAN. VMware Cloud Foundation, VCF, is the fuller stack that adds the networking, automation, management and private cloud capability. They are priced very differently, and the gap between them is where a lot of money is either saved or wasted.
The mistake we see most often is an estate that uses VMware mainly for vSphere and vSAN being quoted, and renewing on, the full VCF bundle. If you are not genuinely running NSX networking, the automation suite, Tanzu or the hybrid cloud pieces, you are paying for a private cloud platform to run what is, in practice, a virtualisation estate. VVF is frequently the better fit, and the saving is not marginal. One caveat to check first: Broadcom has withdrawn VVF in some regions, so confirm it can be licensed in your market before you build the renewal around it. Where it is not available, the work becomes right sizing within VCF and negotiating that subscription hard.
Do not map the bundle to what you have been sold. Map it to what you actually switch on. Audit your real feature consumption across the estate, then choose the bundle that covers it with the least headroom you are forced to pay for. If VCF is justified by genuine use of networking, automation and hybrid, take it with confidence. If it is not, VVF is not a downgrade, it is right sizing. We cover this decision in depth in our guide on choosing between VCF and VVF.
This is also where the per core mechanics of VMware pricing bite. Licensing is per physical core, with a minimum of 16 cores charged per processor even where the CPU has fewer, and you license every core in the server. Because that multiplies across high core count nodes, the bundle choice and the core count interact. Getting the bundle right while ignoring the core baseline leaves money on the table, and vice versa. vSphere Standard remains the lighter option for smaller estates, but it is capped at 512 cores, so larger estates are steered to VVF or VCF.
Right sizing is a discipline rather than a one off: reconcile entitlement against deployment by cluster and node, stop paying for features nobody switched on, and revisit sizing as workloads change. Our guide to reducing your VMware renewal sets out each lever.
How do you keep the renewal under control while staying?
Staying does not mean accepting the quote. The first figure on a Broadcom renewal is rarely the floor, and Broadcom’s standard rules on terms and minimums are a starting position that can be softened in negotiation. The leverage comes from evidence of what you actually use, a credible alternative for part of the estate, and starting early. That approach took a Fortune 500 company’s Broadcom renewal to 56 percent below the quote, saving more than £1 million, as our case study shows.
The full set of levers, from core counts and bundle to term and timing, is in our guide to reducing your VMware renewal after Broadcom. For a quick number first, the VMware renewal calculator estimates your exposure in under a minute. Or talk your renewal through with us and we will tell you what is negotiable.
What does VCF 9 compliance reporting mean if you stay?
Staying on VMware now carries an operational duty that did not exist before, and it is one you cannot afford to treat as paperwork. Broadcom’s product terms require customers running version 9 or later to submit a verified report of their installed base and licence compliance, due 180 days after the licence is registered and every 180 days after that. Failure to do so on time can degrade management plane functionality and suspend support entitlements, including access to updates. Source: Broadcom VCF product description, January 2026. In other words, missing a reporting deadline is not a billing footnote, it can affect the running of the platform and your access to support.
Assign ownership of the compliance reporting before you need it, build it into your operational calendar, and make sure the person responsible understands that the consequence of slipping is operational, not just commercial. Staying well means staying compliant by design, so the obligation never becomes the reason your support lapses at the worst possible moment.
Which VMware versions are still supported?
Staying well means staying supported. vSphere and vSAN 7.0 reached end of general support on 2 October 2025, and vSphere 8 follows on 11 October 2027, so any estate on version 8 needs an upgrade plan. Version 9 brings the compliance reporting above with it, and it is only available on VCF or VVF: vSphere Standard and Enterprise Plus are supported only up to version 8 Update 3, per Broadcom KB 409233. If you are on Standard, staying beyond October 2027 means a bundle change as well as an upgrade. If a perpetual licence has lapsed, support can no longer be bought for it, Broadcom sent cease and desist letters in 2025 to perpetual users applying patches after support expired, and its critical security patch policy for expired contracts now covers vSphere 8 only. Source: Broadcom KB 314603. Time the version upgrade and the renewal together, so neither forces the other.
When is staying the wrong answer?
An adviser who only ever tells you to stay is no more independent than one who only ever tells you to leave. There are estates where staying well still does not get you to a defensible number. If your uplift remains punishing after right sizing and a proper negotiation, if your feature use is genuinely light, or if your strategic direction is moving away from the platform anyway, then the better answer is a planned, unhurried exit rather than another reluctant renewal. Staying should be a decision you can justify on the numbers, not the path of least resistance. If that is where you land, our decision framework and the specific migration guides are the right next read.
C4C assesses both sides before you commit: the full cost of staying against the full cost of moving to Nutanix, Microsoft Azure or Azure Local, Hyper-V, Proxmox or OpenShift, including migration services, running both platforms during the move, hardware, tooling and retraining, and the technical limits that could stop a workload moving, from application vendor support to the networking, storage and disaster recovery features you rely on. You get a clear recommendation: renegotiate and stay, move part of the estate, or move. We do not resell VMware licences. We do supply Nutanix and Veeam, and say so where they are in the running. Talk to us about a stay or migrate assessment.
How does C4C help organisations stay on VMware?
We spent years on the vendor side, across VMware, Dell and the wider infrastructure market, on both the technical and the commercial side, so we know how these renewals and quotes are constructed and where the give is. Our independence is the point: we do not resell VMware licences and we model staying against the alternatives on the same basis, so when we tell you to stay, it is because the numbers say stay. We run the entitlement audit, model VVF against VCF against the alternatives on a consistent basis, build the negotiation evidence, and help you keep VMware on terms you can stand behind.
Staying on VMware? Make sure the renewal is right sized
Send us your renewal, quote or current contract. We will audit the entitlement, model VVF against VCF against your real feature use, and tell you what you should actually be paying. We do not resell VMware licences, so we take no margin on your renewal. We have sat on the other side of the table.
How we are paid. A fixed fee, a share of the saving we achieve, or professional services such as a licence audit. Never a margin on VMware licences.
Prefer email? Reach us directly at hello@c4cgroup.co.uk.
Frequently asked questions
Is staying on VMware after Broadcom a bad idea?
Not at all. For large estates that genuinely use the broad stack, where operations and tooling are deeply integrated and the workloads are stable, a well negotiated renewal is often more rational than a year long migration to escape a number you could have brought down at the table. Staying is the wrong call mainly when your feature use is light, the uplift is sharp, and you are funding a bundle you do not switch on.
Should I choose VVF or VCF?
Map the bundle to what you actually use, not to what you have been quoted. VMware vSphere Foundation, VVF, fits estates that are mostly vSphere and vSAN with light feature use, where it is still available, since Broadcom has withdrawn it in some EMEA countries. VMware Cloud Foundation, VCF, is justified when you genuinely run the networking, automation, Tanzu or hybrid capability. Many estates are quoted VCF while using little beyond VVF.
Can a Broadcom VMware renewal actually be negotiated?
Yes. The first quote is rarely the floor, and Broadcom’s standard rules can be softened in negotiation. The leverage comes from evidence of what you genuinely use, a credible alternative for part of the estate, and starting early. In one engagement that took a Fortune 500 company’s Broadcom renewal to 56 percent below the quote, saving more than £1 million.
What is the version 9 compliance reporting requirement?
Broadcom’s product terms require customers running version 9 or later to submit a verified report of their installed base and licence compliance within 180 days of registering the licence and every 180 days after. If it is not submitted, management features can be degraded and support suspended. Assign ownership and build it into your operational calendar before you upgrade.
When does VMware vSphere 8 support end?
vSphere 8 reaches end of general support on 11 October 2027. vSphere and vSAN 7.0 reached it on 2 October 2025. Estates staying on VMware should plan the move to version 9, which brings the compliance reporting duty, and time it alongside the renewal.
When is leaving VMware the better decision?
When staying well still does not reach a defensible number. If the uplift remains punishing after right sizing and a proper negotiation, your feature use is genuinely light, or your strategy is moving away from the platform anyway, a planned, unhurried exit beats another reluctant renewal. Our decision framework and the specific migration guides cover that path.
Does C4C resell VMware licences?
No. C4C does not resell VMware licences, so we take no margin on your renewal and have no reason to push you into a bigger bundle or off the platform. We are paid a fixed fee, a share of the saving we achieve, or for professional services such as a licence audit or a migration.