Staying on VMware: How to Do It Well After Broadcom

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.

When staying is the right call, and when it is not

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.

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.

Right size the bundle: VVF versus 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.

This is also where the per core mechanics 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.

Negotiate the renewal, do not accept it

The first quoted figure on a Broadcom renewal is rarely the floor. The transparency is limited, the SKUs have shifted, and the quote is constructed to a default that suits the vendor, not to your actual usage. Treating it as fixed is the most expensive assumption you can make.

Negotiating well rests on evidence, not on bluster. You need a clear baseline of your active cores, your processors and your real entitlement, separated cleanly from what you are being billed for. With that in hand, the conversation changes from accepting a number to challenging it on facts. This is precisely what produced the result in our VMware renewal case study, where independent audit and modelling held a UK enterprise's renewal uplift well under 80 percent against an early projection of up to 410 percent, avoiding a six figure annual increase and securing a one year term that kept options open.

• Build the baseline first: active cores, CPUs, entitlement gaps and who actually owns the support contract.
• Model your exposure under more than one scenario, so you know your walk away position before you start.
• Keep a credible alternative alive. The fastest way to lose a negotiation is for the vendor to know you have nowhere else to go.
• Be wary of long terms offered as a discount. A multi year lock can be the right trade, but only once, and only when the commercial terms have stopped moving.

If you want a fast, no signup sense of the number before any conversation, our VMware renewal calculator estimates your exposure from your hosts and cores in under a minute. For the full picture of why the figure jumped and how to read it, our renewal cost guide is the companion piece.

Handle the version 9 compliance obligation properly

Staying on VMware now carries an operational duty that did not exist before, and it is one you cannot afford to treat as paperwork. Version 9 introduces a compliance reporting requirement. You are expected to submit regular verified reports, and failure to do so on time can degrade management plane functionality and suspend support entitlements. 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.

Stop paying for capability you do not use

Right sizing is not a one off event at renewal, it is a discipline. Over years, estates accumulate licensed capability that no one switched on, entitlement that drifted away from deployment, and assumptions that were never revisited. Each of those is money leaving the building quietly.

• Reconcile entitlement against actual deployment, by cluster and by node, not just by contract line.
• Identify features you are licensed for but do not run, and decide deliberately whether to use them or stop paying for them.
• Watch for overlap with tools you already own elsewhere, where you may be paying twice for the same capability.
• Revisit sizing as workloads change, so consolidation or refresh is reflected in what you license rather than discovered two renewals later.

Be honest about when staying is 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.

How C4C helps

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 have no platform to defend and no preferred destination, 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.

Renewing VMware and want to know it 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 give you an evidence based view of what you should actually be paying. Independent, with no platform to sell and no preferred vendor. We have sat on the other side of the table.

Name *

Company *

Work email *

Phone (optional)

Details

Request a renewal review

Prefer email? Reach us directly at hello@c4cgroup.co.uk.

Frequently asked questions