Virtualisation and VDINew in this releasePublished 20 July 2026

vSphere 7 is out of general support: upgrade to vSphere 8 or move to another platform?

vSphere 7 reached end of general support on 2 October 2025. Evaluate hardware compatibility, licensing, backup, networking, storage and team capability before deciding.

Control risk before changing productionValidate first in a test environment or on one representative system, and preserve configuration, logs and recoverable backups. Production cutovers, bulk policy changes, database repair and storage rebuild require a maintenance window and explicit rollback criteria.

1. Conclusion and scope

A virtualisation decision cannot be based on licence price alone. Hardware compatibility, backup support, storage and network migration, operational experience and the three-to-five-year growth path all affect total cost and risk.

This issue involves virtualisation, hardware compatibility, backup and migration. Prove the target platform and recovery process first.

2. Risk signals that deserve priority

Existing ESXi hardware is absent from the vSphere 8 compatibility list and firmware or driver support has ended.
Subscription, budget or vendor-policy changes make the current licensing model difficult to continue.

3. Pre-change assessment checklist

Inventory version dependencies across vCenter, ESXi, vSAN, NSX, Horizon, backup and monitoring.
Check processors, NICs, HBAs, RAID, firmware, TPM and boot-mode compatibility.
Export VM configuration, resource pools, networks, VLANs, distributed switches, storage policies and permissions.
Compare feature gaps, support models and migration tooling for vSphere 8, Hyper-V, Proxmox VE and other candidates.

Read-only checks and validation examples

esxcli system version get
esxcli hardware platform get
esxcli software vib list
Get-VM | Select Name,PowerState,NumCpu,MemoryGB

corp.example, 192.0.2.0/24 and 203.0.113.0/24 are documentation-only examples. Replace them only after the actual environment values have been verified.

4. Recommended implementation sequence

Where hardware and licensing remain suitable, validate the vCenter and ESXi 8 upgrade path in a test cluster.
For a platform change, build a small target cluster first and prove backup, restore, networking, performance and operations.
Migrate in business batches while retaining rollback copies and spare capacity on the original platform.
Redesign monitoring, backup, patching, access control and capacity management rather than treating the project as VM copying.

Remote assessment or on-site work?Logs, configuration and a small number of systems can usually be assessed remotely. Physical servers, storage, data-centre power, bulk cutover and recovery exercises should use a controlled on-site window. On-site service is available for Zhejiang, Shanghai and Jiangsu; other locations can be supported remotely.

5. Validation, rollback and common mistakes

Critical VMs pass restart, backup, restore, snapshot, migration and high-availability tests.
VLANs, MTU, storage multipathing, time synchronisation and monitoring alerts are correct.
Capacity, performance and licensing cover expected growth on the target platform.

Common mistakes

Comparing only the price per CPU or host.
Moving production VMs before proving backup and disaster recovery.
Releasing old-platform capacity before the rollback period ends.

Official references

Broadcom: End of General Support for vSphere 7.0

Frequently asked questions

Will vSphere 7 stop running after general support ends?

No, but support, patching and compatibility exposure increases, so a defined upgrade or replacement plan is necessary.

Is Proxmox VE always cheaper?

Licence cost can be lower, but migration, training, support, backup and operational costs must be included.

Need an assessment based on the actual environment?

Provide versions, topology, complete errors, event-log timestamps, scope of impact, recent changes and actions already taken. We will first determine risk, service boundary and rollback, then confirm the implementation scope.