Prove every record made it across the migration.
Export a source-system snapshot and a target-system snapshot as CSV or XLSX. Match records by a stable ID, compare the fields that matter, and get a reviewable list of missing, unexpected, changed, duplicated, and invalid records.
File-based validation; spreadsheet contents stay in your browser.
Source A · legacy export
legacy-customers.csv
| Customer ID | Balance |
|---|---|
| C-201 | 100.00 |
| C-202 | 50.00 |
| C-204 | 60.00 |
| C-204 | 60.00 |
| C-205 | 75.00 |
Source B · target export
new-system-customers.csv
| Customer ID | Balance |
|---|---|
| C-201 | 100.00 |
| C-203 | 80.00 |
| C-204 | 60.00 |
| C-205 | 78.00 |
Rule: Key: Customer ID · Compare: Balance (numeric, exact)
- C-201
- Matched
- C-202
- Only A · missing from target
- C-203
- Only B · unexpected in target
- C-204
- Duplicate or ambiguous
- C-205
- Balance mismatch
Completeness is more than a row count.
Two files can have the same number of rows yet contain different customers. MatchDock asks whether each source record has one corresponding target record, then whether the compared values agree. Only A flags a source record missing from the target; Only B flags a target record absent from the source.
A cutover review can ask
- Which source IDs did not appear in the target extract?
- Which target IDs were not in the source snapshot?
- Which balances, statuses, or other mapped fields changed?
- Which keys are duplicated or incomplete?
Validate one export pair at a time.
1. Capture the same scope
Export the source and target at comparable cutover points. Decide which records belong in the review.
2. Define identity and values
Map IDs across changed header names. Use a composite key if needed; compare balances or attributes separately.
3. Keep an evidence file
Review explained exceptions and export the result workbook locally for your sign-off process.
Repeat the check at the next cutover wave.
With Pro, save the field mapping and rules as a workflow, then choose fresh local exports for the next run. The saved workflow keeps configuration, not spreadsheet contents. MatchDock does not run a migration pipeline, capture live changes, or write records back to either system.
Your spreadsheet contents stay in your browser.
MatchDock parses and reconciles your files locally. Spreadsheet contents are not uploaded to MatchDock servers, and Excel exports are generated in your browser.
Ready to review the exceptions?
Start with two Excel or CSV exports. Choose the records that should match, apply explicit rules, and keep uncertain outcomes visible.