Independent tool for EspoCRM
Check the rows.
Before you import.
Spot uncertain contact matches, company links and field changes in your CSV — while there is still time to review them.
1 Choose your snapshots
Export Contacts with IDs and the fields you want to compare. Use a fresh, complete export. UTF-8 CSV · up to 5 MB and 10,000 rows per file.
What should I export?
- From your own EspoCRM instance, export Contacts including ID, email and any fields you plan to check. Remove filters that would hide potential matches.
- Select the CSV you intend to import. A stable CRM ID is the best match key; a changed email may not identify the old record.
- To check an incoming company ID or name, also export Accounts with ID and Name. Secondary email aliases, custom relationships and multi-value fields are outside this version.
Nothing here writes to your CRM or prepares an automatically approved import. Follow your normal backup and native import procedure after resolving the findings.
2 Confirm the comparison
Settings contain column mappings only. Save them to check the next batch without rebuilding the mapping.
Email and company-name lookups include case and surrounding-space variants to surface risks. They do not reproduce database matching rules.
Fields to compare
| Include | Incoming column | Existing column |
|---|
Only checked fields are compared. A blank is always flagged for review; it is never assumed to mean “clear” or “keep”.
Company lookup (optional)
3 Review your findings
“Unique match” means one candidate in these files with no row-level warnings. It is not clearance to import. Report downloads contain your record values; keep them private.