A reordered export is difficult to review as a line-by-line diff. Start with identity: which stable key refers to the same business record in both files? Treat the key as text so that leading zeros survive. Do not pick a display name simply because it looks readable.
Run a concrete local check
- Open ExportCheck and choose Try example data.
- The baseline uses record_id, name, plan and monthly_amount; the new export uses customer_id, display_name, tier and amount.
- Review the explicit mappings. Amount is a numeric comparison; IDs remain text. Normalization is opt-in.
- The example contains three unchanged key groups, one changed group, one new key, one duplicate-key group, one blank-key entry and one invalid numeric group.
These counts refer to this synthetic fixture. They are not a statement about your exports. The duplicate group is excluded from automatic matching, and USD 29 is flagged rather than guessed to be a plain decimal.
Separate differences from decisions
A changed value can be intentional. Give each exception an owner, a disposition and an evidence reference. Record the source/target snapshot timing so that a later update is not mistaken for a failed transfer. Column mappings should include intentionally omitted fields; comparing only common columns cannot establish that all required fields arrived.
Keep the result repeatable
The browser tool can save mappings and rules without input rows. The download runner adds composite keys, multiple report formats and exit codes. Store reports only in approved locations: reports can contain input values even though the utility itself makes no input-upload requests.
Use MigrationReady to record your review. Its statuses are assertions you enter, not an automated migration certification. A count match or a completed worksheet does not establish that every value is correct.
Know what this example does not check
The browser accepts CSV/TSV, not XLSX. It does not connect to a database, run a transfer or approve a rollback. Review ambiguous keys, omitted columns and post-snapshot updates. Recovery needs a separate authorized rehearsal on an appropriate environment.