Migration playbook · Servers and cloud

How to migrate VMware virtual machines to Google Cloud

Google gives you two routes off on-premises vSphere: convert VMs to Compute Engine instances with Migrate to Virtual Machines, or keep them on VMware in Google Cloud VMware Engine and move them with HCX. Both replicate while the source keeps running.

Updated 4 phases7 detailed steps6 official sources
Start here

Which route should you take for migrating VMware virtual machines to Google Cloud?

Short answer

This moves virtual machines from your VMware servers into Google Cloud. Most organisations convert them into Google Compute Engine VMs with Google's Migrate to Virtual Machines service: a small appliance in vSphere copies each VM's disks while it keeps running, you test a copy, then switch over with a short outage.

  • Recommended route: Migrate to Virtual Machines to Compute Engine, in waves of related VMs
  • Order: Group VMs that talk to each other into waves, connect networks first, and test-clone before every cut-over.
  • 4 phases: Assess and plan waves, Prepare Google Cloud and connect, Replicate and test and Cut over and finalize.
  • You're done when: Every VM in scope runs as a Compute Engine instance or in VMware Engine, with owner sign-off.

If you need to keep running VMware for now, Google Cloud VMware Engine gives you a VMware environment in Google Cloud and HCX moves VMs into it unchanged.

Recommended routeMigrate to Virtual Machines to Compute Engine, in waves of related VMs

VMs keep running while data replicates, you can test without touching the source, and each cut-over is a short planned outage.

Other options and when to use them
  • Google Cloud VMware Engine with HCX: You need to leave VMs on VMware for now, keep IP addresses with network extension, or move fast before a hardware or licence deadline.
  • Rebuild on new VMs or managed services: Old operating systems or apps you were going to replace anyway.
Order to migrate in, and why

Group VMs that talk to each other into waves, connect networks first, and test-clone before every cut-over.

  1. Inventory and wave planVMs that depend on each other should move together to avoid slow links between sites.
  2. Google Cloud project, network and connectivityThe connector and migrated VMs need a VPC and a route back to on-premises.
  3. Migrate Connector installed and source registeredIt reads VM disks from vSphere and sends them to Google Cloud.
  4. Replication started for the first waveThe first full copy can take hours, so start well before cut-over.
  5. Test-clone and app testingFinds driver, network and licence issues without touching the source VM.
  6. Cut-over, checks, then finalizeFinalize deletes replication data, so run it only once you are sure.
Settings checklist: decide these before you copy

Built-in and third-party tools treat these differently. Tick each one off once you have decided.

Download this checklist (Excel)
  • How each tool handles it
    Built-in methodMigrate to Virtual Machines: moves vSphere VMs to Compute Engine instances. Google Cloud VMware Engine: a VMware private cloud where HCX runs cold, bulk and vMotion migrations and can extend Layer 2 networks.

    Tip: Use VMware Engine as a stepping stone if you cannot change IP addresses or operating systems yet.

    Google Cloud VMware Engine: Migrating VMware VMs using VMware HCX
  • How each tool handles it
    Built-in methodMigrate to Virtual Machines: vCenter 6.0, 6.5, 6.7, 7.0 and 8.0; ESXi 5.5 to 8.0.

    Tip: Check the guest operating system is supported on Compute Engine too, before you plan the wave.

    Google Cloud: Prepare a VMware source for migration
  • How each tool handles it
    Built-in methodMigrate to Virtual Machines: TCP 443 and 902 to vCenter, TCP 902 to ESXi, TCP 443 to Google Cloud APIs over the internet, Cloud VPN or Cloud Interconnect, plus DNS. Allow *.googleapis.com and gcr.io.

    Tip: Large estates replicate faster over Cloud Interconnect; check bandwidth against total disk size.

    Google Cloud: Prepare a VMware source for migration
  • How each tool handles it
    Built-in methodMigrate to Virtual Machines: Global.DisableMethods and Global.EnableMethods at the root with propagation; at VM level, change tracking, power off, read-only disk access, VM download and snapshot management.

    Tip: Create a dedicated vCenter user so you can remove it after the project.

    Google Cloud: Prepare a VMware source for migration
  • How each tool handles it
    Built-in methodMigrate to Virtual Machines: rollback is manual. Redirect traffic and restart the source VM; data written on the Compute Engine instance is not copied back.

    Tip: Keep the source VM powered off, not deleted, until the app owner signs off.

    Google Cloud: VM migration process
