This document is the first of a series that guides you through migrating your virtual machines (VMs) from your source environment to Google Cloud by using Migrate for Compute Engine. Your source environment might be running in an on-premises environment, in a private hosting environment, or in another cloud provider.
This document provides an overview of Migrate for Compute Engine and what it's used for. It also contains important points for you to consider when planning a VM migration, and provides guidance about how to migrate VMs.
This document is part of a multi-part series about migrating to Google Cloud. If you're interested in an overview of the series, see Migration to Google Cloud: Choosing your migration path.
This document is part of a series:
- Migrating VMs with Migrate for Compute Engine: Getting started (this document)
- Migrating VMs with Migrate for Compute Engine: Building your foundation
- Migrating VMs with Migrate for Compute Engine: Migrating your VMs
- Migrating VMs with Migrate for Compute Engine: Best practices
- A VMware vSphere environment
- A Microsoft Azure VM environment
- An Amazon Elastic Compute Cloud (Amazon EC2) environment
- Physical servers and VMs running an operating system that Google Cloud supports
Migrate for Compute Engine lets you streamline your VM migration to Google Cloud. You don't have to spend effort in designing and implementing a reliable toolchain to manually evaluate how your VMs behave in Google Cloud, and then to manually migrate them. Migrate for Compute Engine accelerates your VM migration, saves you time, and lets you focus on improving your workloads.
This series assumes that you have read and are familiar with the following documents:
- Migration to Google Cloud: Getting started describes the general migration framework that you follow in this migration.
- Migrate for Compute Engine architecture describes the reference architecture of Migrate for Compute Engine.
- Migrate for Compute Engine migration workflows describes a typical VM migration journey with Migrate for Compute Engine.
Designing the migration to Google Cloud
To migrate your VMs from your source environment to Google Cloud, we recommend that you follow the framework described in the Migration to Google Cloud series.
The following diagram illustrates the path of your migration journey.
The framework illustrated in the preceding diagram has four phases:
- Assess. In this phase, you assess your source environment, assess the workloads that you want to migrate to Google Cloud, and assess which VMs support each workload.
- Plan. In this phase, you create the basic infrastructure for Migrate for Compute Engine, such as provisioning the resource hierarchy and setting up network access.
- Deploy. In this phase, you migrate the VMs from the source environment to Compute Engine.
- Optimize. In this phase, you begin to take advantage of the cloud technologies and capabilities.
Assessing the source environment and workloads
In the assess phase, you gather information about your source environment and the workloads that you want to migrate. Assessing your source environment and the workloads that you want to migrate is crucial to plan your migration and to rightsize the resources that you need for the migration and your target environment.
The process for assessing your source environment and workloads isn't unique for using Migrate for Compute Engine to migrate your VMs. For more information about how to assess your source environment, refer to Migration to Google Cloud: Assessing and discovering your workloads.
- Migrate for Compute Engine: Building your foundation.
- Explore reference architectures, diagrams, tutorials, and best practices about Google Cloud. Take a look at our Cloud Architecture Center.