> ## Documentation Index
> Fetch the complete documentation index at: https://docs.boothrev.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Exporting leads

# Exporting Leads to Your CRM

When the event is over and you're ready to hand off leads to sales, you export them from BoothRev to your CRM. This is the **outbound** CSV channel — for the conversational alternative (a CRM-ready brief for one lead or a whole event, without a file download), see [Connecting Claude → Prepare next steps for your other tools](/integrations/connecting-claude#prepare-next-steps-for-your-other-tools).

***

## When to export

Export after the core follow-up window has passed — typically 2 to 5 days after the event ends. By then, most leads should be confirmed, Rev should have processed them, and the follow-up status should be accurate.

You can export at any time, but earlier exports may be missing context that arrives after the event (late voice note transcripts, post-event notes, meetings agreed after follow-up).

***

## Export formats

BoothRev exports in four formats:

| Format | Use it when |
| - | - |
| **Salesforce** | Your CRM is Salesforce |
| **HubSpot** | Your CRM is HubSpot |
| **SAP** | Your CRM is SAP |
| **Generic CSV** | Any other CRM, or a spreadsheet handoff |

All formats include the same lead data. The column names and structure are formatted to match what each CRM expects. This is the same field mapping used by [Connecting Claude](/integrations/connecting-claude)'s CRM action brief and event-export tools, so the two can't drift.

***

## Full field reference

Every export includes:

| Field | Notes |
| - | - |
| Contact details | First name, last name, email, phone, title, company |
| Priority | High, Medium, or Low, set by Rev |
| ICP fit score and label | Set by Rev |
| Qualification summary | Set by Rev |
| Next steps | Set by Rev |
| Meeting Agreed date | If a meeting has been set |
| Follow-up sent status | Whether a follow-up has actually been sent |
| Follow-up tier | How BoothRev thinks this lead should be worked by whatever tool you send it to next — see below |
| UTM campaign tag | From your event settings |
| Captured by | Which rep captured the lead |
| Capture timestamp | When the lead was captured |

### Follow-up tier

One of five values, reflecting how much real human contact this lead has had:

| Tier | Meaning |
| - | - |
| **1:1** | A rep actually had a conversation with them |
| **1:few** | Captured, but no real conversation happened |
| **1:many** | Never claimed — still a cold pre-reg or import row |
| **unresolved** | Still sitting in Duplicates, needs a merge or release first |
| **dead** | Archived |

Use this to decide how a lead should be worked once it lands in your CRM or sequencing tool — a **1:1** lead is ready for a rep to pick up the relationship where it left off, while a **1:many** lead is better suited to a broader nurture sequence than a personal outreach. Follow-up tier doesn't currently appear anywhere in the BoothRev app UI (mobile or web) — CSV export, the [Connecting Claude](/integrations/connecting-claude) CRM action brief, and event-export tools are the only places you'll see it.

***

## How to export

1. Open your event in the web inbox.
2. Click **Export** in the top right.
3. Select your CRM format.
4. Download the file.

Import it into your CRM using that platform's standard CSV import process.

***

## Exporting a subset of leads

If you only want to export certain leads — for example, only High priority leads or those with a Meeting Agreed — filter the lead list first, then export. The export reflects what's currently visible in the list.

***

## Related

* [Integrations](/integrations/index)
* [Integrations → Connecting Claude](/integrations/connecting-claude) — the conversational alternative, and the full MCP tool list
* [Integrations → Importing leads](/integrations/importing-leads)
* [Your inbox](/for-event-owners/your-inbox)
* [Event dashboard](/for-field-marketing-managers/event-dashboard)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.