Stay organized with collections
Save and categorize content based on your preferences.
Last reviewed 2024-12-08 UTC
This document series helps you prepare for migrating your workloads and data
across Google Cloud regions. In this series, you learn how to design
reliable, single-region environments, and how to set up security and compliance
controls to help ensure that your workloads and data stay inside specific
Google Cloud regions. This series also provides guidance on how to expand
your environment to multiple regions. This series is useful if you're planning
to do any of these actions, or if you're evaluating the opportunity to do so in
the future and want to explore what it might look like.
This series assumes that you have read and are familiar with
Migrate to Google Cloud: Get started,
which describes the general migration framework used in this series. This series
is also part of a larger set of migration content. For an overview of all
related migration content, see
Migration resources.
Use the following list to help you get started with the documents in this
series and with related migration content:
Architecting your environments for reliability. When designing your
Google Cloud environments, there are several architectural choices to
make, including how to distribute resources across Google Cloud
regions and zones. For more information about how to design your
Google Cloud environments, and about how to design reliable
single-region environments, refer to
Design resilient single-region environments on Google Cloud.
Preparing for and migrating across Google Cloud regions.
Preparing for a migration across Google Cloud regions helps you avoid
potential issues during such a migration, and also reduces the
time and effort required to complete the migration. For example, you might
want to prepare for a future migration to another region because you don't
yet know if a particular region would be the best fit for your environment.
Or you might prepare for a migration because you anticipate that your
requirements about the preferred region might change in the future. You
might even prepare for a migration because you're considering a migration
to a soon-to-be-opened region.
The guidance in this series is also useful if you didn't plan in advance for
a migration across regions or for an expansion to multiple regions. In this
case, you might need to spend additional effort to prepare your
infrastructure, workloads, and data for the migration across regions and for
the expansion to multiple regions.
For more information about preparing for a migration across
Google Cloud regions, see the following documents:
Setting up boundaries, and security and compliance controls to ensure
that your workloads and data stay inside certain Google Cloud
regions. You might have to comply with security and regulatory
requirements so that your workloads and data can only reside in specific
Google Cloud regions. If you have this compliance requirement, you
might need to implement boundaries, controls, and auditing to ensure
locality, sovereignty, privacy, and confidentiality on top of the
guarantees that Google Cloud offers.
For example, you might need to make your environment compliant with
regulations and security requirements that mandate certain workloads and
data never leave a specific region residing in a particular political,
administrative, or state entity.
Minimizing the costs of your single- and multi-region environments,
and of migrations across Google Cloud regions. As your environments
and your Google Cloud footprint grow, you might consider implementing
mechanisms and processes to control and reduce the costs that are
associated with your environments and your migrations across regions. For
example, you can provision resources in specific regions, optimize network
traffic patterns, streamline and automate processes, and automatically
scale resources with demand. For more information about reducing costs,
refer to
Migrate to Google Cloud: Minimize costs.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-12-08 UTC."],[[["\u003cp\u003eThis document series guides you through preparing for and executing the migration of workloads and data across Google Cloud regions.\u003c/p\u003e\n"],["\u003cp\u003eThe series covers how to design reliable, single-region environments and set up security and compliance controls to keep data within specific Google Cloud regions.\u003c/p\u003e\n"],["\u003cp\u003eYou will learn how to prepare for future migrations and how to manage migrations even if not planned in advance.\u003c/p\u003e\n"],["\u003cp\u003eThis content will guide you on how to minimize costs associated with single and multi-region environments, as well as migrations across regions.\u003c/p\u003e\n"],["\u003cp\u003eThe document series helps you with architectural decisions, such as distributing resources across Google Cloud regions and zones.\u003c/p\u003e\n"]]],[],null,["# Migrate across Google Cloud regions: Get started\n\nThis document series helps you prepare for migrating your workloads and data\nacross Google Cloud [regions](/docs/geography-and-regions#regions_and_zones). In this series, you learn how to design\nreliable, single-region environments, and how to set up security and compliance\ncontrols to help ensure that your workloads and data stay inside specific\nGoogle Cloud regions. This series also provides guidance on how to expand\nyour environment to multiple regions. This series is useful if you're planning\nto do any of these actions, or if you're evaluating the opportunity to do so in\nthe future and want to explore what it might look like.\n\nThis document is part of the following series:\n\n- Get started (this document)\n- [Design resilient single-region environments on Google Cloud](/architecture/migrate-across-regions/design-resilient-single-region-environments)\n- [Architect your workloads](/architecture/migrate-across-regions/architect-workloads)\n- [Prepare data and batch workloads for the migration](/architecture/migrate-across-regions/prepare-data-and-batch-workloads)\n\nThis series assumes that you have read and are familiar with\n[Migrate to Google Cloud: Get started](/architecture/migration-to-gcp-getting-started),\nwhich describes the general migration framework used in this series. This series\nis also part of a larger set of migration content. For an overview of all\nrelated migration content, see\n[Migration resources](/architecture/migrations).\n\nUse the following list to help you get started with the documents in this\nseries and with related migration content:\n\n- **Architecting your environments for reliability.** When designing your Google Cloud environments, there are several architectural choices to make, including how to distribute resources across Google Cloud regions and zones. For more information about how to design your Google Cloud environments, and about how to design reliable single-region environments, refer to [Design resilient single-region environments on Google Cloud](/architecture/migrate-across-regions/design-resilient-single-region-environments).\n- **Preparing for and migrating across Google Cloud regions**.\n Preparing for a migration across Google Cloud regions helps you avoid\n potential issues during such a migration, and also reduces the\n time and effort required to complete the migration. For example, you might\n want to prepare for a future migration to another region because you don't\n yet know if a particular region would be the best fit for your environment.\n Or you might prepare for a migration because you anticipate that your\n requirements about the preferred region might change in the future. You\n might even prepare for a migration because you're considering a migration\n to a soon-to-be-opened region.\n\n The guidance in this series is also useful if you didn't plan in advance for\n a migration across regions or for an expansion to multiple regions. In this\n case, you might need to spend additional effort to prepare your\n infrastructure, workloads, and data for the migration across regions and for\n the expansion to multiple regions.\n\n For more information about preparing for a migration across\n Google Cloud regions, see the following documents:\n - [Design resilient single-region environments](/architecture/migrate-across-regions/design-resilient-single-region-environments)\n - [Prepare data and batch workloads for migration across regions](/architecture/migrate-across-regions/prepare-data-and-batch-workloads)\n- **Setting up boundaries, and security and compliance controls to ensure\n that your workloads and data stay inside certain Google Cloud\n regions** . You might have to comply with security and regulatory\n requirements so that your workloads and data can only reside in specific\n Google Cloud regions. If you have this compliance requirement, you\n might need to implement boundaries, controls, and auditing to ensure\n locality, sovereignty, privacy, and confidentiality on top of the\n [guarantees that Google Cloud offers](/security).\n For example, you might need to make your environment compliant with\n regulations and security requirements that mandate certain workloads and\n data never leave a specific region residing in a particular political,\n administrative, or state entity.\n\n- **Minimizing the costs of your single- and multi-region environments,\n and of migrations across Google Cloud regions** . As your environments\n and your Google Cloud footprint grow, you might consider implementing\n mechanisms and processes to control and reduce the costs that are\n associated with your environments and your migrations across regions. For\n example, you can provision resources in specific regions, optimize network\n traffic patterns, streamline and automate processes, and automatically\n scale resources with demand. For more information about reducing costs,\n refer to\n [Migrate to Google Cloud: Minimize costs](/architecture/migration-to-google-cloud-minimize-costs).\n\nWhat's next\n-----------\n\n- Learn how to [design resilient single-region environments on Google Cloud](/architecture/migrate-across-regions/design-resilient-single-region-environments).\n- Learn how to [prepare data and batch workloads for the migration](/architecture/migrate-across-regions/prepare-data-and-batch-workloads).\n- Learn how to [minimize costs](/architecture/migration-to-google-cloud-minimize-costs) of your Google Cloud environment and your migration across regions.\n- Read [an in-depth analysis of deployment archetypes for cloud applications](/architecture/deployment-archetypes).\n- Learn about the migration framework by reading [Migrate to Google Cloud: Get started](/architecture/migration-to-gcp-getting-started).\n- Learn when to [find help for your migrations](/architecture/migration-to-gcp-getting-started#finding_help).\n- For more reference architectures, diagrams, and best practices, explore the [Cloud Architecture Center](/architecture).\n\nContributors\n------------\n\nAuthor: [Marco Ferrari](https://www.linkedin.com/in/ferrarimark) \\| Cloud Solutions Architect\n\nOther contributor: [Lee Gates](https://www.linkedin.com/in/gatesl) \\| Group Product Manager"]]
