VMware Renewal or Re-platform: Deciding Before vSphere 8 General Support Ends
How to decide between renewing VMware and re-platforming before vSphere 8 general support ends on October 11, 2027, based on your hosts, storage, backup, network, and licensing.
vSphere 8 general support ends October 11, 2027; decide with an inventory, not the date alone
Broadcom ends general support for vSphere 8.0, including ESXi 8.x, vCenter 8.x, and vSAN 8.x, on October 11, 2027. Whether you renew or move to another platform, the deciding factors are the same: how old your hosts are, where your storage lives, how backup and recovery work, what your network and security policies depend on, and how many cores you license. Decide with that inventory, not the support date alone.
What Broadcom's support dates say
Broadcom publishes End of General Support dates for vSphere releases. vSphere 7.0 has already passed its date, and Broadcom's knowledge base recommends upgrading to 8.0 or later. The dates below are from Broadcom's knowledge base as of November 2026; confirm them on Broadcom's pages before you plan around them.
| Product or version | Milestone (Broadcom term) | Date | Source |
|---|---|---|---|
| ESXi 8.x, vCenter 8.x, vSAN 8.x | End of General Support | October 11, 2027 | Broadcom KB 459135 |
| vSphere ESXi and vCenter 7.0, vSAN 7.0 | End of General Support | October 2, 2025 | Broadcom KB 326984 |
| vSphere ESXi and vCenter 6.5 and 6.7, vSAN 6.5 to 6.7 | End of General Support | October 15, 2022 | Broadcom KB 326984 |
What to inventory before you price anything
Start with a written picture of the environment. Every path, renewal or re-platform, is priced and planned from the same facts, and surprises later often come from something nobody counted.
- Hosts. Model, age, warranty or support contract dates, and the number of physical CPUs and cores in each host.
- Clusters and vCenter instances. Which hosts belong to which cluster, and which vCenter manages them.
- Storage. vSAN raw capacity per host, or the external arrays in use, with current capacity and performance headroom.
- Backup and disaster recovery. Which tools protect the virtual machines, where replicas go, and when recovery was last tested.
- Network and security. Virtual switching, segmentation, and firewall rules that depend on where virtual machines run.
- Workloads. Owners, operating systems, and applications whose own licensing is tied to hosts or cores.
- Sites. Which locations run clusters, which pairs back each other up, and when each can take a change window.
How Broadcom counts licensed capacity
Broadcom licenses VMware Cloud Foundation (VCF) and vSphere Foundation (VVF) on physical CPU cores, so the inventory above is also your licensing input. This guide quotes no prices; these are the counting rules Broadcom documents.
Cores across the hosts you license
Core licensing is based on the total number of physical CPU cores across the ESXi hosts you intend to license.
A 16-core minimum per CPU
For VCF and VVF, each physical CPU counts as at least 16 cores, even if it has fewer. In Broadcom's own example, three hosts with one 8-core CPU each require 48 cores. VCF Edge uses an 8-core minimum per CPU instead.
Licenses attach to vCenter in 9.0
In version 9.0, VCF and vSphere Foundation share one licensing model: you assign licenses to vCenter instances, and connected ESXi hosts are licensed automatically. Starting with version 9.1, Broadcom also lets you assign a license directly to assets such as ESX hosts and vSAN clusters, so check the licensing page for the version you will run.
vSAN capacity
If you run vSAN, record the raw capacity each host contributes to vSAN as well as the capacity in use, and check the vSAN entitlement for your edition and version on Broadcom's licensing pages.
Four paths, and what each one depends on
Each path is a project with its own dependencies. The useful comparison is not renewal against migration in the abstract, but which path fits your hosts, storage, tooling, and staff for each cluster.
| Path | When it fits | What it depends on | Watch for |
|---|---|---|---|
| Renew and upgrade in place | Hosts are current and supported for the target release | Host compatibility with the target release, licensed core counts | Older hosts that cannot run the target release |
| Renew and refresh hosts | Hosts are near the end of their warranty or support | Sizing new hosts for cores, memory, and storage | Core counts changing the licensed capacity |
| Re-platform to another hypervisor | The platform decision is open and the timeline allows a migration | The target platform's hardware compatibility list, backup support, policy rebuild | Backup, recovery, and security policies that have to be rebuilt |
| Move selected workloads to a public cloud | Specific workloads suit a cloud platform | Data location, application licensing, network connectivity | Workloads that depend on each other being split across platforms |
Hosts, storage, backup, and network decide the real scope
The hypervisor decision touches every layer under and around it. Check these before you commit to a path.
Host refresh timing
If hosts are due for refresh anyway, the renewal and the refresh can be planned as one project, sized once. If they are new, compatibility with the target release or platform is the first check.
Storage capacity and performance
Count raw vSAN capacity against the vSAN entitlement for your edition and version, or confirm that external arrays are supported by the target platform. Size for growth, not only for today's capacity.
Backup and disaster recovery
Backup and replication tools often integrate with the hypervisor. A platform change can change how backups run and how recovery works, so test a restore on the new platform before moving production.
Networking and security
Segmentation and firewall rules tied to virtual machine placement have to be migrated or recreated. Document them before the first wave.
See the server and storage refresh planning page and the backup and recovery planning page.
Sequencing the work across sites
Multi-site environments are usually easier to move in waves than all at once. A pilot cluster shows what the inventory missed while the stakes are still small.
- Pilot first. Move or upgrade one non-critical cluster end to end, including backup and a test restore.
- Waves by site or workload. Group clusters so that each wave has one owner and one change window.
- Keep pairs together. Sites that back each other up move in a planned order, so recovery keeps working throughout.
- Plan the way back. Keep a rollback path for each wave until the next one starts.
- Close the loop. Record final host and core counts after each wave, and retire what is no longer used.
See the Windows Server 2016 end of support guide and the multi-site operations page.
Turning the decision into a project plan
Before talking to any vendor, give your own team these four outputs, so every option is compared on the same facts. If your team does not have the time to build them, the inventory and a ranked replacement plan are what a fixed-fee end-of-support assessment produces.
- A host and core inventory, by cluster and site.
- A storage and backup map, including when recovery was last tested.
- A path per cluster: renew and upgrade, refresh, re-platform, or move to cloud.
- A wave plan with change windows and a rollback path for each wave.
Frequently asked questions
When does vSphere 8 support end?
Broadcom ends general support for vSphere 8.0, including ESXi 8.x, vCenter 8.x, and vSAN 8.x, on October 11, 2027.
Is vSphere 7 still supported?
No. Broadcom's end of general support for vSphere ESXi and vCenter 7.0 and vSAN 7.0 was October 2, 2025, and its knowledge base recommends upgrading to 8.0 or later.
How are VMware Cloud Foundation and vSphere Foundation licensed?
On the total number of physical CPU cores across the ESXi hosts you license, with a minimum of 16 cores counted for each CPU, even when a CPU has fewer.
Should we renew VMware or move to another platform?
Decide from your inventory: host age, storage, backup, network dependencies, and core count. Renewing fits when a migration cannot finish before your renewal date; re-platforming fits when hardware is due anyway or the core count makes the renewal hard to justify.
Plan your VMware decision with Days Dynamics
Send us your host, storage, and workload inventory and we will help you compare renewing with re-platforming for each cluster, size any host or storage refresh, and plan the sequence of work across your sites. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.
Sources
Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.
- Broadcom KB 459135: End of General Support for vSphere 8.0 (opens in a new tab)
- Broadcom KB 326984: End of General Support for vSphere 6.5/6.7/7.0 (opens in a new tab)
- Broadcom KB 313548: Counting Cores for VMware Cloud Foundation and vSphere Foundation and TiBs for vSAN (opens in a new tab)
- Broadcom TechDocs: VMware Cloud Foundation 9.1 Licensing Model (opens in a new tab)
- Broadcom TechDocs: VMware Cloud Foundation 9.0 Licensing Model (opens in a new tab)
Related services
Related resources
Turn the checklist into a plan
The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.
