Run a migration

Migration follows the recovery workflow for protected VMs, with one difference: it is a final cutover, so the goal is zero data loss. Run it on the recovery site: Configure → (protection plan) → Actions → Migrate.

Run a migration

1. Select virtual machines

   Select the VMs to migrate. If pre/post scripts are configured, provide guest credentials (or upload a credentials file — it is removed from the system once recovery completes).

2. Optional: Auto-Migrate

   Auto-Migrate performs the final cutover sequence automatically:

   1. Powers off the source VMs.
   2. Runs replication cycles until there is no changed data.
   3. Initiates the migration.

   During Auto-Migrate the VM status moves through migration_init to migrate-init-success. A warning with details is shown when the option is selected.

3. Tools and scripts

   • Install System Agents — installs EC2Launch + SSM Agent (AWS), the google-compute-engine agent set (GCP), the Azure VM agent (Azure), or VMware Tools (VMware) into migrated guests. Required when assigning static IPs on VMware targets.
   • Install Cloud Packages — installs the AWS or Google Cloud SDK on the migrated guests.
4. Summary

   Review and click Finish. Migration jobs start for the selected VMs — monitor them under Jobs → Recovery.

After migration

• Verify each migrated instance via the IP shown in the recovery jobs (RDP for Windows, SSH for Linux).
• Migration consumes license capacity; the consumption bar under Settings → License reflects it.
• Migrated workloads appear with recovery type Migration in the jobs history, and the dashboard's RPO/RTO panel counts total migrations.

Related docs

• Easy Migrate overview

• Create a plan

• Jobs