The plan, phase by phase
  1. 1

    Assess and plan waves

    Weeks 1 to 2

    Watch out: Some operating systems are not supported on Compute Engine.

    Ways around it

    • Use Google Cloud VMware Engine for those VMs, or upgrade first.
    Show the detailed steps (1) →
  2. 2

    Prepare Google Cloud and connect

    Weeks 2 to 3

    Watch out: The connector service account is limited to 19 sources.

    Ways around it

    • Use another service account for larger numbers of vCenters.
    Show the detailed steps (2) →
  3. 3

    Replicate and test

    Weeks 3 to 4

    Watch out: A test-clone is a snapshot; later changes are not in it.

    Ways around it

    • Run a new test-clone after fixing target settings.
    Show the detailed steps (2) →
  4. 4

    Cut over and finalize

    Per wave

    Watch out: Replication storage is charged until finalize.

    Ways around it

    • Finalize promptly after sign-off, and delete test-clone instances.

    Turn this phase into dated tasks with the cutover planner

    Check your DNS records before and after the change

    Show the detailed steps (2) →
You are finished when
  • Every VM in scope runs as a Compute Engine instance or in VMware Engine, with owner sign-off.
  • Migrations are finalized and test-clone instances deleted.
  • Backups and monitoring are set up for the new instances.
  • Source VMs are deleted after the agreed fallback period.
Click by click

What does each step of migrating VMware virtual machines to Google Cloud involve?

Open a part when you reach it in the plan. Each step says where to go, what to do and what you should see.

About this migrationWhat it covers, limits at a glance

Migrate to Virtual Machines copies vSphere VM disks to Google Cloud in the background while the VMs keep running, lets you start test copies, then shuts the source down and creates a Compute Engine instance at cut-over. Google Cloud VMware Engine is the alternative: a VMware private cloud in Google Cloud, where HCX moves VMs without converting them.

This playbook covers choosing between them, setting up the Migrate Connector, testing and cut-over. Weighing other clouds or hypervisors? See VMware alternatives.

Convert to Compute EngineMigrate to Virtual Machines, with the Migrate Connector in vSphere
Keep VMwareGoogle Cloud VMware Engine, moving VMs with HCX
Supported vCenter6.0 to 8.0 (Migrate to Virtual Machines)
ReplicationFull copy, then changed blocks every two hours by default
DowntimeAt cut-over, when the source VM is shut down
RollbackManual: restart the source VM
1What do you need before you migrate VMware virtual machines to Google Cloud?
NeedDetailsWhere to get it
Google Cloud project with the VM Migration API enabledvmmigration.googleapis.comGoogle Cloud console > APIs & Services
User to register the connectorroles/iam.serviceAccountKeyAdmin, roles/iam.serviceAccountCreator and roles/vmmigration.adminGoogle Cloud console > IAM
vCenter user for the connectorGlobal and VM-level permissions listed in Google's source guidevSphere Client
Network pathCloud VPN or Cloud Interconnect, or internet access to Google Cloud APIsYour network team
VM inventoryOperating system, size, dependencies and ownerThe application inventory template
2Choose the target and plan waves1 step
  1. 1

    Decide per group of VMs

    Where: Your inventory spreadsheet

    Mark each VM for Compute Engine, Google Cloud VMware Engine, rebuild or retire. Group VMs that depend on each other into the same wave in the wave plan.

    You should see: A wave plan with owners and change windows.
3Register vSphere as a source2 steps
  1. 1

    Enable the API

    Where: Cloud Shell or a terminal with the gcloud CLI

    Enable the VM Migration API on the host project.

    gcloud services enable vmmigration.googleapis.com
    You should see: The API shows as enabled.
  2. 2

    Install the Migrate Connector

    Where: vSphere Client, then the connector console

    Create the vCenter user, deploy the Migrate Connector appliance in vSphere as described in Google's guide, and register it with your project and region.

    You should see: The source appears on the Sources tab with status Active.
4Replicate and test-clone2 steps
  1. 1

    Add VMs and start replication

    Where: Google Cloud console > Migrate to Virtual Machines > Sources, then Migrations

    On Sources, select the VMs and click Add Migrations > VM Migration. On Migrations, select them and click Migration > Start Replication.

    You should see: Status shows Active, with the first cycle percentage climbing.
  2. 2

    Set target details and test-clone

    Where: Migrations > select a VM

    Set project, machine type and network. Then click Cut-Over and Test-Clone > Test-Clone, using an isolated network so the copy cannot clash with the source.

    You should see: Test-Clone/Cut-Over status shows Succeeded and the test instance runs.
5Cut over and finalize2 steps
  1. 1

    Cut over

    Where: Migrations > Cut-Over and Test-Clone > Cut-Over

    In the change window, run the cut-over. Google shuts down the source VM, runs a final replication and creates the instance. Follow your cutover runsheet for DNS and firewall changes.

    You should see: The cut-over job completes and the new instance answers on its new address.
  2. 2

    Finalize

    Where: Migrations > select the VM > Finalize

    After sign-off, finalize to delete replication data. Delete any test-clone instances separately.

    You should see: The migration state shows Finalized.
