[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-05 UTC。"],[],[],null,["# Migration overview\n\nThis section provides an overview of how to migrate your database to\nSpanner. The process to migrate to Spanner might vary\ndepending on factors like your source database, data size, downtime requirements,\napplication code complexity, sharding schema, custom functions or\ntransformations, and failover and replication strategies.\n\nA typical Spanner migration involves the following stages:\n\n1. [Assess your migration](/spanner/docs/assess-migration).\n2. [Migrate your schema](/spanner/docs/schema-migration).\n3. [Modify your application code](/spanner/docs/application-migration).\n4. [Optimize your schema and application performance](/spanner/docs/optimize-schema-performance).\n5. [Migrate your data](/spanner/docs/data-migration).\n6. [Validate the migration](/spanner/docs/data-validation).\n7. [Configure cutover and fallback mechanisms](/spanner/docs/cutover-fallback-mechanisms).\n\nDepending on the stage of the migration you're in, you\nmight need to consult your organization's network administrator, database\nadministrator, or application developers to complete that migration steps\noutlined.\n\nYou can use the previously described high-level migration stages if you want to\nmove a one-time dump into Spanner, or complete a large-scale\nproduction migration. Depending on your use case, what you do in each of the\nstages can change significantly.\n\nSource-specific migration guides\n--------------------------------\n\n- MySQL: [Migrate from MySQL to Spanner](/spanner/docs/migrating-mysql-to-spanner)."]]