Cloud Renames Contribute
RenamedCompute, Security & InfraGoogle Cloud

Migrate for Compute Engine Migrate to Virtual Machines

Legacy names Migrate for Compute Engine, Velostrata

Agentless server and VM migration service for moving workloads from on-premises or other clouds to Compute Engine.

Open in interactive timeline ↗All Google Cloud renamesHome

Naming timeline

  1. Velostrata

    · Google Cloud Acquisition

    Streaming VM migration technology acquired by Google Cloud.

  2. Migrate for Compute Engine

    · v4.8 Rebrand

    Rebranded from Velostrata to Migrate for Compute Engine (M4CE).

  3. Migrate to Virtual MachinesCurrent name

    · v5.0 Architecture & Rename

    Renamed product to Migrate to Virtual Machines (M2VM) with cloud-native vmmigration.googleapis.com control plane.

What is Migrate for Compute Engine called now?

Migrate for Compute Engine is now called Migrate to Virtual Machines, with the latest change on 5 July 2022 (v5.0 Architecture & Rename). Earlier names covered by this entry also include Velostrata. Agentless server and VM migration service for moving workloads from on-premises or other clouds to Compute Engine. Only the customer-facing name changed; the underlying technical identifiers remain backward compatible.

Also known as

  • Migrate to Compute Engine
  • M2VM
  • M4CE

Technical identifiers

Technical identifiers unchanged. Only the customer-facing product name changed; the APIs, CLI commands, IAM roles and Terraform resources below keep their legacy identifiers for backward compatibility.

REST / gRPC APIsvmmigration.googleapis.com
gcloud / CLI Commandsgcloud migration vms
IAM Predefined Rolesroles/vmmigration.*
Terraform Resourcesgoogle_vm_migration_source google_vm_migration_migrating_vm

Uses VM Migration API (vmmigration.googleapis.com); legacy Velostrata / M4CE 4.x appliance architecture was retired in favor of v5.0.

Notes & disambiguation

  • Originated from Google Cloud's July 2018 acquisition of Velostrata, rebranded to Migrate for Compute Engine in November 2019 (v4.8), and renamed to Migrate to Virtual Machines on July 5, 2022 with v5.0.
  • Documentation metadata still cross-references '(Migrate to Compute Engine)' and '(formerly Migrate for Compute Engine)' for search continuity.

Sources & official documentation

Catalog last updated . Spotted an error? Suggest an edit