VMware Cloud on Public Cloud supports several ways to migrate your workload VMs from your on-premises hosts to the ones in your SDDC and back again, as well as across hosts in your SDDC. The method you choose should be based on your tolerance for workload VM downtime, the number of VMs you need to move, and your on-premises networking configuration.

It's important to note that any constraints that apply to on-premises migrations are likely to apply to hybrid migrations as well. For example, issues described in Activate Virtual CPU Performance Counters can prevent migration of VMs that enable performance counters when the source or destination cluster enables Enhanced vMotion Compatibility.

Migration within the SDDC

Migration within SDDC refers to migrating virtual machines in your SDDC vCenter Server from one host or cluster to another. For information about migrations like this, see Migrating Virtual Machines in the VMware vSphere Product Documentation.

Hybrid Migration

Hybrid migration refers to migrating virtual machines between two different vSphere installations: one that's in your on-premises data center and another that's in your VMware Cloud on Public Cloud SDDC. Because these two vSphere installations might have different versions, configurations, or both, hybrid migration use cases typically carry additional prerequisites and configuration that ensure both compatibility of the virtual machines and appropriate network bandwidth and latency. VMware Cloud on Public Cloud supports a variety of tools and methods for hybrid migration.

If vCenter Enhanced Linked Mode or Hybrid Linked Mode are not active in your SDDC, you can use Advanced Cross vCenter vMotion to migrate workloads from your on-premises environments to your cloud environments. With Advanced Cross vCenter vMotion, you can move or clone workloads across vCenter Server systems in different vCenter Single Sign-On domains. For more information, see Export or Clone a Virtual Machine in the vCenter Server and Host Management guide.