- Home
- Cloud Migration Tools
- Google Migrate to Containers
Google Migrate to Containers
Mountain View, California, United States
What it is
Google Migrate to Containers moves applications from virtual machines into containers without rewriting or re-architecting them. Source VMs can run on VMware or Compute Engine, and migrated applications can target Google Kubernetes Engine, GKE Autopilot clusters, or Cloud Run. Supported workloads include Linux applications, IBM WebSphere, JBoss, Apache, Tomcat, WordPress, and Windows IIS. The local CLI copies a VM file system, analyzes it into a migration plan, and creates deployment artifacts; it can also move data files to persistent volumes. Linux workloads can be migrated offline, and the CLI can work on a local network without downloading resources from the internet at runtime. A local machine needs Docker and several gigabytes of free storage, depending on the source file system and filters. Google recommends assessing workload fit before migration; certain Linux workloads with high-performance or large in-memory databases, special kernel drivers, hardware dependencies, or hardware-ID-bound licenses are poor fits. Windows workloads need IIS 7 or later. The console UI, migctl, and processing-cluster CRDs were discontinued in May 2024, and Google directs users to the local CLI. Migration has no charge, but other Google Cloud services used are billed separately.
For and against
For
- Migrates applications without rewriting or re-architecting them.
- Targets GKE, GKE Autopilot, or Cloud Run.
- CLI can generate deployment artifacts and migration plans.
- Linux workloads support local offline migration.
- Migration has no charge.
Against
- Other Google Cloud services are charged separately.
- Local use requires Docker and several gigabytes of free storage.
- Some Linux workloads are listed as poor migration fits.
- The console UI and other named tools were discontinued in May 2024.
The verdict
Google Migrate to Containers offers a local CLI workflow for extracting supported VM workloads and preparing them for container deployment. Review workload fit and local requirements first, and account for charges from other Google Cloud services.
Who it suits
This tool suits teams moving supported workloads from VMware or Compute Engine VMs into containers on Google Cloud destinations. It is less suited to workloads with the listed database, driver, hardware, or license constraints.
Plans and prices
Migrate to Containers
Other Google Cloud services used (compute, storage, networking, etc.) are charged separately · Any customer can use the tool
Read 3 Oct 2026 · cloud.google.com
On the record
- 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.docs.cloud.google.com · read 3 Oct 2026
- Cloud Code integration
- The Cloud Code integration supports migrating applications from VMs to GKE containers directly in Visual Studio using a Linux machine.docs.cloud.google.com · read 3 Oct 2026
- Company
- Google Inc. was officially born in August 1998, and Google's current headquarters is the Googleplex in Mountain View, California.about.google · read 3 Oct 2026
- 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.docs.cloud.google.com · read 3 Oct 2026
- 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.docs.cloud.google.com · read 3 Oct 2026
- 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.docs.cloud.google.com · read 3 Oct 2026
- Purpose
- Migrate to Containers automates extracting applications from servers and VMs so they can run in containers without rewriting or re-architecting the apps.cloud.google.com · read 3 Oct 2026
- Security compliance
- Google Cloud's ISO/IEC 27001 page lists Migrate to Containers among offerings in scope for the Google Cloud Services ISMS certification.cloud.google.com · read 3 Oct 2026
- Sources
- Workloads can be migrated from VMs running on VMware or Compute Engine.docs.cloud.google.com · read 3 Oct 2026
- Support
- All Google Cloud customers, including free-trial customers, receive Basic Support with documentation, community forums, billing assistance, and Active Assist.cloud.google.com · read 3 Oct 2026
- Supported workloads
- Supported workload types include Linux-based applications, IBM WebSphere, JBoss, Apache, Tomcat, WordPress, and Windows IIS applications.docs.cloud.google.com · read 3 Oct 2026
- Targets
- Migrated applications can run on Google Kubernetes Engine, GKE Autopilot clusters, or Cloud Run.docs.cloud.google.com · read 3 Oct 2026
- 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.cloud.google.com · read 3 Oct 2026
- 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.docs.cloud.google.com · read 3 Oct 2026
