Migration overview

This section provides an overview of how to migrate your database to Spanner. The process to migrate to Spanner might vary depending on factors like your source database, data size, downtime requirements, application code complexity, sharding schema, custom functions or transformations, and failover and replication strategies.

A typical Spanner migration involves the following stages:

  1. Assess your migration.
  2. Migrate your schema.
  3. Modify your application code.
  4. Optimize your schema and application performance.
  5. Migrate your data.
  6. Validate the migration.
  7. Configure cutover and fallback mechanisms.

Depending on the stage of the migration you're in, you might need to consult your organization's network administrator, database administrator, or application developers to complete that migration steps outlined.

You can use the previously described high-level migration stages if you want to move a one-time dump into Spanner, or complete a large-scale production migration. Depending on your use case, what you do in each of the stages can change significantly.

Source-specific migration guides

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025年11月24日 UTC.