[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-19。"],[],[],null,["# Prepare a VMware source for migration\n\nMigrate to Virtual Machines lets you migrate your virtual machines (VMs) running\nin an on-premises vSphere data center to VM instances running on Google Cloud.\n\nBefore you begin\n----------------\n\n- Enable Migrate to Virtual Machines on Google Cloud. See [Enabling Migrate to Virtual Machines services](/migrate/virtual-machines/docs/5.0/get-started/enable-services).\n- Enable the **VM Migration API** on your host project using \u003chttps://console.cloud.google.com/apis/library/vmmigration.googleapis.com\u003e.\n- Review the [VMware versions supported by Migrate to Virtual Machines](#VMware-versions).\n- Review the [operating systems that support migrating VMs from VMware as a source](/migrate/virtual-machines/docs/5.0/discover/supported-os-versions) to Google Cloud.\n- Review [Migrating VMs with Migrate to Virtual Machines: Getting started](/migrate/virtual-machines/docs/5.0/discover/migrating-vms-migrate-for-compute-engine-getting-started) documentation. This document provides insight into the overall structure of Migrate to Virtual Machines including, key terms, concepts, and reference information that'll help you migrate your workload efficiently and effectively.\n\nMigrate your workload from an on-premises VMware source\n-------------------------------------------------------\n\nTo migrate VMs from an on-premises VMware source, you must configure a\n*migration source* that specifies the on-premises data center from which you'll\nbe migrating the VMs. To configure a migration source, you have to install and\nconfigure the **Migrate Connector** on your on-premises vSphere data center.\n\nThe following diagram shows the architecture of a typical Migrate to Virtual Machines deployment:\n\n\u003cbr /\u003e\n\n[](../images/m4ce-arch.svg)\n\n\u003cbr /\u003e\n\nFollow these steps to install and configure a Migrate Connector, and create a\nVMware source:\n\n1. **On vSphere** , you must create a vCenter user account with the permissions\n required by the Migrate Connector to access your vSphere environment.\n See [Create the vCenter user for the Migrate Connector](#step-1).\n\n2. **On Google Cloud** define two accounts:\n\n - A **user** account with the necessary permissions to perform registration.\n This user account is only used at registration time.\n\n - A **service** account used by the Migrate Connector for run-time data\n transfer to Google Cloud.\n\n See [Define Google Cloud accounts](#step-2).\n3. **When registering the Migration Connector,** you must provide the\n Google Cloud region used to host your migrated VMs.\n See [Select the Google Cloud region](#step-3).\n\n4. **Ensure that you have enabled network access for the Migrate Connector**\n as described in [Configuring network access](#step-4).\n\n5. **Install and register the Migrate Connector** as described in\n [Install the Migrate Connector](#step-5).\n\n### Create the vCenter user for the Migrate Connector\n\nCreate a vCenter user account with the permissions required by the Migrate\nConnector to access your vSphere environment. You then pass the user credentials\nto the Migrate Connector at install time.\n\nThe following table lists the permission names and the corresponding permissions\nas shown in the vSphere UI:\n| **Note:** The `Global.DisableMethods` and `Global.EnableMethods` permissions must be set at the Global, or root, level with propagation. The remaining permissions can be applied at the VM level.\n\n### Define Google Cloud accounts\n\nOn Google Cloud, you need two accounts:\n\n- A [service account](/iam/docs/service-accounts) in your host project used by\n the Migrate Connector for run-time data transfer to Google Cloud.\n\n You can specify an existing service account, or let the Migrate Connector\n create a new one for you. The Migrate Connector applies all necessary\n permissions to the service account to configure it.\n- A [user account](/iam/docs/overview) in your host project with the\n necessary permissions to register the Migrate Connector.\n This user account is only used at registration time, not at run time.\n\n | **Note:** The service account used by the Migrate Connector is limited to 19 sources. If you want to register more than 19 sources to the same Migrate to Virtual Machines host project, you need to create additional service accounts.\n\nThe following diagram shows the service accounts and user accounts\nassociated with a Migrate to Virtual Machines deployment:\n\n\u003cbr /\u003e\n\n[](../images/m4ce-sa.svg)\n\n\u003cbr /\u003e\n\n#### Configure the user account\n\nYou can specify any user account in your host project to register the Migrate\nConnector. The specified user account requires the following permissions:\n\n- `roles/iam.serviceAccountKeyAdmin`\n- `roles/iam.serviceAccountCreator`\n- `roles/vmmigration.admin`\n\n1. Determine the email address of the user account you want to use for\n registration. In the [Google Cloud console](https://console.cloud.google.com/), you can see all users in your\n project on the **IAM** page:\n\n [Go to the IAM page](https://console.cloud.google.com/iam-admin/iam)\n2. Grant the `iam.serviceAccountKeyAdmin` role to the user account:\n\n ```\n gcloud projects add-iam-policy-binding PROJECT_ID\n --member=user:USER_EMAIL_ADDRESS --role=roles/iam.serviceAccountKeyAdmin\n ```\n | **Note:** Depending on the security configuration of your project, you might be prompted to select a [condition](/iam/docs/conditions-overview). Often selecting the option of None is correct, but confirm that with your security team.\n3. Grant the `iam.serviceAccountCreator` role to the user account:\n\n ```\n gcloud projects add-iam-policy-binding PROJECT_ID\n --member=user:USER_EMAIL_ADDRESS --role=roles/iam.serviceAccountCreator\n ```\n4. Grant the `vmmigration.admin` role to the user account:\n\n ```\n gcloud projects add-iam-policy-binding PROJECT_ID\n --member=user:USER_EMAIL_ADDRESS --role=roles/vmmigration.admin\n ```\n\nFor more on assigning roles and permissions to a user account, see\n[Granting, changing, and revoking access to resources](/iam/docs/granting-changing-revoking-access).\n\n### Select the Google Cloud region\n\nOn the Google Cloud a [region](/docs/geography-and-regions) is a specific\ngeographical location where you can host your resources. Regions have three or\nmore zones. For example, the `us-west1` region denotes a region on the west\ncoast of the United States that has three zones: `us-west1-a`, `us-west1-b`, and\n`us-west1-c`.\n\nYou choose which region hosts your resources, which controls where your data is\nstored and used. Distribute your resources across multiple regions to tolerate\noutages. Therefore, if a region experiences any disturbances, you should have\nbackup services running in a different region.\n\nWhen you install the Migrate Connector on vSphere, you select a Google Cloud\nregion. The source VMs migrated using this connector are then associated with\nthe chosen region.\n\nTo migrate VMs to multiple regions, you must:\n\n1. Create a host project.\n\n2. Install and configure a separate Migrate Connector for\n each [supported Google Cloud region](/migrate/virtual-machines/docs/5.0/resources/locations).\n\n3. Migrate and deploy your VMs selecting the supported region for each VM or VM\n group.\n\nIn that way, if one region goes down, you can still perform migrations by using\na migration source associated with a different region.\n\nSee [Migrate to Virtual Machines locations](/migrate/virtual-machines/docs/5.0/resources/locations) for a\nlist of supported regions.\n| **Note:** Migrate to Virtual Machines supports migration to multiple regions using the same host project. Each Migrate Connector you connect to a Google Cloud project facilitates migration to a specific region. If you are migrating to multiple regions you will need to deploy a separate Migrate Connector for each region.\n\n### Configure network access\n\nEnable network access for the Migrate Connector by opening the required ports and\nby opening access to the domains required by the Google Cloud APIs:\n| **Note:** Your on-premises or Google Cloud VMware Engine hosts might also use [Private Google Access](/vpc/docs/private-access-options). With Private Google Access, your on-premises or Google Cloud VMware Engine hosts connect to Google Cloud APIs through a Cloud VPN tunnel or Cloud Interconnect. To configure the DNS on your on-premises hosts for private access, set Google API Address as **Private** or **Restricted** . For more information on configuring Private Google Access for your on-premises hosts, see [Private Google Access-specific domains and VIPs](/vpc/docs/private-google-access-hybrid).\n\n1. Ensure that you have enabled network access for the Migrate Connector.\n The following table lists the network connectivity requirements for the connector:\n\n2. Ensure that the firewall rules on your vSphere or VMware Engine\n server allow external access to the following domains required by the\n Google Cloud APIs:\n\n - `*.googleapis.com`\n - `gcr.io`\n\n### Install the Migrate Connector\n\nYou can now install and register the Migrate Connector. For more information, see\n[Installing the Migrate Connector](/migrate/virtual-machines/docs/5.0/migrate/migrate-connector).\n\nAfter you've installed and registered the Migrate Connector, you can start\nmigrating your VMs from your on-premises vSphere data center to\nGoogle Cloud. For more information, see\n[Next steps: Start your migration](#next-steps).\n\nSupported VMware Versions\n-------------------------\n\nMigrate to Virtual Machines supports migrations from VMware vCenter and ESXi.\n\nThe latest Migrate to Virtual Machines release is compatible with VMware versions:\n\n- vCenter: 6.0.\\*, 6.5.\\*, 6.7.\\*, 7.0.\\*, 8.0.\\*\n- ESXi: 5.5.\\*, 6.0.\\*, 6.5.\\*, 6.7.\\*, 7.0.\\*, 8.0.\\*\n\nNext steps: Start your migration\n--------------------------------\n\nStart your migration process, see\n**[Migrating individual VM](/migrate/virtual-machines/docs/5.0/migrate/migrating-vms)**."]]