Worth knowing

What can go wrong when migrating VMware virtual machines to Google Cloud, and how do you avoid it?

The detail behind the plan: options compared, and what experienced engineers check first. Tap any item.

Compare all the ways to do this3 options

Migrate to Virtual Machines

Medium effort

Best for: Converting vSphere VMs into Compute Engine instances

  • Source runs during replication
  • Test-clones before cut-over
  • Google-managed service
  • Downtime at cut-over
  • Manual rollback
Read more →

Google Cloud VMware Engine with HCX

Medium effort

Best for: Keeping VMs on VMware, or moving without changing IP addresses

  • No conversion
  • Cold, bulk and vMotion migrations
  • Layer 2 network extension
  • You still run VMware
  • Needs HCX set up on both sides
Read more →

Rebuild

High effort

Best for: Old systems you planned to replace

  • Clean start
  • Most effort per app
Our advice

Default to Migrate to Virtual Machines. Use VMware Engine for groups that cannot be converted or re-addressed yet, and plan their move to Compute Engine later.

Cut-over means downtimeUser impact

Cut-over shuts down the source VM, completes a final replication and then creates the instance.

What to do

Schedule each wave in a change window and tell users.

Google Cloud: VM migration process
Rollback is manualReduces risk

Google states rollback is not automated, and data written on the new instance is not copied back.

What to do

Keep source VMs, and write the rollback steps in the rollback plan.

Google Cloud: VM migration process
Replication storage costs until finalizeCost lever

Replication storage is charged until the finalize phase, and test-clone instances are charged until you delete them.

What to do

Finalize after sign-off and clean up test-clones.

Google Cloud: VM migration process
Replication runs every two hoursSaves time

After the first full copy, incremental replication runs every two hours by default using changed block tracking.

What to do

Start replication days before cut-over so the final copy is small.

Google Cloud: VM migration process
HCX licensing in VMware EngineCompliance

From HCX 4.10.3, HCX activates automatically and inherits licensing when the on-premises connector pairs with HCX Cloud Manager.

What to do

Check your on-premises HCX version and licence before planning a VMware Engine route.

Google Cloud VMware Engine: Migrating VMware VMs using VMware HCX
Finish safely

How do you check it worked after migrating VMware virtual machines to Google Cloud, or roll back?

Full validation checklist4 checks

Run these before you declare the migration complete. Record the results in the data validation report.

CheckHow to checkWhat good looks like
Instance boots and apps run

Log in and run the app owner's test script.

All tests pass.
Network paths work

Test connections to databases, file shares and on-premises services.

All dependencies reachable.
Data is current

Check the latest records written before cut-over.

They are present.
Clean-up done

Check migrations are Finalized and test-clones deleted.

No leftover replication storage or test instances.
Rollback planIf it goes wrong

Roll back if

  • The app fails tests on the new instance
  • Performance is unacceptable after cut-over

Point of no return

Until you delete the source VM you can roll back. Writes on the new instance are not copied back, so the longer you run there the more you lose.

  1. 1

    Restart the source VM

    Where: vSphere Client

    Power on the source VM.

    You should see: It runs as before.
  2. 2

    Redirect traffic

    Where: DNS and firewalls

    Point DNS and rules back to the source, and stop the Compute Engine instance.

    You should see: Users reach the source VM.

Agree the triggers and who decides before the go / no-go meeting. Use the rollback plan template.

Common problems and fixes4 errors
Source not Active in Sources tab

Cause: The connector cannot reach vCenter or Google Cloud APIs.

Fix: Check ports 443 and 902 and access to *.googleapis.com and gcr.io.

Replication fails on an encrypted VM

Cause: The vCenter user lacks cryptographic access.

Fix: Add Cryptographic operations > Direct Access permissions.

Cut-over failed and source is off

Cause: The cut-over job did not complete.

Fix: Resume replication, then retry cut-over, or restart the source VM.

New instance cannot reach on-premises services

Cause: Firewall rules or routes are missing in the VPC.

Fix: Add routes and firewall rules, then retest.

Search the full error library →

FAQ

Questions about migrating VMware virtual machines to Google Cloud

Does the source VM keep running during replication?

Yes. It runs until cut-over, when Migrate to Virtual Machines shuts it down.

Can I test before switching?

Yes. A test-clone creates an instance from replicated data without touching the source.

Can I keep VMware in Google Cloud?

Yes. Google Cloud VMware Engine runs VMware, and HCX moves VMs into it.

What happens at finalize?

Replication data is deleted. The Compute Engine instance stays.

Sources

Official sources for migrating VMware virtual machines to Google Cloud

6 official pages this guide is based on

Get one practical migration tip a day

Follow Cloud-Migrations.au on LinkedIn or X for deadlines, error fixes, free templates and outage briefs as they happen.