Short answer: A business card scanner for CRM reads a card and writes the person to a contact or lead record, the company to a company or account record, and the conversation to a note. Before your next event, set your field mapping, duplicate rule and owner rule, so every card lands in the right place with someone responsible for it.
Getting a business card into a CRM is not a scanning problem. It is a data problem: the scan takes seconds, but the rules you set decide whether the record is useful a week later.
This guide covers field mapping, duplicates, owners and notes, then the specifics of Salesforce, HubSpot and Zoho CRM, the spreadsheet route for teams without a CRM, and a checklist to work through before your next expo.
What does a business card scanner for CRM actually do?
It reads the card, maps each value to the right CRM field, checks for an existing record, and adds context. In four steps:
- Read the card. Pull out name, title, company, email, phone, website and address.
- Map the fields. Decide which CRM object and field each value belongs in.
- Check for an existing record. Update it if one exists, create it if not.
- Add context. Assign an owner, tag the event and log what was discussed.
Most comparisons focus on step one. In practice, steps two to four are where records go wrong. A perfect scan that creates a duplicate with no owner and no notes is worse than useless, because it looks like progress.
How should card fields map to your CRM?
Person fields go on the contact or lead, and company fields go on the company or account. A card holds information about two things, a person and a company, and your CRM almost certainly stores them separately. Mixing them up is the most common setup mistake.
| Card field | Belongs on | Notes |
|---|---|---|
| Full name | Contact or Lead | Split into first and last name. Watch for initials and honorifics. |
| Job title | Contact or Lead | Keep the exact title. Map seniority separately if you use it. |
| Contact or Lead | Your main duplicate key. Store in lower case. | |
| Mobile and office phone | Contact or Lead | Store with country code, for example +91, so WhatsApp and dialling work. |
| Company name | Company or Account (text field on a Lead) | Normalise "Pvt. Ltd." and similar suffixes so matching works. |
| Website | Company or Account | The domain is what most CRMs use to match companies. |
| Office address | Company or Account | City is useful for territory routing. |
| Event and date met | Contact or Lead | Use a picklist field or campaign, not free text. |
| Conversation | Note or activity | Never squeeze it into a description field. |
Should a new card become a contact, a company or a lead?
Either "lead first" or "contact plus company" works, as long as the whole team uses the same one. Decide before you scan a single card.
- Lead first. Every new person starts as a lead. Someone qualifies them, and only then do they become a contact linked to a company. This keeps unqualified names out of your main database.
- Contact plus company. Every person becomes a contact linked to a company straight away, and a status field tracks how qualified they are. This is simpler and suits teams where most event contacts are worth tracking.
What goes wrong is letting each salesperson choose. Pick one rule and set the scanner to follow it.
Should a scanner create Leads or Contacts in Salesforce?
Create Leads for new people at companies you do not work with yet, and Contacts on the existing Account when the company is already a customer. Salesforce keeps the two apart. A Lead is a standalone record, with the company stored as a text field. When you convert a lead, Salesforce uses the lead's information to create an account, a contact and an opportunity.
- Create Leads for expo contacts at new companies. This is the usual choice.
- Create Contacts on an existing Account when the company is already a customer or has an open opportunity. Otherwise the new person sits as a lead, cut off from the account your team is already working.
A good setup checks for an existing Account by company name or website first, and only creates a Lead if none is found. Also check your Salesforce matching and duplicate rules: a duplicate rule can either block a new record or allow it with an alert. If it blocks one, you need to know whether the scanner tells you or fails silently.
How does a business card scanner for HubSpot link contacts and companies?
HubSpot links a contact to a company by matching the domain in the contact's email to the company's domain name. People are stored as contacts and organisations as companies, joined by associations. HubSpot deduplicates contacts by email address and companies by domain name.
The automatic association setting works well for corporate emails. Many founders and smaller traders hand out a Gmail address, though. For free email addresses, HubSpot checks the contact's Website URL instead, and if that is empty, no association happens. So a business card scanner for HubSpot should write the website printed on the card.
Set the contact's lifecycle stage and lead status at creation, so event contacts show up in the right views instead of sitting unassigned.
How does Zoho CRM handle scanned cards?
Zoho CRM works like Salesforce: separate Leads, Contacts and Accounts modules, with a conversion step. When you convert a lead in Zoho, it creates a contact and, if the lead has a company name, an account, and you can add a deal. The same questions apply: which module a new card goes into, how duplicates are matched and who owns the record.
Check whether the scanner writes to Zoho directly or exports a file you import yourself. A CSV import works, but someone has to do it after every event, and that is exactly the step that gets delayed.
How should duplicates be handled?
Match on email first, then phone, then name plus company, and update the existing record instead of creating a new one. Duplicates are the biggest source of bad CRM data after events: the same person meets two colleagues at the same stand, or was already in the CRM from last year.
- Email. The most reliable match.
- Phone number, stored in one format with country code.
- Name plus company, as a last resort, flagged for review rather than merged automatically.
When a match is found, add the new event, the new note and any new phone or title. Do not create a second record. Do not overwrite a title without checking which one is newer.
Who should own the scanned record?
In a small team, the person who scanned the card owns the contact. Owner assignment decides whether anyone follows up.
Larger teams may route by territory, product line or account. If the company already has an account manager, the new contact should usually go to them, with the person who met them credited in a note. Whatever the rule, write it down and make sure the scanner applies it, because an unowned record is a record nobody follows up.
How should you log the conversation?
Log it as a note or activity on the contact, linked to the company, with the event name and date. The card tells you who someone is. The conversation tells you why to call them: what they are working on, what you promised and when.
Event note format
Met at: [event], [date], [stand or session]. Discussed: [their project or problem]. Promised: [what you said you would send]. Next step: [call, visit or quote] by [date].
Notes logged during the event are far more useful than notes typed two days later from memory. The fastest route is a line or a voice note while you are still at the event. Our trade show follow-up guide covers how to use these notes in the first message.
How do you convert business cards to Excel when you have no CRM?
Use a shared online sheet with one row per person and fixed columns. Many small businesses and founders in India do not use a CRM yet, and that is fine. Use these columns:
- First name, last name, title
- Company, website, city
- Email, mobile with country code
- Event, date met, owner
- Conversation notes, promised item, next step, next step date
- Status: new, followed up, replied, meeting booked, not interested
Keep it online rather than in a file on one laptop, so the whole team sees the same list. Use the same column names a CRM would use, so a later import into Salesforce or HubSpot is straightforward.
What about privacy?
Store only what you need, use it for the follow-up the person expects, and stop when they ask. A card handed to you is an invitation to follow up, not permission for anything you like. India's Digital Personal Data Protection Act, 2023 gives people the right to withdraw consent at any time, and requires personal data to be erased once consent is withdrawn, unless another law requires you to keep it. This is not legal advice, so check your own obligations.
Business card scanner setup checklist
Work through this before your next event, whether you use a trade show lead capture app or a simple scanner.
| Item | Decision to make | Check |
|---|---|---|
| Record type | Lead first, or contact plus company | One rule for the whole team |
| Field mapping | Person fields to contact or lead, company fields to company or account | Test with 5 real cards |
| Phone format | Always store with country code | Numbers open in WhatsApp |
| Duplicate rule | Email, then phone, then name plus company | Scan a card already in the CRM |
| Company match | By website domain, then normalised name | Contact links to the existing company |
| Owner | Scanner, territory or account owner | Every test record has an owner |
| Event tag | Picklist value or campaign per event | You can filter by event |
| Notes | Conversation logged as a note on the contact | Note visible on contact and company |
| No CRM | Shared sheet with fixed columns | Whole team has access |
| Privacy | What you store and how long | Removal process agreed |
Sources
- Salesforce Trailhead: Create and convert leads
- Salesforce Trailhead: Improve data quality (matching and duplicate rules)
- HubSpot Knowledge Base: Deduplication of records
- HubSpot Knowledge Base: Automatically create and associate companies with contacts
- Zoho CRM Help: Converting leads
- The Digital Personal Data Protection Act, 2023 (MeitY)
How does SuperBound handle cards and your CRM?
SuperBound, launching soon in early access, works over WhatsApp. You send a photo of the card, with a note or voice note if you have one. It reads the card, fills in company details and LinkedIn, and saves the contact: to your phone or Google Contacts if you work alone, or to Salesforce, HubSpot or Google Sheets for teams. It then drafts a follow-up email and WhatsApp message for you to send yourself. See how it works, or read more about our WhatsApp business card scanner.
Frequently asked questions
Should a scanned business card become a Lead or a Contact in Salesforce?
Make it a Lead if your team qualifies people before they join an account, which suits most event contacts you have just met. Make it a Contact on an existing Account if the company is already a customer or an active opportunity. Pick one rule for the whole team before the event, so records do not end up split across both objects.
How does HubSpot link a scanned contact to a company?
HubSpot matches the domain in the contact's email address to the company's domain name, if automatic association is switched on. For free email addresses such as Gmail, it checks the contact's Website URL instead. So a scanner that also writes the website from the card helps. Check the association on a few test scans before an event.
How do I avoid duplicate contacts when scanning cards?
Match on email first, then phone number, then name plus company. If a match exists, update the existing record and add the event as a note instead of creating a new one. Salesforce, HubSpot and Zoho each have their own duplicate checks, so make sure your scanner and your CRM use the same matching logic.
Can I convert business cards to Excel instead of a CRM?
Yes, a shared spreadsheet works well for small teams. Use one row per person with columns for name, title, company, email, phone, website, event, date met, owner, conversation notes and next step. Keep it in a shared online sheet, not a file on one laptop, so the team sees one list and you can import it into a CRM later.
Does scanning business cards into a CRM raise privacy issues in India?
Yes, India's DPDP Act applies to how you use and keep personal data, even from a card someone handed you. Store only what you need, use it for the follow-up the person would expect, and honour requests to stop: the Act gives people the right to withdraw consent at any time. This is not legal advice, so check your own obligations.
We build the WhatsApp follow-up assistant for people who meet buyers at events.