Your next VMware decision
Make your next VMware decision with confidence.
Rising costs, renewal deadlines, and migration risks can make the next step feel overwhelming. Our advisors help you understand your options and choose a path that fits your infrastructure, team, and budget.
- A clearer shortlist. Options worth evaluating, including staying on VMware.
- The key tradeoffs. Cost, migration effort, and operational risk.
- Practical next steps. What to verify before a renewal or migration.
30-minute conversation. Free advisory guidance. No obligation to move forward. See an example review.
Explore a rough cost estimate first
Adjust your VM count and storage for a directional annual range across eight paths. This is a planning estimate, not a provider quote.
Total usable storage for your VMs, before replication or backup copies. 1 TB = 1,000 GB. Default: 20 TB for 100 VMs; adjust to your actual environment.
Estimated annual cost across 8 paths
Request a written options review
Prefer to start by email? Request a written shortlist with the main tradeoffs and next steps. An advisor will reply within one business day and confirm any details needed for your review. A meeting is optional.
We couldn't save your request. Please try again.
Request received. An advisor will reply within one business day with next steps for your written review. A meeting is optional. You can also talk through your options.
vSphere 7 lifecycle dates
| Component | End of General Support | End of Technical Guidance | Status today |
|---|---|---|---|
| ESXi 7.0 | Oct 2, 2025 | Apr 2, 2027 | Past EoGS, no new patches |
| vCenter Server 7.0 | Oct 2, 2025 | Apr 2, 2027 | Past EoGS, no new patches |
| vSAN 7.x | Oct 2, 2025 | Apr 2, 2027 | Past EoGS, no new patches |
| vSphere 7 individual update releases | Vary by release | Vary by release | Many fell out well before Oct 2025 |
The October 2025 date was itself an extension. General support was originally scheduled to end on April 2, 2025, and Broadcom pushed it back six months. That extension is the source of the confusion covered in the next section.
The eighteen-month gap nobody budgeted for
This is the detail that separates vSphere 7 from every other version in the matrix, and it works against you.
When Broadcom extended general support by six months, from April 2025 to October 2025, it did not move the technical guidance date to match. That date stayed anchored where it always was, two years after the original general support date. So the six months of extra general support came out of the technical guidance window rather than being added to the end of it.
| Version | General support ends | Technical guidance ends | Gap between them |
|---|---|---|---|
| vSphere 7 | Oct 2, 2025 | Apr 2, 2027 | 18 months |
| vSphere 8 | Oct 11, 2027 | Oct 11, 2029 | 24 months |
If you planned on the usual two-year tail, you have six months less runway than you think. And technical guidance was never runway in the first place, which is the next point.
What each date actually changes
| Milestone | What you lost, or will lose | What you keep |
|---|---|---|
| End of general support Oct 2, 2025 (passed) | New security patches, bug fixes, hardware and guest OS enablement, the ability to open a support case | The software runs. Existing licences remain valid. Previously published patches stay available. |
| End of technical guidance Apr 2, 2027 | Self-service access to previously published patches and the documentation path | Nothing meaningful. This is the true end of the line. |
Technical guidance is routinely misread as a grace period. It is not. No new patches are produced during it. You get self-service access to material that already existed on the day general support ended, and nothing more. Every ESXi vulnerability disclosed since October 2025 is one with no vendor fix for your version.
What running vSphere 7 exposes you to right now
This is not a future risk on this version. It is the current state of the estate.
- Unpatchable vulnerabilities. ESXi is a high-value ransomware target precisely because compromising one host reaches every VM on it. Since October 2025 there has been no vendor remediation path for anything newly disclosed against 7.0.
- Compliance findings today, not at renewal. PCI DSS, HIPAA, SOC 2 and most cyber-insurance questionnaires ask directly whether systems are vendor-supported. The honest answer for vSphere 7 has been "no" for months.
- Insurance exposure. Carriers ask about end-of-life systems at renewal. Answering that question inaccurately is a coverage problem at exactly the moment you need the coverage.
- Hardware and guest OS drift. New server generations and new guest operating systems are no longer certified against 7.0, so your refresh cycle is now blocked by your hypervisor.
Your options from here
You are past the deadline, so the question is no longer whether to move but which move costs least. Upgrading in place is one option among five, not the default.
| Option | What it involves | Best when |
|---|---|---|
| Upgrade and subscribe | Move to vSphere 8 or VCF 9 on per-core subscription direct with Broadcom | Deep VMware dependencies and a budget that absorbs the increase. Note this buys you the October 2027 deadline next. |
| Managed VMware provider | Keep vSphere, run it in a VCSP provider's cloud at their scale pricing | You want VMware without Broadcom's direct pricing. See providers. |
| Migrate platforms | Replatform to Nutanix, Proxmox, Hyper-V, or OpenShift | Hardware refresh is due anyway and long-term cost control is the goal. See the comparisons. |
| Hyperscaler VMware service | AVS, GCVE, or VMware Cloud on AWS | Data-center exit on a deadline. Note these mostly keep you licensing VMware. See the GCVE migration guide. |
| Third-party support bridge | Independent support covers the gap while you execute | You are already unsupported and need 6 to 18 months of cover. Not a destination. |
The trap specific to vSphere 7 is treating the in-place upgrade as the safe, cheap choice because it is the familiar one. Under per-core subscription pricing the upgrade often arrives with a materially different bill, and the effort of moving to a different platform is frequently similar. Price both before committing to either. The cost calculator gives you a starting figure.
What to do, in order
- This week. Inventory exact ESXi builds and vCenter versions. Some update releases fell out of support well before October 2025, so parts of the estate may be further behind than the version number suggests.
- This month. Establish what you are actually entitled to. Contract changes since the Broadcom acquisition affect whether the April 2027 technical guidance date applies to you at all.
- Next 90 days. Price every option, including staying and paying. Do this before your next renewal conversation, not after, or you negotiate with nothing in hand.
- Before April 2, 2027. Be landed on something supported, with the 7.0 estate decommissioned.
If a full migration cannot land inside that window, a third-party support bridge is the honest interim answer. It is not a destination, but it is better than an audit finding and it buys the time to choose properly. See the renewal negotiation guide for where the leverage sits.
vSphere 7 end-of-life FAQ
When did vSphere 7 reach end of life?
End of general support was October 2, 2025. That date was itself an extension: it was originally April 2, 2025, and Broadcom pushed it back six months. End of technical guidance is April 2, 2027.
Is ESXi 7 still supported?
No. ESXi 7.0 and vCenter Server 7.0 have been past end of general support since October 2, 2025. They receive no new security patches. The software still runs, but no vendor patch exists for anything disclosed after that date.
Why does vSphere 7 only get 18 months of technical guidance when vSphere 8 gets two years?
Because the technical guidance date was never moved. It stayed anchored to the original April 2, 2025 general support date, while general support itself was extended to October 2, 2025. The six-month extension came out of the technical guidance window rather than being added to the end.
What is the difference between end of general support and end of technical guidance?
General support includes new patches, security fixes and hardware enablement. Technical guidance is self-service access to previously published patches and documentation only. No new patches are produced during it, and you cannot open a support case.
Can I just upgrade vSphere 7 to vSphere 8?
You can, but check the licensing cost before the technical work. Broadcom's per-core subscription model means an in-place upgrade often arrives with a substantially different bill. The migration effort to a different platform is frequently similar, so price both before committing to either.
When does vSphere 8 reach end of life?
vSphere 8 reaches end of general support on October 11, 2027 and end of technical guidance on October 11, 2029. If you are planning an upgrade from 7, that is the next deadline you are buying into. See the vSphere 8 end of life guide.