TL;DR
- One wrong mapping can put names in the company field, skip the email column or swap first and last names.
- The CRM can't match those rows to existing records, so it creates new ones.
- First find the import's records by date or import name, and decide whether to delete the batch or merge it.
- If the import added anything new, like real contacts or activities, merge the duplicates instead of deleting.
- In Dedupely, filters focus a search on one import, and cross-field matching catches values in swapped fields.
An event list goes into the CRM at the end of a long day. The email column was mapped to "Secondary email". Or first and last name were swapped. Or the company column landed in "Job title". The import ran, and the CRM couldn't match any row to the contacts that were already there, so it created a new record for each.
The next morning, there are 900 new contacts, most of them duplicates with data in the wrong fields. This post covers how to clean up after a bad import.
What a wrong mapping does
| Mistake | What the CRM does |
|---|---|
| Email mapped to a field the CRM doesn't match on | Creates a new contact for every row, even existing people |
| First and last name swapped | Creates records that don't match on name |
| Company mapped to the wrong field | Leaves contacts without a company, or creates new companies |
| A column mapped to a field with existing data | Overwrites good values on existing records |
The first one is the most common, and the most damaging: the field the CRM uses to find existing contacts came through empty.
Step 1: Find the import's records
Every import leaves a trail you can filter on:
- Created date and time: the records arrived together.
- Import name or list: many CRMs tag records with the import they came from.
- Created by: the user who ran the import.
Count them, and check a sample to see which mapping went wrong.
Step 2: Delete the batch or merge it?
| If the import... | Then |
|---|---|
| Only created duplicates of people already in the CRM, and nothing else touched them | Deleting the batch and re-importing correctly is usually simplest |
| Also created real new contacts | Merge the duplicates, keep the new ones |
| Has had activity since: emails sent, calls logged, workflows run | Merge, so that activity isn't lost |
| Overwrote values on existing records | Restore those values from a backup or export, then merge |
Deleting is only clean if nothing else depends on the new records.
Step 3: Fix the values, then merge
- Move values to the right fields on the imported records, where you can, with a bulk update.
- Match the import's records against the rest of the CRM, on email if it's now in the right field, or on name plus company.
- Keep the existing record as the survivor, so its ID, owner and history stay.
- Make sure blanks don't win, so empty imported fields don't overwrite real values.
How Dedupely helps after a bad import
In Dedupely, filters on any synced field, like created date or an import or source field, let you focus a search on one import's records. Cross-field matching catches values swapped between the fields of a match, like first and last names entered the wrong way round. The Primary Record setting, for example Oldest Record, keeps the existing contact as the survivor, and blank values never win, so empty imported fields can't overwrite real data. Merge History records each merge with the original values.
Find it, decide, then merge
A bad mapping turns an import into a batch of duplicates. Find the batch by date or import name, delete it only if nothing depends on it, otherwise fix the values and merge into the existing records, keeping their history and owners.
Frequently asked questions
How do I fix duplicates from an import with the wrong column mapping?
Find the import's records by date or import name, fix values in the wrong fields, then merge the duplicates into the existing records.
Should I delete the imported records?
Only if they're all duplicates and nothing has happened to them since. If they include new contacts or activity, merge instead.
Why did the import create new records instead of updating?
The field the CRM uses to find existing records, usually email, was mapped to the wrong column or came through empty.
What if the import overwrote good data?
Restore those values from a backup or recent export before merging.
How do I avoid this next time?
Import a few rows first, check them in the CRM, then import the rest.




Pipedrive user