Legacy vCenter Server migration support was introduced in Cloud Director Availability 4.4.1. To leverage legacy vCenter Server migrations, deploy a supported version of Cloud Director Availability on both the source legacy on-premises site and the destination cloud site.
The supported source vCenter Server and ESXi versions for legacy migrations are:
Note: From Cloud Director Availability 4.6 onwards, source vCenter Server and ESXi versions 6.5 and 6.7 are now considered legacy vSphere environments.
Note: The legacy vCenter Server 5.5, 6.0, 6.5, and 6.7 versions do not support the VMware Cloud Director Availability vSphere plug-in. You can either migrate the workloads from the on-premises appliance interface or from the cloud site as incoming migrations.
Only migrations are supported from the legacy vCenter Server source site.
It is only supported to migrate workloads in a single direction, from an on-premises site to a cloud site where the legacy vCenter Server is the source on-premises site. Depending on the cloud site, the legacy migrations support the following use cases:
For more information on the Cloud Director Availability deployment types in an on-premises site, see the Installation, Configuration, and Upgrade Guide in On-Premises and Provider Site section of the Cloud Director Availability documentation.
The classic data engine is the only data engine supported for legacy migrations.
As legacy vSphere environments reach both the end of general support and technical guidance, VMware Cloud Director Availability offers best effort support only to resolve issues encountered with legacy workload migrations.