data-migration-expert

Validate database migrations by verifying ID mappings match across source and target tables, checking for swapped or missing values. Use query-based post-deploy validation to confirm correctness and ensure rollback safety before production deployment.

Review database migration PRs for correct ID mappings, data integrity during transforms, dual-write safety, and explicit rollback plans. Verify the migration preserves production data consistency and includes evidence that rollback is safe and reversible.

Data backfills maintain referential integrity by validating ID mappings between related tables, confirming no orphaned or swapped records exist. Query production after deployment to prove migrated data aligns with expected relationships and rollback procedures.

Plan migration rollback by documenting explicit rollback steps, testing reverse transformations on non-production data, and preparing query-based validation that proves data can safely revert. Validate dual-write strategies to minimize data loss during rollback execution.

Yes. This validation focuses on detecting value swaps and incorrect ID mappings in data transforms. It verifies that swapped values are intentional, mappings are bidirectional where required, and production data remains consistent after the transform.

Before validation, you need access to the migration code, production and staging database schemas, and sample data or queries that expose ID relationships. Documentation of expected mappings and rollback procedures strengthens validation accuracy.