Published 24 October 2026 · dotNewLABS
Saying a migration went well is not evidence. A proof report is: a short document showing what was compared, how, and what the results were. Here is what goes in it.
The simplest check and the first one to run. Every table or file should have a count in the old system and the same count in the new one, or a written reason for any difference such as duplicates removed.
For money, quantities and dates, compare sums, minimums and maximums. A count can match while amounts are wrong, so check key columns such as balances or charges.
Pick a sample that includes ordinary records, unusual ones and the oldest ones. Compare every field. Have a person who knows the data confirm a few by eye.
If the old system calculated something, such as a status or a fee, run the same cases through both and compare. Staff examples are the best test cases.
Some differences are intended: cleaned codes, merged duplicates, new formats. List each one with the reason. An unexplained difference is a defect until proven otherwise.
The proof report lists what was compared, the results, the differences and who approved them. The data owner signs, and the report is kept with the scripts so the check can be rerun.
Book a free 20-minute call about one app or data move: what it runs on, what's risky, and the shortest safe path forward. You keep a short written summary whether or not you hire us.
Book a free callOr email contact@dotnewlabs.ai