Stay organized with collections
Save and categorize content based on your preferences.
Workload VM migration
Using Google Cloud VMware Engine, you can migrate virtual machines (VMs) from an
on-premises data center to your private cloud. Your private cloud provides
native access to VMware vCenter, which supports a variety of tools for workload
migration.
Migration options
You can migrate workload VMs to your private cloud in multiple ways. Here are
some of the more common options to consider:
VMware HCX. Create a hybrid infrastructure by abstracting and presenting
vSphere-based on-premises and cloud resources to applications as one
continuous resource
Backup and disaster recovery tools. Use your private cloud as a target to
restore backups.
VMware PowerCLI. Migrate VMs from one vCenter to another using a
command-line interface.
ISO files and templates. Create new VMs by uploading an ISO file to your
private cloud and using a VM template from your published vSphere content
library.
NSX Layer 2 VPN. Live migrate workload VMs by making an on-premises subnet
available on your private cloud.
Migration requirements
Migration of VMs and data from your on-premises data center requires network
connectivity between the data center and your private cloud. Before you can
migrate workloads, set up a site-to-site VPN connection between your on-premises
environment and your private cloud.
The network path from your on-premises vCenter environment to your private cloud
must support migration of VMs by using vMotion. The vMotion network on your
on-premises vCenter must have routing abilities. Verify that your firewall
allows all vMotion traffic between your on-premises vCenter and private cloud
vCenter. On the private cloud, routing on the vMotion network is configured by
default.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Workload VM migration\n=====================\n\nUsing Google Cloud VMware Engine, you can migrate virtual machines (VMs) from an\non-premises data center to your private cloud. Your private cloud provides\nnative access to VMware vCenter, which supports a variety of tools for workload\nmigration.\n\nMigration options\n-----------------\n\nYou can migrate workload VMs to your private cloud in multiple ways. Here are\nsome of the more common options to consider:\n\n- **VMware HCX.** Create a hybrid infrastructure by abstracting and presenting vSphere-based on-premises and cloud resources to applications as one continuous resource\n- **Backup and disaster recovery tools.** Use your private cloud as a target to restore backups.\n- **VMware PowerCLI.** Migrate VMs from one vCenter to another using a command-line interface.\n- **ISO files and templates.** Create new VMs by uploading an ISO file to your private cloud and using a VM template from your published vSphere content library.\n- **NSX Layer 2 VPN.** Live migrate workload VMs by making an on-premises subnet available on your private cloud.\n\nMigration requirements\n----------------------\n\nMigration of VMs and data from your on-premises data center requires network\nconnectivity between the data center and your private cloud. Before you can\nmigrate workloads, set up a site-to-site VPN connection between your on-premises\nenvironment and your private cloud.\n\nThe network path from your on-premises vCenter environment to your private cloud\nmust support migration of VMs by using vMotion. The vMotion network on your\non-premises vCenter must have routing abilities. Verify that your firewall\nallows all vMotion traffic between your on-premises vCenter and private cloud\nvCenter. On the private cloud, routing on the vMotion network is configured by\ndefault."]]
