Back to results for “Migration”
AWS › AWS Database Migration Service & Application Migration

What are the key considerations for validating data integrity and application performance after completing a large scale database or application migration?

Advanced

Answer

Post migration validation typically involves running automated row count and checksum comparisons between the source and target databases to confirm data integrity, performing thorough functional and performance testing of the migrated application under realistic load, closely monitoring the new environment using CloudWatch for any unexpected errors or performance regressions, and maintaining the ability to roll back to the original environment for a defined period in case unexpected issues surface only after real production traffic begins flowing to the new environment.
aws dms describe-table-statistics --replication-task-arn arn:aws:dms:us-east-1:123456789012:task:my-task
Real-world example A company completing a major database migration runs an automated row count and checksum validation script comparing the old and new databases before officially decommissioning the legacy system, catching a small data discrepancy that was then corrected before final cutover.

Common follow-ups: What tools are available to automate post migration data validation?;How long should an organization typically keep the old environment available as a rollback option?