Data Migration Integrity Validator

A Data Migration Integrity Validator is an AI assistant built for one of the highest-stakes moments in a database's life: moving data from one system, schema, or platform to another. Migrations are notorious for introducing subtle problems, truncated text fields, silently dropped rows, incorrectly converted data types, broken relationships between tables, or character encoding issues that corrupt special characters. Because these problems often aren't visible until weeks after a migration, when someone finally queries the affected data, this assistant focuses on catching integrity issues at every stage of the migration process rather than after the fact. Working with this assistant typically starts with describing the source and target systems involved, such as moving from one database engine to another, consolidating multiple databases into one, or migrating to a new schema version. The assistant helps design a validation plan covering all three phases of migration: pre-migration checks that establish a clear baseline of the source data (row counts, checksums, key constraints, data type ranges), in-flight validation that confirms data transformation and loading logic is behaving as expected, and post-migration verification that systematically compares source and target to confirm nothing was lost, duplicated, or altered unexpectedly. It can generate row count comparisons, checksum-based verification queries, sampling strategies for spot-checking large datasets, and specific tests for known migration pitfalls like type conversion edge cases, NULL handling differences between systems, and timezone or date format mismatches. Expect the assistant to produce concrete validation scripts and queries, a clear migration validation checklist tailored to the specific systems involved, and a structured way to document and sign off on migration success. When discrepancies are found, it helps determine whether they reflect genuine data loss or corruption versus expected, intentional changes from the migration's transformation rules. This makes the assistant especially valuable for teams planning major platform migrations, database engine upgrades, cloud migrations, schema version upgrades, and mergers requiring data consolidation across previously separate systems. Typical users include database administrators, data engineers, and migration project leads who need confidence that a migration succeeded completely before decommissioning the old system. The assistant's focus is giving teams a rigorous, repeatable way to prove a migration was successful rather than relying on a quick spot-check and hoping nothing was missed.