The Architecture Center provides content resources across a wide variety of migration subjects and scenarios to help you migrate workloads, data, and processes to Google Cloud. These resources are designed to help you complete these kinds of migrations:
- From an on-premises environment
- From a private hosting environment
- From another cloud provider
- Across Google Cloud regions
A migration 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.
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. The Migrate to Google Cloud series helps you choose the best path to suit your migration needs by establishing a migration framework. It's important to establish a migration framework 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.
Migration resources in the Architecture Center
You can filter the following list of migration resources by typing a product name or a phrase that's in the resource title or description.
|
Build hybrid and multicloud architectures using Google Cloud Provides practical guidance on planning and architecting your hybrid and multi-cloud environments using Google Cloud. Products used: Cloud Load Balancing, Compute Engine, GKE Enterprise, Google Kubernetes Engine (GKE) |
|
Continuous data replication to Spanner using Striim How to migrate a MySQL database to Cloud Spanner using Striim. Products used: Cloud SQL, Cloud SQL for MySQL, Compute Engine, Spanner |
|
Database migration: Concepts and principles (Part 1) Introduces concepts, principles, terminology, and architecture of near-zero downtime database migration from on-premises or other cloud environments. Products used: Compute Engine, Spanner |
|
Decide the network design for your Google Cloud landing zone This document describes four common network designs for landing zones, and helps you choose the option that best meets your requirements. Products used: VPC Service Controls, Virtual Private Cloud |
|
Designing networks for migrating enterprise workloads: Architectural approaches This document introduces a series that describes networking and security architectures for enterprises that are migrating data center workloads to Google Cloud. These architectures emphasize advanced connectivity, zero-trust security principles, and... Products used: Cloud CDN, Cloud DNS, Cloud Interconnect, Cloud Intrusion Detection System (Cloud IDS), Cloud Load Balancing, Cloud NAT, Cloud Service Mesh, Cloud VPN, Google Cloud Armor, Identity-Aware Proxy, Network Connectivity Center, VPC Service Controls, Virtual Private Cloud |
|
Federate Google Cloud with Microsoft Entra ID (formerly Azure AD) Products used: Google Cloud Directory Sync |
|
File storage on Compute Engine Describes and compares options for file storage on Compute Engine. Products used: Compute Engine, Filestore |
|
Global deployment with Compute Engine and Spanner Learn how to architect a multi-tier application that runs on Compute Engine VMs and Spanner in a global topology on Google Cloud. Products used: Cloud Load Balancing, Cloud Storage, Compute Engine, Virtual Private Cloud |
|
Implement your Google Cloud landing zone network design This document provides steps and guidance to implement your chosen network design for your landing zone. Products used: Virtual Private Cloud |
|
Jump Start Solution: Load balanced managed VMs Deploy an autoscaling group of Compute Engine VMs with a load balancer as the frontend. |
|
Landing zone design in Google Cloud This series shows how to design and build a landing zone in Google Cloud, guiding you through high-level decisions about identity onboarding, resource hierarchy, network design, and security. |
|
Migrate across Google Cloud regions Start preparing your workloads and data for migration across Google Cloud regions. Products used: BigQuery, Bigtable, Cloud SQL, Cloud Storage, Compute Engine, Dataflow, Dataproc, Google Kubernetes Engine (GKE), Spanner |
|
Migrate containers to Google Cloud: Migrate from Kubernetes to GKE Describes how to design, implement, and validate a plan to migrate from Kubernetes to Google Kubernetes Engine (GKE). Products used: Google Kubernetes Engine (GKE) |
|
Describes how to design, implement, and validate a plan to migrate from AWS to Google Cloud. Products used: Cloud DNS, Cloud Domains, Cloud Firewall, Cloud Load Balancing, Cloud Storage, Cloud Storage, Compute Engine, VPC Service Controls |
|
Migrate from AWS to Google Cloud: Migrate from AWS Lambda to Cloud Run Describes how to design, implement, and validate a plan to migrate from AWS Lambda to Cloud Run. Products used: Cloud Run, Migration Center |
|
Migrate from AWS: Amazon EC2 to Compute Engine Describes how to design, implement, and validate a plan to migrate from Amazon EC2 to Compute Engine. Products used: Cloud DNS, Cloud Domains, Cloud Firewall, Cloud Load Balancing, Cloud Storage, Cloud Storage, Compute Engine, VPC Service Controls |
|
Migrate from AWS: Amazon S3 to Cloud Storage Describes how to design, implement, and validate a plan to migrate from Amazon S3 to Cloud Storage. Products used: Cloud DNS, Cloud Domains, Cloud Firewall, Cloud Load Balancing, Cloud Storage, Cloud Storage, Compute Engine, VPC Service Controls |
|
Migrate from AWS: Migrate from Amazon EKS to GKE Design, implement, and validate a plan to migrate from Amazon EKS to Google Kubernetes Engine. Products used: Cloud Storage, Compute Engine, Google Kubernetes Engine (GKE) |
|
Migrate to a Google Cloud VMware Engine platform Describes the VMware Engine blueprint, which deploys a platform for VM workloads. |
|
Helps you plan, design, and implement the process of migrating your application and infrastructure workloads to Google Cloud, including computing, database, and storage workloads. Products used: App Engine, Cloud Build, Cloud Data Fusion, Cloud Deployment Manager, Cloud Functions, Cloud Run, Cloud Storage, Container Registry, Data Catalog, Dataflow, Direct Peering, Google Kubernetes Engine (GKE), Transfer Appliance |
|
Migrating On-Premises Hadoop Infrastructure to Google Cloud Guidance on moving on-premises Hadoop workloads to Google Cloud... Products used: BigQuery, Cloud Storage, Dataproc |
|
Multi-regional deployment on Compute Engine Provides a reference architecture for a multi-tier application that runs on Compute Engine VMs in multiple regions and describes the design factors to consider when you build a multi-regional architecture. |
|
Overview of identity and access management Explores the general practice of identity and access management (generally referred to as IAM) and the individuals who are subject to it, including corporate identities, customer identities, and service identities. Products used: Cloud Identity, Identity and Access Management |
|
Regional deployment on Compute Engine Learn how to architect a multi-tier application that runs on Compute Engine VMs in multiple zones within a Google Cloud region. Products used: Cloud Load Balancing, Cloud Storage, Compute Engine, Virtual Private Cloud |
|
Single-zone deployment on Compute Engine Provides a reference architecture for a multi-tier application that runs on Compute Engine VMs in a single-zone region and describes the design factors to consider when you build a single-zone architecture. |
|
Use RIOT Live Migration to migrate to Redis Enterprise Cloud Describes an architecture to migrate from Redis-compatible sources to fully managed Redis Enterprise Cloud in Google Cloud using RIOT Live Migration service. Products used: Compute Engine |