Unable to perform vMotion due to lack of shared storage and vCenter IP subnet at destination cluster
Network segment change (New IP/Gateway) is required at the destination.
Need to decommission the source ESXi hosts or cluster.
VMware vCenter Server 7.x
VMware vCenter Server 8.x
ESXi hosts using Distributed Switches (DVS) or Standard Switches (VSS)
Standard vMotion migration requires shared storage and network heartbeat. Without these, a traditional migration is not possible. A manual deployment and host migration strategy is required.
To migrate the environment under these constraints, follow these steps:
Prepare ESXi Hosts (DVS to VSS Migration)
If the source hosts use a Distributed Virtual Switch (DVS), migrate the management and virtual machine networking to a Standard Virtual Switch (VSS) on each host. For detailed steps, see Migrate VMs and VMkernel adapters from DVS to VSS.
Deploy New vCenter Server
Deploy a new vCenter Server Appliance on the destination cluster using the required new IP address, Subnet Mask, Gateway, and DNS settings. Ensure forward and reverse DNS records are updated for the new IP.
Prepare for Host Migration
Log in to the new vCenter Server and create a new Datacenter and Cluster object.
Disconnect and Move ESXi Hosts
Post-Migration Validation