Local migration workbench
Check the data before the next consumer depends on it.
Matching row counts are a starting point. Compare complete business keys, exact values and declared relationships with the same reference engine used by the downloadable CLI.
Free. No account or email gate. Browser checks are limited to 5 MB and 15 seconds; the CLI supports the documented larger input limits.
Compare supplied JSON snapshots.
Try a synthetic control, or select your own declared audit input. Your file is processed in a browser worker; it is not uploaded, saved on this site or added to analytics. Closing or clearing this tool discards its in-memory input and report.
Use the audit input schema. A pair of arbitrary JSON files needs explicit keys, field mappings and relationship rules before it can be compared.
Make the scope explicit.
Record the source and target capture boundaries, business keys, field rules and required parent populations. A clean supplied-scope result can still omit a source table, a historical period or an undeclared business rule.
Read the CLI and input guideCarry the evidence into implementation.
Use the CLI handoff command to export an implementation brief and hashes. Source completeness, live consumer behavior, access, cutover and operating acceptance need evidence from their actual owners.
Choose a commerce or merger kit