Migration overview

This section provides an overview of how to migrate your database toSpanner. The process to migrate to Spanner might varydepending on factors like your source database, data size, downtime requirements,application code complexity, sharding schema, custom functions ortransformations, 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, youmight need to consult your organization's network administrator, databaseadministrator, or application developers to complete that migration stepsoutlined.

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

Source-specific migration guides

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

Last updated 2025-12-15 UTC.