Google Migrate to Containers
Google Migrate to Containers automates extracting applications from servers and virtual machines so they can run in containers without rewriting or re-archit…
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 workloads can come from VMware or Compute Engine VMs, and migrated applications can target Google Kubernetes Engine, GKE Autopilot clusters or Cloud Run. Supported types include Linux applications, IBM WebSphere, JBoss, Apache, Tomcat, WordPress and Windows IIS applications. The local CLI copies a source VM file system, analyzes it into a migration plan and generates deployment artifacts; it can optionally move data files to persistent volumes. Linux workloads can be migrated locally in offline mode, and the CLI can operate on a local network without downloading resources from the internet during runtime. Google recommends assessing workload fit before migration. A local machine needs Docker and several gigabytes of free storage, with the amount depending on the source file system and filters. 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.
Good
- Automates application extraction without rewriting or re-architecting.
- Targets GKE, GKE Autopilot and Cloud Run.
- Supports local Linux migration in offline mode.
- Migration has no charge.
Watch out
- Requires Docker and several gigabytes of local storage.
- Console UI, migctl and processing-cluster CRDs were discontinued.
- Other Google Cloud services are charged separately.
- Some Linux workloads are poor migration fits.
Who it suits
Migrate to Containers suits teams moving supported applications from VMware or Compute Engine VMs into containers on Google Cloud. It may fit users who can work with the local CLI and assess workload fit before migrating.
Verdict
Migrate to Containers offers a local CLI workflow for moving supported VM workloads into containers. Check workload compatibility and account for local requirements and charges for other Google Cloud services.
Plans and prices
From Google Migrate to Containers's own pricing page, checked 3 Oct 2026.
| Plan | Price | What it gives you |
|---|---|---|
| Migrate to Containers | Free | Other Google Cloud services used (compute, storage, networking, etc.) are charged separately · Any customer can use the tool · No charge for migrating workloads to Google Cloud |
The facts
Each one read from Google Migrate to Containers's own pages, with the date it was checked.
What it does
- 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.checked 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.checked 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.checked 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.checked 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.checked 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.checked 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.checked 3 Oct 2026
- Sources
- Workloads can be migrated from VMs running on VMware or Compute Engine.checked 3 Oct 2026
- Support
- All Google Cloud customers, including free-trial customers, receive Basic Support with documentation, community forums, billing assistance, and Active Assist.checked 3 Oct 2026
- Supported workloads
- Supported workload types include Linux-based applications, IBM WebSphere, JBoss, Apache, Tomcat, WordPress, and Windows IIS applications.checked 3 Oct 2026
- Targets
- Migrated applications can run on Google Kubernetes Engine, GKE Autopilot clusters, or Cloud Run.checked 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.checked 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.checked 3 Oct 2026
The company
- Company
- Google Inc. was officially born in August 1998, and Google's current headquarters is the Googleplex in Mountain View, California.checked 3 Oct 2026
- Founded
- 1998checked 28 Sep 2026
- Headquarters
- Mountain View, California, United Stateschecked 28 Sep 2026
Alternatives to Google Migrate to Containers
- 1
Amazon Database Migration Service
Free planWebAPI7.0Free plan - 2
AWS Mainframe Modernization
WebAPILinuxSelf-hosted6.9From $0.31 a month - 3
CAST Highlight
WebAPILinuxmacOS6.9From $6,800 a year - 4
ShareGate
WebAPISelf-hostedWindows6.7$5,995 one-time - 5
pgloader
Free planLinuxSelf-hosted6.6From €800 a month - 6
Device42
WebAPILinuxmacOS6.5