> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/the-hub/working-with-leads/how-to-upload-csv-for-enrichment.md).

# How to upload a CSV for enrichment

Upload a CSV of leads to a Mobly event or activation — for pre-event registration lists, marketing lists you want enriched and synced, or bulk-loading historical records into a specific event. Uploaded leads flow into your CRM the same way captured leads do.

*This flow is for Mobly Admins with Hub access.*

## When to use CSV upload vs. other options

* **CSV upload (this article)** — you have a list of leads and want them attached to a specific event or activation, running through Mobly's normal enrichment + CRM sync path.
* **Host registration form** — you want leads to flow in automatically as people register for the event. See [How registrants flow into Mobly](https://help.getmobly.com/help-center/host/how-registrants-flow-into-mobly.md).
* **Off-Hub enrichment** — if you don't want the leads in your CRM but do want them enriched, send the file to your CSM instead. They'll run it through Mobly's enrichment queue and send back an enriched CSV.

## Uploading

1. Open the event or activation you want the leads to land on, and switch to the **Leads** tab.
2. Click **Add Lead** (top-right of the Leads table), then **Import from CSV**. A four-step uploader opens.
3. **Choose file.** Drop in your CSV. You don't have to match a specific format — the next step lets you tell Mobly what each column is. If you'd rather start from a known-good layout, click **Download template**; the template includes the standard lead columns plus a column for each qualifier published to this event.
4. **Match columns.** Mobly guesses which of your columns map to which Mobly fields and qualifiers, and you correct anything it got wrong. See [Matching your columns](#matching-your-columns) below.
5. **Check data.** Mobly flags rows missing required details or carrying qualifier values it couldn't match. Fix them inline, or drop the rows. See [Fixing flagged rows](#fixing-flagged-rows) below.
6. **Confirm upload.** Pick your enrichment mode and any additional options, then confirm.

{% hint style="info" %}
**Every row needs a first name, last name, and company name.** Email is not a substitute for company — a row missing any of those three won't import.
{% endhint %}

## Matching your columns

Step 2 shows a preview of your first five rows with a picker above each column. Set each one to the Mobly field or qualifier it belongs to, or leave it unmatched.

* **Mobly guesses first.** Columns whose headers resemble a known field or a qualifier name are matched automatically. Check them — a wrong guess is easier to miss than a blank one.
* **Fields your file has no values for are tucked behind a disclosure** so the list stays short.
* **Unmatched columns are listed under "Not imported."** Anything there is ignored, which is fine for columns you don't need.

You can't move past this step until first name, last name, and company name are all matched to something.

{% hint style="warning" %}
**A qualifier has to be published and on this event before you can import answers for it.** If one of your columns matches an org qualifier that isn't on this event, Mobly names it and tells you to publish it and add it to the event. Until you do, that column lands in "Not imported" and those values are dropped. See [Configuring qualifiers](https://help.getmobly.com/help-center/the-hub/working-with-leads/configuring-qualifiers.md).
{% endhint %}

Two problems will block the upload outright rather than letting you fix them row by row — more than 10 rows missing required details, or more than 50 rows with qualifier values that don't match. Both point back to a column match being wrong, so re-check step 2 before editing your file.

## Importing qualifier answers

Any qualifier published to the event can be filled in from your CSV — picklist, boolean, open text, numeric, and note-style all work. One column per qualifier, with the answer as the cell value.

Use the value exactly as it's configured in Mobly — for a picklist, that means the value's label as written. For a multi-select, put several values in the one cell separated by a semicolon, or by whatever separator that qualifier is set to. Give a single-select more than one value and the row gets flagged.

Anything Mobly can't match is flagged in step 3 rather than silently dropped.

Answers are applied after the leads are attached to the event, and they apply to **leads that already existed** as well as new ones — so a CSV is a reasonable way to backfill qualifier answers onto leads captured earlier.

{% hint style="info" %}
**A bad qualifier value never fails the import.** If an answer still can't be saved, Mobly imports the lead without it and reports how many values were skipped. You'll see "N of M qualifier values couldn't be saved" on the file afterward.
{% endhint %}

## Fixing flagged rows

Step 3 lists every row that needs attention, with the problem called out per field.

* **Missing required details** — fill them in inline, or drop the row.
* **Unmatched qualifier values** — you get a control shaped to the qualifier: a dropdown for single-select, a multi-picker for multi-select, a number box for numeric, a text box for open text. Each one shows the raw value from your file so you can see what it's replacing.
* **Skip this value** — leaves that one answer off that one lead and imports everything else about them. Reversible while you're still on the step.

## How should we enrich these leads?

The final step asks how Mobly should treat the data you're uploading. Three choices, same as [Host's registrant enrichment mode](https://help.getmobly.com/help-center/host/how-registrants-flow-into-mobly.md#enrichment-mode-for-registrants):

| Mode                                                             | What it does                                                                                                                                       |
| ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Enrich, fill in missing fields only (keep my data)** (default) | Enrichment fills empty fields but never overwrites what you provided. Best when your data is authoritative but you want Mobly to fill in the gaps. |
| **Enrich, overwrite OK**                                         | Enrichment may replace values you provided. Best when your list is old or sparse and you want Mobly's data to take precedence.                     |
| **Skip enrichment**                                              | Import as-is. Mobly never runs enrichment on these leads. They still sync to your CRM.                                                             |

The button label at the bottom of the step reflects your choice — **Confirm and enrich N leads** for a Fill/Overwrite mode, or **Confirm upload of N leads** for Skip.

Leads uploaded under **Skip enrichment** are labeled **"Imported"** on the leads table and are excluded from every re-enrichment sweep. That state is durable until someone edits the lead's mode later.

## Additional options on the confirm step

Two more toggles sit alongside the enrichment mode on the final step:

* **Skip lead owner routing** — bypass any Pulse or org-level lead-routing rules that would normally assign these leads to a rep. Use when you already know who owns each lead and want to preserve that assignment (e.g., a marketing team pre-loading their own list).
* **Mark as registered** — if the event has Mobly Registration enabled, this marks each uploaded lead as **Registered** on arrival, so they're already accounted for in your Registration count and can move straight into check-in on the day.

## What happens next

Uploaded leads land in the event's Leads table right away. Enrichment (if you didn't Skip) runs in the background — most contacts finish within a few minutes; complex ones can take longer. Once enrichment settles, the leads sync to your CRM the same way any captured lead does.

## Troubleshooting

**Rows dropped during validation.** Every row needs a first name, last name, and company name. Email doesn't substitute for company. Fix or drop rows missing any of the three.

**A whole column of qualifier answers didn't import.** Either the column wasn't matched on step 2, or the qualifier isn't published and added to this event. Check the "Not imported" list on step 2 — Mobly names any qualifier it recognized but couldn't use.

**Leads landed but no enrichment happened.** Check the enrichment mode you picked. If it was Skip, that's expected — the leads show as "Imported" and stay that way. Change the mode on the lead if you want enrichment to run.

**Leads not showing up in the CRM.** Check the [Reconciliation](https://help.getmobly.com/help-center/integrations/crm/reconciliation.md) tab on your CRM integration. Any sync error would surface there. See also [How data flows from Mobly to your CRM](https://help.getmobly.com/help-center/integrations/crm/how-data-flows.md).

## Related articles

* [How registrants flow into Mobly (Host)](https://help.getmobly.com/help-center/host/how-registrants-flow-into-mobly.md) — same enrichment mode choice, applied to Host registrants
* [Mobly fields reference](https://help.getmobly.com/help-center/integrations/mobly-fields-reference.md) — every column the CSV template accepts and what it maps to
* [Configuring qualifiers](https://help.getmobly.com/help-center/the-hub/working-with-leads/configuring-qualifiers.md) — a qualifier must be published and on the event before you can import answers for it
* [How data flows from Mobly to your CRM](https://help.getmobly.com/help-center/integrations/crm/how-data-flows.md)
* [Reconciliation](https://help.getmobly.com/help-center/integrations/crm/reconciliation.md) — where CSV-upload sync errors surface
