Thank You Thomps & Sachin

Sorry to ask all these basic Qs. We are using Hyper V as the primary virtualization platform and moving to VMware in stages.

We don't have high availability for those VMs with multiple standalone ESXi hosts, and since many VMs are not compatible with existing ESXi 6.7 cluster, we plan to create 2 X ESXi 6.0 in cluster.

Existing vCenter is configured with one Datacenter & one Cluster with 2 ESXi 6.7 hosts. As you mentioned we will create a new cluster and add those 2 X new ESXi 6.0 hosts in same Datacenter. Here do we need to create multiple DCs (for easy management) since the new cluster need to be managed by ESXi management team as well by the team owing all those VMs.

If the existing standalone ESXi's are managing from a vCenter server, then as per the update from Thomps, we could not add them to the vCenter server managing new ESXi cluster, right? What is the option / workaround to add those standalone ESXi's to the vCenter managing new cluster. The team responsible for standalone ESXi hosts are on training, so we are not sure how they are managing those hosts (through vCenter or GUI)

We referred the KB for Shared nothing vMotion requirements and limitation document, will check source and destination hosts for the compatibility. By combining the recommendations from both of you what we understood is, each source ESXi host should be added to the new cluster in same vCenter server, then do a vMotion. Is it right?

xv Motion is same as what we mentioned above?

Thank You