This overview outlines the general steps required for migrating VMs from Microsoft Azure to Google Cloud using Google Cloud Migrate for Compute Engine (formerly Velostrata).
Configure the source and destination for migration
- Set up GCP as a migration destination. Before beginning a migration to Google Cloud, you must create Cloud Identity and Access Management permissions.
- Set up a VPN for communication between the migration source and destination. Plan for and create a secure connection between Azure and Google Cloud. One way to do this is to follow this guide.
- Configure network access. See Network Access Requirements for detailed information on firewall, routing, and network tag considerations for your Migrate for Compute Engine deployment.
- Create Azure credentials in the Migrate for Compute Engine Manager that will enable Migrate for Compute Engine to connect to Azure.
- Set up the Migrate for Compute Engine Manager. The Migrate for Compute Engine Manager provides a web UI and controls migration operations from Google Cloud.
- Create Cloud Details on your Migrate for Compute Engine Manager using your Azure credentials.
- Set up Cloud Extensions. After configuring the Migrate for Compute Engine Manager, create Cloud Extensions for your migration.
- Create a test clone for a given VM to perform a test migration, then validate the migrated VM. A test clone is a copy of the VM and doesn't use live data from the source platform.
- Prepare your Linux VMs. If you are migrating Linux VMs, install the Migrate for Compute Engine package to reconfigure them for Google Cloud.
Migrate a wave of VMs. Migrate for Compute Engine organizes groups of VMs into waves. When you understand the dependencies of your applications, create runbooks that contain groups of VMs, then begin your migration.