Duplicates are the quiet failure mode of every card scanner workflow. Nobody notices them on the day. They surface a year later when three sales reps email the same prospect in the same week, or when a report counts one company as four. The fix is cheap if you do it at the point of import and expensive once the records have spread through a CRM.
Where duplicate scans actually come from
There are four common sources, and none of them is carelessness. The same person hands out a card at two events a year apart. Two colleagues at the same conference each scan the same contact. Someone rescans a card because the first attempt looked wrong. Or a contact already exists in the CRM from a web form and now arrives again from a card.
Each produces a slightly different kind of duplicate, which is why a single matching rule never catches all of them.
Match on the field that does not change
Names are unreliable — Robert becomes Bob, initials appear and disappear, and transliterated names have several valid spellings. Company names are worse, because branch names, legal suffixes and abbreviations all vary.
Email address is the strongest single match key, followed by mobile number. Match on email first, then mobile, then fall back to a fuzzy name-plus-company check for the remainder. Anything that clears the first two rules is a duplicate with near certainty; anything caught only by the third deserves a human glance before merging.
Catch them before the export, not after
The cheapest place to deduplicate is inside the scanning app, while the set is still small and you remember the event. Sort by company, scan the list visually, and merge the obvious repeats before anything syncs outward.
This is a five-minute job for forty cards and a multi-day job for four thousand CRM records. If you are exporting to a spreadsheet as an intermediate step, our guide to getting scans into Excel cleanly makes the visual pass easier, because a sorted column of emails shows repeats instantly.
Merging without losing the good bits
The mistake when merging is to keep one record and delete the other. The second scan often holds information the first did not — a new job title, a changed mobile, the note about what they asked at the second event.
Merge field by field, keeping the most recent value for anything that changes over time (title, company, number) and keeping all notes rather than the latest one. A contact history that shows someone moved from one firm to another is genuinely useful; a merge that silently overwrote it is not.
Stop the team from creating them in the first place
Two reps scanning into two separate phones will generate duplicates at every event, permanently. The structural fix is a shared contact pool, so the second scan lands in a database that already has the first and can flag it.
BizConnect offers a shared contact database with an admin dashboard and role-based access on its team plan, which turns duplicate prevention into a default rather than a chore. We covered how to roll that out in running one app across a whole sales team.
Let the CRM do the second pass
Salesforce, HubSpot and Zoho all have their own duplicate rules, and they are worth configuring before a bulk import rather than after. Set the matching rule to email, decide whether the CRM should block or flag on match, and run a small test batch of ten contacts first.
BizConnect exports natively to all three, plus Google Contacts, Outlook and Excel, and connects through Zapier to the rest — so the pre-import cleanup and the CRM rules stack rather than compete. If Outlook is your destination, the Microsoft 365 guide covers where duplicates tend to appear across shared mailboxes.
A ten-minute routine that keeps it clean
After every event: sort by email, merge repeats, check that job titles look current, then export. Once a quarter: run the CRM’s duplicate report and clear whatever slipped through. That is the entire discipline, and it takes less time in a year than one afternoon of untangling a corrupted database.
The alternative is a contact list that slowly stops being trusted, which is how teams end up back on spreadsheets — a path we traced in the app versus spreadsheet comparison. BizConnect is on Google Play with a free plan of 50 cards a day if you want to set the routine up before your next event.
Frequently Asked Questions
How do I stop duplicate contacts from a card scanner?
Match on email first and mobile second, deduplicate inside the app before exporting, and use a shared contact pool so team members scanning the same person land in one database rather than several.
What is the best field to match duplicates on?
Email address, then mobile number. Names and company names vary too much — abbreviations, initials and transliterations all create false negatives.
Should I merge or delete a duplicate contact?
Merge. The newer scan often carries an updated job title, a changed number or a fresh note. Deleting one record throws that away.
Can two people scan the same card without creating duplicates?
On a team plan with a shared contact database, yes — the second scan lands in the same pool and can be flagged. On separate personal accounts, duplicates are inevitable.
Does the CRM catch duplicates on its own?
Salesforce, HubSpot and Zoho all have duplicate rules, but configure them before a bulk import and test with a small batch. They work best as a second line of defence, not the only one.