Add a migration source

Before you start migrating, create a migration source that represents the source platform from which you'll be migrating. This source will be added to your migration plan. You may use migration sources that were previously configured in Migrate to Containers for migrating other Linux or Windows VMs.

Define the migration source you're migrating from by using the migctl source create command:

  1. For a processing cluster deployed on Google Cloud, create the source:

    1. When using Compute Engine as the migration source:

      1. Create a service account for using Compute Engine as a migration source and download the JSON key file, as described in Configuring a service account.

      2. Create the source using the service account:

        migctl source create ce my-was-src --project my-project --json-key m4a-ce-src.json

        Where m4a-ce-src.json specifies the service account.

    2. When using AWS as the migration source:

      migctl source create aws my-was-src --manager-address 1.2.3.4 --cloud-details cloud-details --cloud-extension cloud-extension

      Specify the name of the Migrate for Compute Engine Extension and the Cloud Details name, as configured in Migrate for Compute Engine. For more on Cloud Details, see set up Migrate for Compute Engine.

      You'll be prompted for the password for your Migrate for Compute Engine management server.

    3. When using Azure as the migration source:

      migctl source create azure my-was-src --manager-address 1.2.3.4 --cloud-details cloud-details --cloud-extension cloud-extension

      Specify the name of the Migrate for Compute Engine Extension and the Cloud Details name, as configured in Migrate for Compute Engine. For more on Cloud Details, see set up Migrate for Compute Engine.

      You'll be prompted for the password for your Migrate for Compute Engine management server.

    4. When using VMware as the migration source:

      migctl source create vmware my-was-src --manager-address 1.2.3.4 --cloud-extension cloud-extension

      Specify the name of the Migrate for Compute Engine Extension, as configured in Migrate for Compute Engine.

      You'll be prompted for the password for your Migrate for Compute Engine management server.

  2. For an Anthos on-prem processing cluster on VMware, create the source:

    migctl source create local-vmware my-was-src --vc '1.2.3.4' --username 'admin'

    Where:

    --vc specifies the vCenter DNS name or vCenter IP address.

    --username specifies the username for a user that has permission to access the vCenter. You will be prompted to enter the password for the user.

  3. For an Anthos on AWS processing cluster, create the source:

    migctl source create local-aws local-aws-src --region my-region --access-key-id my-access-key-id

    or:

    migctl source create local-aws local-aws-src --region my-region --credentials-file-path=credentials.csv

    Where:

    --region specifies the Google Cloud region of your cluster.

    --access-key-id specifies the AWS access key ID for a user that has permission to access AWS. You are prompted to enter the secret for the access key ID. See Managing access keys for IAM users for more.

    --credentials-file-path specifies the path to a CSV file, downloaded from the AWS console, containing the credentials. See Configuring AWS IAM groups and instance roles for more on creating the CSV file.

  4. For an Anthos clusters on bare metal cluster, create the source... (this section to be filled in by @danarad)

Next steps

Create a migration plan