Data migration reconciliation
Validate structured pre- and post-migration exports record by record. Use Generic Record when you have structured exports from before and after a migration and need to verify which records correspond, what changed and what exists on only one side.
Local-first workflow
Platforms Web app available
Windows Desktop follows web validation
Input CSV · XLS · XLSX
Journey Import → Understand → Map & Configure → Match → Explain → Review → Verify → Export
Method Explicit rules · Explainable results
Open the browser workspace to process supported files locally. Only minimal trial, entitlement or privacy-safe analytics metadata uses ReconLoom services.
How to use ReconLoom for migration validation Import. Choose the supported pre-migration and post-migration CSV/XLS/XLSX exports. Map. Define the identity fields that identify the same business record on each side. Configure. Select typed comparison fields that should be checked after identity is established. Reconcile & Review. Inspect exact matches, changed records, conflicts, invalid records and records present on only one side. Export. Generate the supported local comparison output for further review or evidence. Record identity Customer ID, account ID, SKU, employee ID or another key that genuinely represents the same record in both exports.
Comparison fields Status, category, amount-like text/number fields, dates or other supported typed fields selected deliberately.
Migration evidence Changed, missing, duplicate/conflict and invalid states stay distinct so they can be investigated.
Scope: ReconLoom validates structured exported records. It does not perform the migration, infer schema meaning with AI, validate unexported database state or replace a migration platform.Related: Generic Record · Inventory reconciliation · All use cases