Google Migrate to Containers
cloud.google.com
What it is
Google Migrate to Containers is a free, self-hosted tool for moving applications from virtual machines or servers into containers without rewriting or re-architecting them. Its local CLI copies a source VM file system, analyzes it, creates a migration plan, and generates deployment artifacts. It can optionally move data files to persistent volumes. Sources include VMware and Compute Engine VMs, and destinations include Google Kubernetes Engine, GKE Autopilot clusters, and Cloud Run. Supported workloads include Linux applications, IBM WebSphere, JBoss, Apache, Tomcat, WordPress, and Windows IIS applications. Linux workloads can be handled locally in offline mode or on a local network without runtime internet downloads. A local machine needs Docker and several gigabytes of storage. Google recommends assessing workload fit first. The console UI, migctl, and processing-cluster CRDs were discontinued in May 2024; Google directs users to the local CLI. Migration has no charge, while other Google Cloud services cost separately.
Spec sheet
- Purpose
- Migrate to Containers automates extracting applications from servers and VMs so they can run in containers without rewriting or re-architecting the apps.Read 3 Oct 2026 · cloud.google.com
- Support
- All Google Cloud customers, including free-trial customers, receive Basic Support with documentation, community forums, billing assistance, and Active Assist.Read 3 Oct 2026 · cloud.google.com
- Headquarters
- Mountain View, California, United StatesRead 28 Sep 2026 · cloud.google.com
- Founded
- 1998Read 28 Sep 2026 · cloud.google.com
- Company
- Google Inc. was officially born in August 1998, and Google's current headquarters is the Googleplex in Mountain View, California.Read 3 Oct 2026 · about.google
- CLI workflow
- The CLI copies a source VM file system, analyzes it into a migration plan, generates deployment artifacts, and can optionally migrate data files to persistent volumes.Read 3 Oct 2026 · docs.cloud.google.com
- Cloud Code integration
- The Cloud Code integration supports migrating applications from VMs to GKE containers directly in Visual Studio using a Linux machine.Read 3 Oct 2026 · docs.cloud.google.com
- Fit assessment
- Google recommends fit assessment before migration, and its documentation describes the Migration Center discovery client CLI as a tool to assess whether a VM workload fits migration to a container.Read 3 Oct 2026 · docs.cloud.google.com
- Local requirements
- The local machine needs Docker and several GB of free storage, with required storage depending on the source file system size and applied filters.Read 3 Oct 2026 · docs.cloud.google.com
- Offline mode
- The CLI can migrate Linux-based workloads locally in offline mode and can work on a local network without pulling resources from the internet during runtime.Read 3 Oct 2026 · docs.cloud.google.com
- Security compliance
- Google Cloud's ISO/IEC 27001 page lists Migrate to Containers among offerings in scope for the Google Cloud Services ISMS certification.Read 3 Oct 2026 · cloud.google.com
- Sources
- Workloads can be migrated from VMs running on VMware or Compute Engine.Read 3 Oct 2026 · docs.cloud.google.com
- Supported workloads
- Supported workload types include Linux-based applications, IBM WebSphere, JBoss, Apache, Tomcat, WordPress, and Windows IIS applications.Read 3 Oct 2026 · docs.cloud.google.com
- Targets
- Migrated applications can run on Google Kubernetes Engine, GKE Autopilot clusters, or Cloud Run.Read 3 Oct 2026 · docs.cloud.google.com
- Tool availability
- The product's console UI, migctl, and processing-cluster CRDs were discontinued in May 2024; Google directs users to use the CLI on a local machine.Read 3 Oct 2026 · cloud.google.com
- Workload limits
- Windows workloads need IIS 7 or later; Linux workloads with high-performance or large in-memory databases, special kernel drivers, hardware dependencies, or hardware-ID-bound licenses are listed as poor fits.Read 3 Oct 2026 · docs.cloud.google.com
Plans and prices
Strong points and limits
Strong points
- Free migration tool
- Supports VMware and Compute Engine sources
- Targets GKE, GKE Autopilot, and Cloud Run
- Offline Linux migration available
- Includes workload discovery and assessment guidance
Limits
- Windows workloads require IIS 7 or later
- Some database and hardware-dependent workloads fit poorly
- Docker and several GB of local storage required
- Former console tools were discontinued in May 2024
Who it suits
It suits teams moving supported workloads from VMware or Compute Engine VMs into Google container platforms. It is also suited to operators who need offline or local-network Linux migration.
Verdict
Google Migrate to Containers provides a no-charge CLI workflow for extracting supported VM workloads into deployable containers. Its fit limits and local requirements should be checked before migration, and users must use the local CLI rather than discontinued console components.
Where Specifiction places it
- Cloud Migration Tools#10 of 327.9