Introduction to migration waves

A wave is one sitting: which VMs (or folders) move together, which maps they use, and which Plan CRs MTV creates. You prepare the wave in AAP, start it in MTV, then verify and archive.

  1. Configure providers — source hypervisor on the destination cluster.

  2. Configure storage and network maps.

  3. Defining a migration wave — Plan CRs, not the copy itself.

  4. Preparing VMs for migration — guest-side checks when the workload needs them.

  5. Migrating VMs — start the Ready plans.

  6. Verifying a migration and Archiving the plan.

Launch each AAP template for one source_name + target_name pair (inventory host names). There is no workflow that loops every pair.