Migrate to Containers converts existing VM-based applications into containers that then run on Google Kubernetes Engine, GKE Autopilot clusters, GKE Enterprise, or Cloud Run. According to Google, getting there requires neither source code access nor rewriting the application.
What is Migrate to Containers?
Migrate to Containers is a migration tool for modernizing existing workloads. Instead of rebuilding applications, the tool extracts an image from the VM workload and constructs a Docker image and related artifacts from it. These can then run on a container platform and be integrated into a CI/CD pipeline, for example with Cloud Build.
As sources, the documentation lists VMs running in VMware on-premises environments or in Compute Engine. Target platforms are Google Kubernetes Engine, GKE Autopilot clusters, GKE Enterprise, and Cloud Run. An m2c CLI for Linux and Windows is available for preparing and running the migration.
Google explicitly distinguishes the tool from Migrate to VMs: a lift and shift into Compute Engine preserves the existing operational model and modernizes only the underlying infrastructure. Migrate to Containers instead targets the shift from VMs to containers and management through GKE or GKE Enterprise.
The documented benefits include greater density through lightweight containers, automatic operating system upgrades of nodes by GKE and GKE Enterprise, augmenting existing applications with platform services such as Cloud Service Mesh, and logging and monitoring via Cloud Logging and Cloud Monitoring without changing the application.
According to the pricing page, the solution itself is provided at no charge for migrations into Google Kubernetes Engine; you pay for the resources used, such as GKE clusters. Paid support is available through a Google Cloud Support subscription.
Core Features
- Automated containerization: Extraction of an image from the VM workload and construction of a Docker image plus related artifacts.
- Multiple target platforms: Run on GKE, GKE Autopilot clusters, GKE Enterprise, or Cloud Run.
- No source code access needed: Modernization without rewriting or rearchitecting the application.
- m2c CLI: Command-line tooling for Linux and Windows environments.
- CI/CD integration: Generated artifacts can be wired into build pipelines such as Cloud Build.
- Platform services available: After migration, capabilities such as Cloud Service Mesh, Cloud Logging, and Cloud Monitoring can be used.
Typical Use Cases
Modernizing a legacy application without refactoring
An application that has grown over years runs on VMs whose source code is only partly maintained. Migrate to Containers containerizes it and runs it on GKE without a rewrite.
Moving VMware workloads to GKE
A data center operator gradually moves VMs from a VMware environment into containers on GKE and reduces the number of self-operated operating systems.
Consolidating Compute Engine VMs
VMs already running in Google Cloud are containerized so that multiple workloads can run more densely on shared clusters.
Getting started with Cloud Run
For stateless applications, Cloud Run is chosen as the target to further reduce operational effort.
Establishing modern operational practices
After containerization, rolling updates, dynamic scaling, and self-healing are used through the container platform.
Benefits
- Modernization without rebuilding: Existing applications are containerized without touching the source code.
- Choice of target platform: GKE, GKE Autopilot, GKE Enterprise, and Cloud Run are available.
- Lower operational effort: Automatic node operating system upgrades move out of your own responsibility.
- Greater density: Containers require fewer compute and memory resources than full VMs.
- No additional tooling cost: For migrations into GKE, the pricing page states no additional charge for the solution.
Integration with innFactory
As a certified Google Cloud Partner, innFactory supports you with Migrate to Containers: assessing the container fit of your workloads, planning migration waves, building the GKE or Cloud Run target environment, and establishing CI/CD and operational processes after the migration.
Contact us for a consultation on Migrate to Containers and Google Cloud.
Typical Use Cases
Technical Specifications
Frequently Asked Questions
What is Migrate to Containers?
According to the Google documentation, Migrate to Containers is a tool to containerize existing VM-based applications to run on Google Kubernetes Engine, GKE Autopilot clusters, GKE Enterprise, or Cloud Run.
Do I have to rewrite my application?
No. Google explicitly states that modernization and management can be done without requiring access to source code, rewriting, or rearchitecting applications.
Which sources are supported?
The documentation lists VMs running in VMware on-premises environments or in Compute Engine. Refer to the official documentation for the currently supported source systems, as the scope can change.
What does Migrate to Containers cost?
According to the pricing page, the solution is provided at no charge for migrations into Google Kubernetes Engine. Costs arise for the resources used, such as GKE clusters. Paid support is available through a Google Cloud Support subscription.
How does Migrate to Containers differ from Migrate to VMs?
Migrate to VMs moves workloads unchanged into VM instances in Compute Engine - a classic lift and shift that preserves the existing operational model. Migrate to Containers goes a step further and moves workloads into containers that are then managed through GKE or GKE Enterprise.
What does the migration produce?
Google describes that Migrate to Containers extracts an image from the VM workload and constructs a Docker image and related artifacts. These can then be integrated into a CI/CD pipeline, for example with Cloud Build.
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of Google Cloud (official documentation). This page does not represent an offer by Google Cloud.
