Migrate an application
Inventory the application
Section titled “Inventory the application”List tables, constraints, indexes, functions, extensions, triggers and migration tools. Record how clients handle transactions, parameters, errors and returned types.
Test compatibility
Section titled “Test compatibility”A compatible driver does not imply complete compatibility with another database. Run representative SQL and schema changes against the release you plan to deploy. Check feature limits and schema transactions.
Move a sample first
Section titled “Move a sample first”Create the destination schema explicitly. Load a small sample, verify types and values, and test the application’s reads and writes. Import and export.
Plan cutover
Section titled “Plan cutover”Choose a maintenance or synchronization strategy appropriate to the application. Verify counts, reconcile writes that occurred during the move, and preserve a rollback path. Do not assume cross-database atomic commits.
Verify after cutover
Section titled “Verify after cutover”Check errors, latency, permissions, background jobs and recovery. Keep the previous environment available according to your rollback plan until the migration is accepted.
Related
Section titled “Related”This site uses Google Analytics cookies to count visits. Privacy · License