October 2, 2025 came and went. Every organization still running vSphere 7 in production today is running unsupported, unpatched infrastructure. This is not a future risk. It is a current compliance and security exposure, and the planning window to address it is narrowing fast.
On October 2, 2025, Broadcom ended general support for VMware vSphere 7.x, vCenter Server 7.x, and vSAN 7.x. Broadcom confirmed this date on the official VMware Cloud Foundation blog, noting that after that date, customers running vSphere 7.x would receive no new security patches, no bug fixes, and no ability to engage Broadcom Support for these releases. It is now May 2026. That date is seven months in the past.
For organizations still running vSphere 7 in production, the question is not whether the deadline matters. It is whether the organization has formally acknowledged the exposure and built a plan to address it.
What 'Unsupported' Actually Means in Practice
The practical consequences of running unsupported infrastructure are not abstract. When a new CVE is discovered affecting vSphere 7 components, Broadcom will not release a patch for it. Infrastructure teams managing vSphere 7 environments today are operating with a fixed, aging security surface that grows more vulnerable with every unpatched vulnerability identified in the platform.
For regulated industries, the compliance implications are immediate. PCI DSS, HIPAA, and SOC 2 frameworks require that systems handling sensitive data operate on supported, patchable infrastructure. An audit that surfaces vSphere 7 in production after October 2025 is an audit finding, not a future risk to plan for. The IT Vortex analysis of VMware's 2026 licensing and support landscape describes this combination of unsupported infrastructure and a narrowing partner ecosystem as a compounding risk that most organizations underestimated.
The Technical Guidance Window Is Also Closing
Some organizations are operating under the assumption that the Technical Guidance phase, which runs until April 2, 2027, provides meaningful support continuity. It does not. Technical Guidance means access to previously published patches and documentation only. No new security patches. No ability to contact Broadcom Support. No hardware compatibility updates. April 2, 2027 is the date when even that limited fallback expires entirely.
The practical planning implication is this: an organization that has not yet begun a migration program has less than 23 months before vSphere 7 loses its last form of support. Gartner's research, reported by Network World, estimates that comprehensive VMware migration programs require 18 to 48 months end-to-end. At the upper end of that range, the window has already closed. At the lower end, it is closing.
Why Nutanix Is the Validated Path Forward
The organizations that have moved most decisively off vSphere 7 since October 2025 share a consistent characteristic: they evaluated their destination platform before their support deadline rather than after it. Nutanix AHV, documented in depth in the Nutanix Cloud Bible, is the hypervisor platform with the largest installed base of organizations that have already completed or are actively executing VMware exits. Nutanix Move, Nutanix's purpose-built migration tool, is specifically designed to handle vSphere 7 workload migration to AHV with VirtIO driver injection, background data replication, and managed cutover.
The ReadyWorks VM Accelerator provides the estate inventory that makes a Nutanix migration program executable: a normalized view of every vSphere 7 workload and its actual resource consumption, available immediately upon connecting to vCenter or ingesting RVTools or Nutanix Collector data. VirtualReady then takes that foundation into the full operational program: wave modeling, automated scheduling, stakeholder communications, and cutover execution integrated with Nutanix Move and Nutanix Prism, with full audit trails throughout. For organizations that have been delaying because they do not yet have the inventory data to plan a program, this is the starting point.
The Timeline Visual
The six confirmed VMware and Broadcom deadlines between October 2025 and October 2027 do not arrive in isolation. They arrive simultaneously with three-year subscription renewal cycles, a narrowed partner ecosystem, and hardware costs at their highest point in years. The organizations that navigate this window successfully are the ones that started planning before each deadline became a crisis.
READY TO ACT?
Start with the data. The ReadyWorks VM Accelerator gives you a complete, normalized vSphere 7 estate inventory immediately upon connecting to vCenter or ingesting RVTools or Nutanix Collector data. Try it free for 45 days with no commitment. Learn more about VM Accelerator
FREQUENTLY ASKED QUESTIONS
Is vSphere 7 still safe to run after October 2, 2025?
No. After October 2, 2025, Broadcom provides no new security patches, no bug fixes, and no technical support for vSphere 7.x. New vulnerabilities discovered in vSphere 7 after this date will not be patched by Broadcom, leaving production environments with a permanently expanding unpatched attack surface.
What is the difference between End of General Support and End of Technical Guidance?
End of General Support (October 2, 2025) ended new patches, bug fixes, and Broadcom Support access. End of Technical Guidance (April 2, 2027) will end even the limited self-service access to previously published patches and documentation. After April 2027, vSphere 7 has no support of any kind.
How does running unsupported VMware infrastructure affect compliance?
PCI DSS, HIPAA, and SOC 2 frameworks require that systems handling regulated data operate on supported, patchable infrastructure. Running vSphere 7 in production after October 2025 creates direct audit exposure for organizations subject to these frameworks.
How long does a Nutanix migration program actually take?
Gartner estimates 18 to 48 months for a comprehensive VMware migration program. The range reflects program scale and complexity. Organizations that have not yet begun should assume a timeline in the middle of that range and start immediately to ensure April 2027 Technical Guidance expiry does not arrive before migration is complete.
