You are now viewing Migrate to Virtual Machines (formerly Migrate for Compute Engine). For Migrate for Compute Engine versions 4.x, see the 4.x documentation.

Migrate to Virtual Machines 5.0 release notes

Stay organized with collections Save and categorize content based on your preferences.
This page documents production updates to Migrate to Virtual Machines. You can periodically check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.

You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or you can programmatically access release notes in BigQuery.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly: https://cloud.google.com/feeds/migrategce-release-notes.xml

August 02, 2022

Several updates to Migrate to Virtual Machines:

July 05, 2022

Connector renaming

Includes the following updates:

  • Renamed CLI command from m4c to m2vm
  • Renamed product to Migrate to Virtual Machines
  • Bug fixes

June 27, 2022

The maximum amount of active VMs has been increased from 100 to 200 VMs.

March 17, 2022

Migrate for Compute Engine allows you to employ a VPC-SC service perimeter and communicate with select services using your migrate connector.

For more information about using a VPC-SC perimeter, see the secure your migrations in a service perimeter documentation.

October 26, 2021

Migrate VMs using UEFI firmware. Using UEFI firmware you can enable Secure Boot migration details.

October 25, 2021

#199379063 Windows migrated VMs have GooGet installed with a wrong root directory

Windows VMs migrated before October 7th 2021 may have GooGet (Google package manager) installed with the wrong root directory (C:\Windows\System32\%ProgramData%\GooGet instead of C:\ProgramData\GooGet).

Workaround: Reinstall GooGet and guest environment by following the instructions to Install a guest environment in-place. A copy of googet.exe can also be found under C:\Google\Migrate\GooGet, which allows you to skip the download command in step 1. C:\Windows\System32\%ProgramData%\GooGet can be safely deleted if needed.

Following the steps to install a guest environment in place will also update guest environment packages to their latest released versions.

October 03, 2021

Migrate for Computer Engine now supports the configuration of multiple network interfaces to migrated VMs.

September 20, 2021

Migrate for Compute Engine now supports the deployment of migrated workloads to sole-tenant nodes. A sole-tenant node is a Compute Engine server that is dedicated to hosting only your project's VMs.

See Migrating individual VMs for more information on sole tenancy.

September 05, 2021

Added support for overriding the default license type to explicitly specify a license type of PAYG or BYOL.

See Configuring the target for a migrated VM for more information.

April 14, 2021

Google Cloud Console UI

End-to-end migration experience in Google Cloud Console including: Dashboard, Source inventory, Migrations managements, VM groups, and Targets.

To access the UI:

  1. Open the Migrate for Compute Engine page in the Google Cloud Console.

  2. In the upper-right corner, select Try the new version to open the Google Cloud Console to the 5.0 UI.

Migration primitives

Migration primitives controlling VM migration journey, which includes:

  • Replication - Initiate replication based migration, control periodical replication cycle schedule.

  • Test-Clone - Test a clone of migrating VM in Google Cloud with no disruptions on source VM to reduce migration risk.

  • Cut-Over - Cutting over to Google Cloud process with minimized downtime to migrating VM.

See VM Migration lifecycle for more.

VM groups

Group migration operations to enable you to manage and execute mass migration sprints.

See Mass migration with groups for more.

Seamless OS adaptation

Seamless OS adaptation of migrating VMs to prepare OS to run in Compute Engine (such as network settings) and deploy Compute Engine agents for seamless day 2 integrations with Compute Engine services.

See Adapting VMs to run on Google Cloud for more.

Compute Engine Targets

Migration to n Google Cloud target projects and flexible configuration of migrating VM target details (such as instance type, disk type, and network settings).

See Configuring the target for a migrated VM for more.

vSphere Source

Agentless migration of vSphere source environment utilizing Migrate Connector appliance deployed in source.

See On-premises VMware to Compute Engine migrations for more.

VM utilization reports

To help you determine the optimal settings for the Compute Engine target, Migrate for Compute Engine lets you create a source VM utilization report. This report displays information about resource allocation and utilization for the source VMs deployed on vCenter.

See Creating a source VM utilization report for more.