Assess
Establish the environment, dependencies and scope of the issue before changing anything.

Upgrade or migrate ESXi / vCenter platforms, hosts, virtual machines and storage with hardware compatibility and workload validation planned in advance.
Confirm hardware compatibility, vCenter / ESXi versions, VM dependencies, storage and backup before sequencing the platform upgrade and workload moves.
The same delivery discipline applies to migrations, remediation, operational handovers and other critical infrastructure changes.
Capture current versions, roles, dependencies and protection state.
Confirm the target platform, compatibility and known constraints.
Choose the migration or upgrade path and define synchronization, cutover and rollback.
Implement in the approved window and validate the real business path.
Keep a defined observation / rollback window and provide the new operating baseline.
Before implementation we define ownership, maintenance windows, verification and rollback. After the change we retain key records and handover documentation.
Establish the environment, dependencies and scope of the issue before changing anything.
Define scope, impact, maintenance window, verification and rollback.
Execute within the approved scope and keep evidence at key checkpoints.
Validate system behavior, access, business paths and recovery capability.
Provide configuration baseline, implementation record, residual risks and next actions.
For project decision-makers
vSphere 7 general support ended in October 2025. Compare an in-family upgrade with alternatives such as Proxmox VE against application support, hardware compatibility, storage, backup and rollback costs.
Scope and impact depend on the live environment; no unverified zero-downtime promise.
Versions, roles, dependencies and known issues.
Affected services, acceptable downtime and validation criteria.
Maintenance window, backup state and rollback conditions.