VMware vSphere 7 support ended: what to do now

General support vs technical guidance

These two get confused constantly, and the distinction decides how exposed you are. General support, which ended in October 2025, is the real thing: security patches, bug fixes, and the ability to raise a case with support. Technical guidance, which runs until April 2, 2027, is self-help only: documentation and knowledge-base access, with no new patches and no engineering fixes. Being inside the technical-guidance window is not the same as being supported, and an auditor will not treat it as such. For the terminology in general, see EOL vs EOS vs EOSL.

The lifecycle at a glance

vSphere 7, vCenter Server 7 and vSAN 7 share the October 2, 2025 date. Check each component: a vCenter left behind on 7 is as unsupported as the hosts.

Why an unpatched hypervisor is the worst kind of EOL

Most end-of-life risk is proportional to one device. A hypervisor is different: compromise the host and every virtual machine on it is exposed at once, including the domain controllers, file servers and databases you carefully patched. ESXi has had its share of actively exploited vulnerabilities, and ransomware crews specifically target unpatched hosts because encrypting the datastore takes out an entire estate in one move. That is why this expiry belongs at the top of the list rather than in the backlog. For the wider consequences, see how unsupported software affects compliance and insurance.

Your options, honestly compared

• Upgrade to vSphere 8. The direct path, and the right answer for most estates already invested in VMware. Go in with your eyes open: vSphere 8 reaches end of general support on October 11, 2027, so treat it as the next step, not the destination, and check hardware compatibility because newer ESXi drops support for older server generations.
• Move to VMware Cloud Foundation or the vSphere Foundation bundle. Under Broadcom, licensing consolidated into subscription bundles rather than standalone perpetual licences, with higher per-core minimums. For some estates this is a straightforward renewal; for smaller ones it is a significant cost change worth modelling before committing.
• Buy extended support, if it is still offered to you. A paid bridge to finish a migration already under way. Expensive, time-boxed, and not a strategy on its own.
• Migrate to another platform. Proxmox, Hyper-V, Nutanix and public cloud have all seen serious evaluation since the licensing changes. Genuinely feasible, but it is a project measured in months, not a patch window, so decide early rather than under deadline pressure.

Do not forget the hardware underneath

A vSphere 7 cluster is usually running on servers bought around the same time, which puts that hardware near its own end of service life, and newer ESXi releases drop support for older CPU generations. So the upgrade decision is rarely just software: for many teams the honest answer is that the hosts need replacing too, and the hypervisor upgrade is what surfaces it. Model both together. If you are sizing the spend, the refresh budget calculator turns a host count into an annual number, and treating software and hardware as one lifecycle management problem is what keeps them from colliding.

A plan for a deadline that has already passed

• Now: inventory every ESXi host, vCenter and vSAN cluster with its exact build, and confirm which are still on 7.x. Make sure no management interface is reachable from the internet.
• This month: decide the destination per cluster, vSphere 8, a Broadcom bundle, or another platform, and check hardware compatibility for the version you pick.
• Next two quarters: run the upgrades or migrations, starting with the clusters holding your most sensitive workloads.
• Ongoing: record the new platform's end-of-support date on day one, including the October 2027 vSphere 8 date, so the next one is a planned project rather than a surprise.

Related deadlines worth noting

The same servers often carry several expiries at once: Windows Server 2016 leaves extended support on January 12, 2027, Windows Server 2019 on January 9, 2029, SQL Server 2016 ended on July 14, 2026, and Exchange 2016 and 2019 in October 2025. The full, continuously updated view sits on the IT end-of-support calendar.