Before importing event leads into a CRM, preserve the original file, review extracted fields, identify existing records, map the columns, and test a small sample. Do not merge people by name alone or assume a card scan establishes marketing permission or sales qualification.
How do you clean trade show leads before CRM import?
Work from a copy of the captured contact list. Review the card details against the source, separate uncertain records, compare reliable identifiers with your existing CRM, and agree on field mapping before importing. Give every accepted next action a responsible owner. Keep the original capture and your decisions so a colleague can understand what changed.
This is a sales-operations workflow, not an automatic ExpoSnap deduplication feature. ExpoSnap supports reviewed card capture, notes, exports, and supported CRM handoffs. Matching policies, import rules, campaign fields, and ownership depend on your team and CRM configuration.
If your starting point is a pile of paper cards, first follow the business card scanning to Excel guide to create a reviewed working file.
1. Preserve the original and correct uncertain contact fields
Keep a restricted original export and create a separate working copy with a clear version name. Limit access to colleagues who need the data. Record who reviewed each uncertain row and what source supported the correction.
Compare names, organizations, job titles, email addresses, and phone numbers with the card. Pay attention to characters such as O and 0 or l and 1. Remove accidental leading or trailing spaces in a working column, but preserve the original value for reference. Never guess an unreadable email address or invent a missing country code.
A correctly formatted email address is not proof that the mailbox exists, belongs to the person, or may be added to a campaign. Mark missing or doubtful fields for confirmation instead of quietly treating them as valid.
2. Check duplicates without merging different people
Repeated scans can come from multiple representatives meeting the same person. Compare dependable identifiers and conversation context before deciding whether records describe one individual. A shared name, a company domain, or a reception phone number alone is not enough to merge personal contacts.
HubSpot documents email matching for contact imports and Record IDs for identifying existing records. It also warns that omitting a unique identifier can create new contacts. Its company-domain deduplication does not apply in the same way to companies created through an API. Verify the rules for your exact import or integration route rather than assuming all CRMs and sync methods behave identically.
For the specific ExpoSnap handoff, read the HubSpot business card scanner guide and confirm the destination record after syncing.
Source: HubSpot documentation: deduplication and import identifiers
| Situation | Review decision |
|---|---|
| Same person scanned by two reps | Check matching identifiers, keep the useful notes from both meetings, and choose the existing contact where appropriate. |
| Two people share an organization or surname | Keep separate unless reliable evidence establishes they are the same person. |
| Person already exists in the CRM | Confirm the record identifier and allowed updates; do not overwrite a known owner without agreement. |
| Unreadable or conflicting contact detail | Hold the row for review rather than forcing an uncertain match. |
3. Separate card fields from sales handoff fields
A card can provide contact details, but it cannot tell you the person’s budget, authority, permission preferences, or purchase timetable. Record only what was actually discussed. Keep your qualification assessment distinct from the person’s own words.
The worksheet below is a suggested manual handoff structure. It is not a promise that every field appears in an ExpoSnap export or maps automatically to a CRM. Your administrator should confirm supported fields and prepare any extra columns.
| Field group | Suggested fields | Source |
|---|---|---|
| Contact identity | Name, company, role, email, phone, website | Reviewed card or confirmed contact detail. |
| Meeting context | Event, date, representative, discussion summary | Factual meeting notes. |
| Next action | Requested material, owner, due date, contact channel | The action agreed during the conversation. |
| CRM matching | Existing record identifier, new/update decision, review status | Approved CRM matching process. |
| Communication preferences | What was requested, recorded preference, relevant restrictions | The actual request and your organization’s approved policy. |
Download the event contact cleanup worksheet (.txt) Free download. No sign-in required.
4. Map fields and test a small sample before the full import
Back up affected CRM data under your normal policy before a bulk update. An import can update existing records, so a source-file copy alone is not a complete recovery plan. Confirm your CRM’s restore options before making changes that are difficult to undo.
Compare supported destinations on the ExpoSnap CRM integrations page, then use the guide for your CRM rather than assuming the same mapping applies everywhere.
For a Salesforce team, the business card to Salesforce guide explains the reviewed Lead handoff and why qualification and ownership remain part of your CRM process.
- Review the destination
Confirm the CRM object, required fields, identifier rules, ownership policy, and permissions with the administrator.
- Make a column map
Document which source column goes to which CRM field. Keep notes separate from company names or job titles.
- Test representative cases
Use approved sample records covering a new contact, an existing contact, and an uncertain row that should be held back.
- Inspect the result
Open the resulting records and check names, notes, associations, ownership, and whether a record was created or updated.
- Process and reconcile
Run the approved batch, keep the import result, and review rejected rows before retrying them. Repeatedly importing an unresolved file can compound errors.
A fictional cleanup example: 12 scans are not necessarily 12 leads
Suppose a booth team has 12 scanned records. Review finds two extra scans of people already present in the file, leaving 10 distinct contacts. Three of those contacts already exist in the CRM. Of the seven remaining contacts, two have uncertain email addresses that need confirmation.
Under this example’s email-required handoff policy, the working queue contains five potential new contact records, three existing records to review for updates, and two records on hold. That is eight records ready for the next review step, not eight qualified opportunities. None of the counts establishes permission for a marketing campaign.
This is an illustrative arithmetic example, not a customer result or a typical duplicate rate. Keep your own definitions consistent when reporting captured records, distinct contacts, qualified opportunities, and won customers.
When you report the event outcome, use the trade show ROI guide and calculator to keep contact totals separate from attributed financial results.
5. Hand over the next action, not just the spreadsheet
Tell the receiving salesperson which contacts are ready, which need clarification, and what was promised. Check that existing account owners are involved before a second rep starts contacting the same person. If there was no agreed next action, record that instead of inventing urgency.
Review unresolved rows after the handoff and dispose of temporary files under your organization’s retention policy. Do not keep distributing exported contact lists simply because storage is inexpensive.
Once the data and owner are clear, adapt the trade show follow-up email templates to the conversation and review the message before sending.
Frequently asked questions
Should I remove duplicates using the name column?
Not by name alone. Different people can share a name. Review reliable identifiers and context, and follow the matching rules of your CRM before merging or updating records.
Does a scanned business card count as a qualified lead?
No. A scan captures contact information. Qualification depends on a relevant need, the person’s role, the discussion, and your team’s criteria.
Does ExpoSnap automatically create every worksheet field?
No. The worksheet is a suggested manual sales-operations aid. Confirm the actual export and integration fields, and manage extra handoff information in your approved spreadsheet or CRM process.
Sources and further reading
Further reading from event-industry and sales resources. Sample scripts and hypothetical calculations in this guide are illustrations, not customer results.
Put the workflow into practice.
Capture business cards, review contact data, add conversation context, and prepare the next step with ExpoSnap.