This document presents the Migration to Google Cloud series and helps you to understand how each piece of the series relates to other documents. This document is an overview for the following series:
- Migration to Google Cloud
- Migrating VMs with Migrate to Virtual Machines
- Migrating VMs to containers with Migrate to Containers
- Migrating containers to Google Cloud
These series are for anyone who is intending to migrate virtual machines (VMs), containers, databases, or storage to Google Cloud. This document is useful for the following migration scenarios:
- From an on-premises environment
- From a private hosting environment
- From another cloud provider to Google Cloud
As part of your migration journey, you have to make decisions that are dependent on the environment, the workloads, and the infrastructure that you're migrating to Google Cloud or to a hybrid cloud environment. These documents help you choose the best path to suit your migration needs in the following ways:
- Establish a framework to design and run your migration journey by using the Migration to Google Cloud series.
- Use this framework as a baseline against which you can assess your migration progress.
- Give guidance that's specific to a particular environment or use case by building on the Migration to Google Cloud framework, such as Migrating VMs with Migrate to VMs, Migrating containers to Google Cloud, and Migrating VMs to containers with Migrate to Containers.
Benefits of establishing a migration framework
Establishing a migration framework is important because migration can be a repeatable task. For example, if you initially migrate your VMs to Google Cloud, you might also consider moving other data and workloads to Google Cloud. Establishing a general framework that can be applied to different workloads can make future migrations easier for you.
The following diagram illustrates the migration phases:
During each migration step, you follow the phases defined in Migration to Google Cloud: Getting started:
- Assessing and discovering your workloads.
- Planning and building a foundation.
- Deploying your workloads.
- Optimizing your environment and workloads.
This journey isn't unique to Google Cloud. Moving from one environment to another is a challenging task, so you need to plan and execute your migration carefully. No matter what you're migrating—whether apps, VMs, or containers—you need to complete tasks such as creating an inventory, establishing user and service identities, deploying your workloads, and optimizing for performance and scalability.
Design of the series
To design and plan the Migration to Google Cloud, the Migrating VMs with Migrate to VMs, the Migrating containers to Google Cloud, and the Migrating VMs to containers with Migrate to Containers series, we used software design paradigms and strategies that are common in object-oriented programming (OOP).
You can use the concepts of OOP to think about the recommendations in each of the series. This document is like your software documentation when you're developing an application: it guides you through your journey, offering direction along the way.
The following simplified UML class diagram illustrates the relationships between the documents in the Migration to Google Cloud, the Migrating your VMs with Migrate to VMs, and the Migrating containers to Google Cloud series:
In the preceding diagram, the series maps to a UML class diagram in the following ways.
The Migration to Google Cloud series includes the following documents:
Migration to Google Cloud: Choosing your migration path (this document) helps you choose the best migration options for your components.
Migration to Google Cloud: Getting started sets up the framework for the other migration series and teaches you about migration concepts, but doesn't help you perform an actual migration. All other documents in the series are a direct extension of that document.
The documents in this series describe each phase of the migration to Google Cloud in detail. The concepts in these documents apply to the migration of various assets, including data, apps, VMs, and containers.
The concepts that are explored throughout the Migration to Google Cloud series are extended and applied to the following series to give more prescriptive guidance for specific use cases and environments:
Migrating VMs with Migrate to VMs
Migrating containers to Google Cloud
- Getting started
- Migrating from Kubernetes to GKE
- Migrating from OpenShift to Anthos
- Migrating OpenShift projects to Anthos
- Migrating OpenShift security context constraints to Anthos
- Migrating to a multi-cluster GKE environment
- Migrating to a multi-cluster GKE environment with Multi Cluster Ingress and Multi Cluster Service Discovery
Migrating VMs to containers with Migrate to Containers
The logic that is applied in the diagram can be extended to other workloads. For example, by using the assessment, planning, deployment, and optimization phases, you can modernize your CI/CD pipelines when you migrate them to Google Cloud.
- Start designing your migration to Google Cloud.
- Migrate your VMs with Migrate to VMs.
- Migrate your containerized workloads to Google Cloud.
- Migrate your VMs to containers with Migrate to Containers.
- Explore reference architectures, diagrams, and best practices about Google Cloud. Take a look at our Cloud Architecture Center.