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.
You can use The high-level migration stages offered
A typical Spanner migration involves the following stages:
- Assess your migration.
- Migrate your schema.
- Modify your application code.
- Optimize your schema and application performance.
- Migrate your data.
- Validate the migration.
- 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
- MySQL: Migrate from MySQL to Spanner.