Key matching across different layouts
CRM and store exports never share column names or order. Matching runs on the key columns you map, so 'Email Address' in one file and 'customer_email' in the other still line up.
All use cases
One customer, two systems, zero matches.
Your CRM says 4,200 customers. Your store says 3,900. Which records are missing where, and whose phone number is right? Export both systems to CSV, and CSV Power Editor matches them by email or customer ID, shows what differs field by field, and helps you build a single master list — locally, so customer PII never leaves your Mac.
Workflow
From two exports to one clean answer.
- 1
Export customers from both systems
Pull a customer CSV from each side — CRM (Salesforce, HubSpot, Pipedrive), store (Shopify, WooCommerce), or ERP. Any system that exports CSV or XLSX works.
- 2
Open both files and normalize the key
Open one export and import the other as a second tab. Run Trim Spaces and Change Case on the email column in both so '[email protected] ' and '[email protected]' match.
- 3
Compare keyed by email or customer ID
Run the Compare Files wizard and map the key columns — email is usually right, or a shared customer ID if you have one. Column names don't need to match between systems.
- 4
Read the compare workbook
The output lists customers missing from either system and, for matched customers, appends the second system's values alongside the first — so conflicting names, phones, and addresses are visible side by side with audit notes.
- 5
Build the master list (optional)
Merge both sources into one sheet, run Remove Duplicates keyed by email, and review fuzzy matches for typo variants. Export the result as an import-ready CSV or XLSX.
Why it works
Reconciliation needs keys, not eyeballs.
Fuzzy matching for messy reality
Fuzzy Duplicates catches near-matches — typos, spacing, casing — that strict equality misses, which is exactly how the same human ends up as two records.
Field-level differences, documented
The compare workbook is a normal spreadsheet with audit columns. Hand it to the team that owns the CRM and they can review every conflict without special tools.
Customer PII stays on your Mac
No uploads, no web converter, no third-party processor. The app makes no outbound network connections — reconcile customer data without adding a vendor to your privacy story.
FAQ
Common questions.
The two systems use completely different column names. Does that matter?
No. The Compare Files wizard lets you map which columns are the matching key in each file, so 'Email Address' and 'customer_email' compare correctly. Other columns don't need to align either.
Should I match on email or customer ID?
Use a shared customer ID if both systems have one — it survives email changes. Otherwise email works well; normalize it first with Trim Spaces and Change Case so formatting differences don't break matches.
Can I find customers that exist in the store but not the CRM?
Yes. Rows present in one file but missing from the other are identified by key in the compare workbook — that list is exactly your sync gap.
Can I merge both systems into one master list?
Yes. Merge the two sources into one sheet, then Remove Duplicates keyed by email, with Fuzzy Duplicates to review typo variants before they slip through. Export the cleaned master as CSV or XLSX.
Does it work with Salesforce, HubSpot, Shopify, or WooCommerce?
It works with any system that exports CSV or XLSX — which covers all of those. The reconciliation happens on the exported files, so no integrations or API keys are involved.
Is customer data uploaded anywhere?
No. Everything runs locally on your Mac and the app makes no outbound network connections.
Keep going
Related guides.
Compare Two CSV Files on Mac
Get a reviewable compare workbook with matched keys, changed columns, and missing rows.
Merge CSV Files into One
Combine multiple CSV or Excel exports into one workbook, dedupe the result, and export.
Clean and Prepare Data for ERP Migration
Normalize legacy exports, dedupe master records, and validate fields before they hit the ERP importer.