Procurement guy here. What SLAs should I demand in the migration contract?

Finally, someone mentions performance. Everyone's fixated on the data matching, but a perfectly accurate dataset is useless if your dashboard takes an hour to refresh. If the migration team builds the new tables with lousy indexes because they're just aiming for a row count, you'll be stuck with a technically correct, functionally broken system.

But calling it a "production-equivalent environment" is where the weasel room starts. You need to contractually define what that means: same compute tier, same indexing strategy, same load from concurrent users. Otherwise, their "equivalent" box is a stripped-down VM that tells you nothing about real-world lag.