The conversations at a trade show are only worth what reaches your sales system. Too often, that is a spreadsheet uploaded ten days later, with half the columns blank, the notes left behind in a rep's app, and the same buyer appearing three times because two reps and the organizer's scanner all captured them.
Getting trade show leads into your CRM well is mostly a setup job. Decide the fields, the event tag and the duplicate rules before the show, pick the route each contact takes, and the records arrive the same day with the context that makes follow-up specific. This guide covers that setup for Salesforce, HubSpot, Zoho CRM and any other CRM.
To get trade show leads into your CRM, prepare it before the show: create custom fields for your qualification answers, agree one event tag and a source value, and set a duplicate rule based on email. At the booth, capture every contact in one app with notes and qualification fields. Then sync each contact as it is saved, or export and import at the end of each day, and merge the organizer's lead file with a duplicate check. Aim to have every lead in the CRM the same day.
CRM cleanup is easier to prevent than fix. An hour with whoever runs your CRM, two weeks before the event, saves days of cleanup afterwards.
CRMs organize people differently. Salesforce and Zoho CRM separate leads (people not yet qualified) from contacts (people attached to an account). HubSpot keeps everyone as a contact and uses a lifecycle stage to show where they are. Agree three rules:
Look at what your team will record at the booth and check the CRM can hold it. Typical gaps are the qualification fields: interest level, product line, quantity tier, buying timeline and next step. Create them as picklists with the same options the booth team will use. Free text in a qualification field cannot be filtered or reported on.
Intent signals, in apps that support them, work like a custom form you design to qualify a prospect: for example order quantity tiers of 100, 500, 1,000 and 5,000, or a buying timeline of this quarter, this year or later, tapped at the moment of capture. Mirror those options in the CRM so the values match.
Every contact from the show needs two values that never change: the event (for example "Hannover Messe 2027") and the source ("Trade show"). Use one naming pattern for every event, such as show name plus year. This is what lets you build a list of the show's contacts, assign follow-up and later trace revenue back to the event. See the trade show ROI guide for why the tag matters months later.
Pick the field the CRM uses to decide that two records are the same person. Email is the usual choice; phone is a weaker fallback because formats vary. Then decide what a match does: update the existing record, add a note to it, or skip the new row. Write the rule down and give it to everyone who will import data.
Fill this in with sales operations before the show. The left column is what your capture app or the organizer's file provides; the right side is where it lands.
| Captured field | CRM field (example) | Type | Rule |
|---|---|---|---|
| First name, last name | First Name, Last Name | Text | Required |
| Company | Company or Account | Text | Match to existing account where possible |
| Job title | Title | Text | Keep as captured |
| Duplicate key | |||
| Phone, mobile | Phone, Mobile | Phone | Include country code |
| Website | Website | URL | Used to match the account |
| Country, city | Country, City | Picklist, text | Use the CRM's country list |
| Event | Event or Campaign | Picklist | Same name pattern for every show |
| Source | Lead Source | Picklist | "Trade show" |
| Captured by | Owner or Captured By | User | The rep who scanned |
| Interest level | Interest (custom) | Picklist | Options match the booth fields |
| Quantity tier | Quantity Tier (custom) | Picklist | Options match the booth fields |
| Timeline | Timeline (custom) | Picklist | Options match the booth fields |
| Notes, voice note transcript | Description or Note | Long text | Keep the full text |
| Capture date | Created Date or custom | Date | Keep the show date, not the import date |
Two checks before you sign it off: every picklist value on the booth side exists on the CRM side, and nobody has mapped two captured fields into one CRM field by accident.
The capture app sends each contact to the CRM after it is saved, usually within seconds when the phone is online. This is the best route for teams that exhibit often: nobody has to remember an import, and the record is there while the show is still running.
What to check: that the sync creates the right object (lead or contact), that the event tag travels with it, and what happens to contacts captured offline. In a good app they sync once the phone reconnects.
Export from your capture app to Excel or CSV at the end of each day, then use the CRM's import tool to map columns to fields. It is slower, but it suits a one-off event, a CRM your app does not connect to, or a team that wants a person to review every row first.
What to check: that the export includes the qualification fields and notes, that the event and source columns are filled on every row, and that the import uses your duplicate rule. Run a test import of five rows before the full file.
If you rented the organizer's lead retrieval, you receive a file of badge scans during or after the show. It often overlaps with contacts you also captured in your own app, sometimes with richer registration data and sometimes with none of your notes. See what lead retrieval is for what that file typically contains.
Do not import it straight on top of your own records. Import it into your capture app or a staging sheet first, resolve duplicates so each person has one record, keep your notes and qualification answers, and add any registration fields the organizer's file holds. Then send the merged records to the CRM.
| Situation | Best route |
|---|---|
| You exhibit several times a year and your CRM is connected | Direct sync |
| One event, or a CRM your app does not connect to | Export and import, daily |
| You rented lead retrieval and also used your own app | Merge, then sync or import |
| Sales operations must review every record first | Export and import |
The principles above apply to any CRM. A few points specific to the common ones, in general terms:
If you are unsure how your CRM is set up, ask whoever administers it to fill in the field-mapping worksheet with you. Ten minutes with them avoids rejected records on the first evening of the show.
A lead that is not in the CRM cannot be assigned, added to a sequence or counted. Teams that import a week after the show lose exactly the days when follow-up works best. The follow-up guide covers timing in detail; the CRM side is simple:
At a busy show, the same person can reach you three ways: a badge scan by one rep, a business card scanned by another, and a row in the organizer's file. The fix happens in two places.
Before the CRM: review the duplicates your capture app flags and choose, for each match, whether to keep one record or both. Merge notes from both captures into the record you keep.
In the CRM: let the duplicate rule catch people who already existed before the show. Check the first import's results report for matches and decide whether the rule did what you intended.
Common causes worth fixing:
| Mistake | What happens | Fix |
|---|---|---|
| No event tag | You cannot build the show's list or trace revenue | One tag pattern, on every record |
| Notes left in the app | Sales calls the visitor with no context | Map notes and transcripts to a long-text field |
| Free-text qualification | Nobody can filter "wants a quote this quarter" | Picklists with matching options |
| One big import after the show | Follow-up waits a week; errors surface too late | Sync or import daily |
| Organizer file imported on top | Duplicates and overwritten notes | Merge first, then import |
| Import date as created date | Reports show the wrong month | Keep the capture date |
| Every scan into the CRM as a sales lead | Students and competitors in sales queues | Sort by qualification before routing |
A five-person team from an industrial valve maker exhibits at a three-day show and uses HubSpot. Two weeks before, the marketing operations lead adds three custom properties (product line, quantity tier, timeline) with the same options the booth team will tap, and creates the event value "FlowTech 2027".
At the show the team captures 290 contacts in one app, synced to HubSpot after each save with the fields they mapped. Each evening the lead checks the day's count in HubSpot against the app: 104, 117 and 69. On day 2 she finds that 11 contacts captured in a hall with no signal have not arrived; once the reps reconnect, they sync.
The organizer's lead file arrives after the show with 214 badge scans. Imported into the app first, 176 match contacts the team already has; the other 38 are added. The merged records gain job titles from the registration data. By the morning after the show, 328 records sit in HubSpot under one event value, and the sales team's list of quote requests for this quarter (41 contacts) is a saved filter on the properties they mapped, not a project.
Habsy syncs the fields you map to your CRM. Scanning is free and unlimited; CRM integrations are part of Habsy Plus.
Connect your CRM. In the Habsy app, open Settings › Integrations and connect your CRM. Habsy supports 10+ CRMs, including Salesforce, HubSpot, Zoho CRM, Dynamics 365, Odoo and Zapier, plus custom integrations on request. Teams on Habsy Platform connect under Integrations at app.habsy.ai, where Habsy maps fields automatically when you connect and asks you to confirm. You can change the field mapping to suit your CRM.
Sync each contact after save. Turn on CRM sync in Card Preferences (Habsy Plus), per save or as a default in Settings. After a contact is saved from a scan, a batch or manual entry, Habsy syncs it to your connected CRM in the background. Contacts captured offline are processed once the phone reconnects.
Push contacts you already have. The app can push existing contacts to the CRM in bulk. On Habsy Platform, turning on auto sync shows a button to push existing contacts, and managers can push selected leads from an event campaign.
Export when you need a file. Export to Excel, CSV or VCF on any plan. Exports include one column per intent signal, your notes, audio transcriptions, the source and the created date, so a manual import keeps the booth context.
Handle duplicates before they leave. Habsy flags possible duplicates and you choose how to handle each match; nothing merges silently. Import the organizer's lead file into Habsy (Settings › Manage Account › Upload Contact, CSV up to 10 MB or VCF) to merge it with your own scans before syncing.
Know the sync direction. CRM sync is one-way as standard, from Habsy to the CRM. Two-way sync is available as a custom integration and is not charged separately.
See Habsy event lead capture for the app, or Habsy Platform for team campaigns and CRM pushes from each event.
For the wider booth process, see the trade show lead capture guide.
Trade show leads reach the CRM cleanly when the CRM is ready before the show: fields that match the booth, one event tag, one duplicate rule. Then pick the route, sync or import every day, merge the organizer's file instead of stacking it, and sales gets a usable list the morning after the show.