Broadcom’s published lifecycle information lists 11 October 2027 as the End of General Support date for vSphere 8.0. That’s over a year away at the time of writing, which is exactly why it’s worth thinking about now rather than later. The organisations that handle these deadlines well are rarely the ones that start planning in the final quarter.
If this feels like a familiar conversation, it should. vSphere 7.0 reached End of General Support on 2 October 2025, and plenty of our customers found themselves scrambling in the weeks either side of that date. vSphere 8’s deadline gives you a longer runway, but only if you use it. Why write about a 2027 deadline now? A few reasons:
Migrations take longer than people expect. Between hardware compatibility checks, licensing decisions, third-party tooling validation, and actual cutover planning, a properly sequenced vSphere migration is measured in months, not weeks. Starting in 2027 means starting under pressure.
Budget cycles don’t move quickly. If a hardware refresh or licensing change is part of your path forward, that likely needs to go through a budget planning cycle, which for most organisations means this needs to be on next year’s roadmap conversation, not next year’s emergency. Feed into that the current Hardware supply issues, and planning well in advance is imperative
You may still be catching up from vSphere 7. If your organisation only recently moved off vSphere 7, or is still mid-migration, it’s worth knowing where vSphere 8 sits in your roadmap before you finish one project and immediately need to plan the next.
The runway shortens every quarter you don’t think about it. A year and a bit sounds like plenty of time. It compresses quickly once you factor in procurement, testing, and business-as-usual workload.
What “End of General Support” means when it arrives
Broadcom’s support lifecycle for vSphere runs through two main phases:
- General Support – the full package: security patches, bug fixes, and hardware compatibility updates
- Technical Guidance – a much thinner offering after General Support ends: self-service documentation and limited advice, with no new patches or fixes
Once vSphere 8 moves into Technical Guidance in October 2027, your environment doesn’t stop working, but newly discovered vulnerabilities go unpatched, new hardware won’t get certified against it, and direct troubleshooting support from Broadcom becomes much harder to get. For infrastructure sitting underneath your entire virtual estate, that’s a materially different risk position than staying on a fully supported version.
What this means if you’re currently on vSphere 7
If your organisation is still running vSphere 7.x, this deadline matters in a different way: vSphere 7.0 has already passed its End of General Support date of 2 October 2025, so you’re not planning of a future deadline, you’re already operating past one. In that position, vSphere 8 isn’t a “plan for 2027” conversation, it’s one of your live upgrade options right now, alongside extended support or an alternative platform. Worth treating as a separate, more urgent thread within the same overall roadmap.
Building a sensible timeline
There’s no single right answer for when to start, it depends on estate size, hardware age, and how much change appetite the business has. As a rough shape:
12+ months out: Get visibility. Inventory current versions across ESXi, vCenter, and vSAN. Understand hardware compatibility against vSphere 8 or 9 and flag any kit that will need refreshing regardless of which path you take – Remember, current lead times on Servers and Storage systems is upwards of six months and these times may not improve for many months yet.
6–12 months out: Make the platform decision. Upgrade within the VMware ecosystem or evaluate alternatives properly rather than under time pressure. This is also the point to revisit your licensing position under Broadcom’s current subscription model, which has changed substantially from the perpetual licensing many organisations budgeted around historically.
3–6 months out: Validate third-party dependencies, backup software, monitoring and DR orchestration against the target platform, and run the migration plan past a second set of eyes before committing to a cutover date.
Final stretch: Execute in a controlled, phased way. A migration that’s been planned properly rarely needs to be rushed at the end.
The platform question worth asking early
Is staying within the VMware ecosystem still the right long-term call for your organisation, particularly given the licensing changes since the Broadcom acquisition?
For some, the answer is straightforwardly yes – upgrade to the next supported version and move on. For others, it’s worth evaluating alternatives properly. HPE Morpheus VM Essentials, for example, is designed to run alongside an existing VMware estate rather than forcing an all-at-once switch, so you can manage both VME and VMware-based VMs from a single interface while you assess the fit at your own pace.
This isn’t a call to make reactively in the final months before a deadline. It’s a call worth making with time to properly test the alternative against your actual workloads.
Where to start
Whether your deadline pressure is 2027 or already behind you, the groundwork is the same:
- Inventory exactly what versions you’re running across the estate
- Check hardware compatibility against your likely target platform
- Understand your current licensing position and what changing it would mean commercially
- Audit third-party tooling for compatibility with the target version or platform
- Build a realistic timeline that doesn’t compress the final stages
The deadline itself isn’t the risk. An unplanned scramble in the months beforehand is. Getting ahead of it now, even just by putting it on the roadmap, is the difference between a controlled migration and a rushed one.
Book your VMware Renewal Assessment with Nexstor now.
