vSphere 8 End of Life: Your Options Before October 2027

vSphere 8 reaches end of life on 11 October 2027, and there is no vSphere 9 Standard or Enterprise Plus to upgrade into. That second half is the part most teams have not absorbed. vSphere 9 exists only inside VMware vSphere Foundation or VMware Cloud Foundation — so for anyone running Standard or Enterprise Plus, this is not a version upgrade. It is a move to a different product, on a fixed deadline.

That turns what looks like a routine end-of-support notice into a scheduled platform decision, and it lands for a lot of estates at the same time as a renewal. This piece covers what the deadline actually forces, the three real paths, and the arithmetic worth doing before anyone quotes you.

Three facts, in the order they matter.

vSphere Standard went end of sale on 31 July 2025. You cannot buy it new. Existing agreements run their term.

Standard and Enterprise Plus stop at 8 Update 3. There is no version 9 of either edition. Whatever build you are on is close to the last one those product lines will ever receive.

vSphere 9 is not a standalone SKU. It ships inside VVF or VCF. This is the structural change — Broadcom collapsed a large catalogue into a small number of bundles, and the standalone hypervisor edition is not one of them.

Put together: the thing you are running has a terminal version and a terminal date, and the successor is a bundle rather than an edition. If you have been treating this as "we will upgrade when we get to it", the upgrade you are picturing does not exist.

Every estate on Standard or Enterprise Plus lands on one of these. They are not equally priced and they are not equally disruptive.

VVF is the like-for-like path. It carries the Enterprise Plus hypervisor capability and adds vSAN entitlement, vSphere Kubernetes Service and operations tooling. For most estates this is the answer, and the transition is a commercial motion rather than an architectural one.

VCF is the step up. NSX networking, VCF Automation, VCF Operations for Networks and SDDC Manager fleet lifecycle management. It costs more per core and it earns that when you genuinely need software-defined networking, self-service provisioning, or to patch a large fleet as a unit. If you would not deploy those, you are buying a private cloud platform to run a virtualization workload. We work through that decision in detail in VCF vs VVF: which tier do you need.

Leaving VMware is real but front-loaded. Some estates should. It involves hardware, retraining, a cutover plan and a period of running two platforms — which is why it is a programme decision, not a way to dodge a renewal quarter. Teams that decide this late usually end up renewing once anyway to buy the runway.

One regional caveat that removes the choice for some organisations: Broadcom withdrew VVF from several EMEA countries in December 2025. If your entity or a subsidiary sits in an affected market, VCF may be the only supported path, and that is worth confirming before you build a business case around VVF pricing.

Licensing is per physical core, and two minimums decide more of the total than the list price does.

16-core minimum per CPU socket. A socket with 12 physical cores licenses as 16. On a fleet of smaller hosts that gap compounds quickly.

72-core minimum per order, introduced in April 2025. Small estates pay for 72 cores whether or not they have them. If you are running a handful of hosts, this single rule may be the largest line on your quote.

Two practical consequences. First, host consolidation changes the number — fewer, denser hosts can license better than many small ones, and that is worth modelling before you commit to a hardware refresh. Second, term length is the main discount lever: multi-year commitments price materially better than one-year, so the tier decision and the term negotiation are the same conversation.

Count your cores before you request a quote. A renewal quote built on an assumed inventory is a quote for the wrong thing, and it is much harder to unwind after it has been issued.

Running past end of life is always technically possible. What it means in this environment is worth stating plainly.

No patches and no security fixes, on a hypervisor that sits underneath everything else you run. No supported upgrade path when you eventually move, which usually makes the later migration harder rather than easier. And the same compliance posture as any unsupported estate — which matters more than it used to, because Broadcom has been actively pursuing perpetual licence holders whose support has lapsed.

If that describes you — perpetual licences, expired SnS — there is a further constraint worth understanding before you plan around "we will just stay where we are": you may not be entitled to the build you are currently running. We covered that in can Broadcom disable your perpetual VMware licence. The short version is that there is no remote kill switch, but the constraint is version rather than time, and post-expiration patches are exactly what the cease-and-desist letters target.

Four steps, and the first two are the ones that get skipped.

1. Inventory what you actually hold. Which editions, on which hosts, with which expiry dates. Mixed estates carrying two or three legacy SKUs are the norm, not the exception, and the mapping into the new portfolio is rarely obvious from the outside.
2. Count physical cores per socket and model both minimums against your real footprint. Do this before you talk to anyone about price.
3. Decide the tier on requirements, not on the quote. Do you need NSX? Do you need automated fleet lifecycle management? If the honest answer is no, VVF is the answer and you should not be talked upward.
4. Start early enough to have leverage. A large share of the base converted to three-year terms in 2024 and 2025, so renewals and this deadline cluster in the same window. Quote turnaround and attention both get scarcer as that builds.

If you want the inventory checked and VVF and VCF priced side by side against your actual core counts, talk to AceMQ — we are a Broadcom partner and we run this analysis weekly. We will also tell you when VVF is plainly the right answer, because for most estates it is.