In this video, you will learn how to migrate more than one virtual machine at a time using a feature called the Migration Wave. So far in this module, you've learned how to migrate a single virtual machine. Enterprise Cloud migration projects often include moving hundreds, if not thousands, of application workloads from on-premises or other clouds into Google Cloud Platform. Migrating the entirety of your data center at once is challenging, if not impossible. It is important to assess your workloads and batch them into different migration groups. One of the main decision drivers of a migration group is often related to application affinity, where certain systems must maintain specific latencies between each other. In those types of scenarios, you will want to migrate these applications as one migration group called the migration wave. A migration wave is a way of organizing the systems you want to move into batches that make your migration strategy more manageable. Now that you understand why we leveraged migration waves, let's discuss how we go about choosing which systems to group together for your first migration wave. One of the most important considerations to think about when choosing systems for the first wave is to focus on the business criticality of the individual workload. We recommend choosing workloads and underlying systems that are the least business critical. These workloads will give you the opportunity to get comfortable with your migration process while minimizing risk early on in the migration. Another recommendation would be to migrate your application development or test environments first. You will also want to consider your application Service Level Agreements, or SLA, and up-time requirements. Workloads that can experience interruption and downtime without major business impact or batch processes are also excellent migration workloads for the first wave. Another point that's important to consider is your workloads' licensing and compliance requirements. A good first-mover is either a workload that's developed in-house or one whose licensing requirements support running in a Cloud environment. Low compliance complexities are another indicator of a strong first wave candidate. Lastly, when choosing your first wave candidates, you wanna select workloads that have fewer system and network to network dependencies. By taking this approach, you minimize your migration scope and reduce technical complexities.