Google Migrate to Containers
cloud.google.com
- Free plan
- Windows
- Linux
- Self-hosted
What Google Migrate to Containers is
Google Migrate to Containers automates extracting applications from servers and virtual machines so they can run in 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 applications. The local CLI copies a VM file system, analyzes it into a migration plan and generates deployment artifacts; it can also move data files to persistent volumes. Linux workloads can be migrated locally in offline mode, and the CLI can work on a local network without downloading runtime resources from the internet. A local machine needs Docker and several gigabytes of free storage, with the amount depending on the source file system and filters. Google recommends assessing workload fit first. Windows workloads need IIS 7 or later; Linux workloads with certain database, driver, hardware or licensing dependencies are poor fits. The console UI, migctl and processing-cluster CRDs were discontinued in May 2024; Google directs users to the local CLI. Migration is free, but other Google Cloud services used are charged separately.
Who it suits
Migrate to Containers suits teams moving supported applications from VMware or Compute Engine VMs to Google Kubernetes Engine, GKE Autopilot or Cloud Run. It is less suited to workloads with the listed Linux hardware, database or licensing dependencies.
Good to know, and what to watch
- Migration itself has no charge.
- Supports Linux, Windows IIS and named application workloads.
- CLI can migrate Linux workloads in offline mode.
- Can generate deployment artifacts from VM filesystems.
- Targets include GKE, GKE Autopilot and Cloud Run.
- Other Google Cloud services are charged separately.
- Local machine requires Docker and free storage.
- Some hardware- or database-dependent Linux workloads are poor fits.
- Console UI, migctl and processing-cluster CRDs were discontinued.
Plans
Every plan and priceMigrate to Containers
Free plan
The verdict
Migrate to Containers provides a CLI workflow for extracting supported VM workloads and generating container deployment artifacts. Review workload fit and local requirements, and account separately for any Google Cloud services used.
What the maker publishes
- 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. source
- Cloud Code integration
- The Cloud Code integration supports migrating applications from VMs to GKE containers directly in Visual Studio using a Linux machine. source
- Company
- Google Inc. was officially born in August 1998, and Google's current headquarters is the Googleplex in Mountain View, California. source
- 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. source
- Founded
- 1998 source
- Headquarters
- Mountain View, California, United States source
- 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. source
- 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. source
- Purpose
- Migrate to Containers automates extracting applications from servers and VMs so they can run in containers without rewriting or re-architecting the apps. source
- Security compliance
- Google Cloud's ISO/IEC 27001 page lists Migrate to Containers among offerings in scope for the Google Cloud Services ISMS certification. source
- Sources
- Workloads can be migrated from VMs running on VMware or Compute Engine. source
- Support
- All Google Cloud customers, including free-trial customers, receive Basic Support with documentation, community forums, billing assistance, and Active Assist. source
- Supported workloads
- Supported workload types include Linux-based applications, IBM WebSphere, JBoss, Apache, Tomcat, WordPress, and Windows IIS applications. source
- Targets
- Migrated applications can run on Google Kubernetes Engine, GKE Autopilot clusters, or Cloud Run. source
- 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. source
- 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. source
Checked against the maker's pages on 3 Oct 2026.