---
name: crm-event-import
description: Plans and prepares CRM imports for event data. Designs a Salesforce campaign with one consistent campaign member status set (Registered, Attended, No Show, Visited Booth, Meeting Held, with the right ones marked Responded) or the HubSpot equivalent (event status property, static lists, marketing events), maps file columns to CRM fields, matches existing leads and contacts, and outputs import-ready files with a pre-import checklist. Use for Salesforce campaign member status setup, event lead import, HubSpot list import or fixing event attribution data.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: leads-and-follow-up
  source: https://eventmarketingsoftware.com/skills/crm-event-import
---

# CRM event import

Get event registrants, attendees and leads into the CRM in a way that reporting can trust: one campaign per event, one campaign member status set across all events, existing people matched instead of duplicated, and import files that load cleanly the first time.

The status set and terms are in [references/shared-terms.md](references/shared-terms.md). Typical inputs: a registration or attendance export, the clean file from badge-scan-cleanup, or the scored file from event-lead-scoring.

## Intake

1. Read `event-context.md` (or `event-program-context.md`) if present: CRM, campaign naming convention, status set, parent campaign, lead source values, owners.
2. Ask for what's missing, in one message:
   - Which CRM (Salesforce, HubSpot, other) and who will run the import (admin or marketer, which tool).
   - The files: registration export, attendance or check-in export, badge scans, meetings list.
   - Event name, type (trade show, conference, user conference, webinar, field event, dinner), dates, region, cost if they want it on the campaign.
   - Existing naming convention and status values, or a field list (pasted or through a connector).
   - Whether this is one event or a scheme for several.
3. If the user wants a scheme for several events, design the scheme first (step 1) and stop for approval before building files.

## Connectors (optional)

- **Salesforce or HubSpot connector**: read field lists, picklist values, existing campaigns, and look up existing leads and contacts by email. Create or update anything only after the approval gate.
- **Google Sheets connector**: read exports and write import files to new tabs.
- **Otherwise**: ask for an export of existing emails (leads and contacts) for matching, and return import-ready CSVs.

## Method

### 1. Design the campaign and status scheme
- **Naming**: propose `YYYY-MM_Type_EventName_Region`, e.g. `2027-03_TradeShow_ExampleExpo_NA`. Keep the user's convention if they have one.
- **Hierarchy (Salesforce)**: a parent campaign per program or fiscal year (e.g. `FY27 Trade Shows`), one child per event. For big events, optional children per activity (booth, dinner, sponsored session) only if they'll be reported separately.
- **Status set**: use the standard campaign member status table in shared terms, marking Attended, Attended On-Demand, Visited Booth and Meeting Held as Responded. Use only the statuses this event needs, but never rename them per event.
- **HubSpot**: no native campaign member status. Use a contact property for event status with the same values, a static list per status, and the marketing events object if the portal uses it. Details in [references/hubspot-setup.md](references/hubspot-setup.md).
- Salesforce setup steps are in [references/salesforce-setup.md](references/salesforce-setup.md).

### 2. Assign a status to every person
- Map export fields to statuses using [references/status-mapping.md](references/status-mapping.md) (e.g. registration status Confirmed and Checked In = Yes > Attended).
- One status per person per campaign. When several apply, keep the most advanced (order in shared terms) and keep the other facts in columns.
- Badge scans at a third-party show: Visited Booth. Meetings: Meeting Booked or Meeting Held from the meetings list.
- Count people per status and show the table before going on.

### 3. Map columns to CRM fields
- Build a mapping table: source column, CRM object and field, transform, required yes/no, notes. Field maps are in [references/crm-field-map.md](references/crm-field-map.md).
- Picklist fields (Lead Source, Country, Industry, Status) must use exact existing values. List any value that doesn't exist yet and ask whether to map it or have an admin add it.
- Carry `lead_tier`, `tier_reasons` and `owner` from event-lead-scoring into custom fields if the user has them; otherwise into a description or notes field.

### 4. Match existing records
- Match on email (lowercased) against contacts first, then leads.
- **Existing contact**: don't create a lead. Add the contact as a campaign member.
- **Existing lead**: update only empty fields unless the user says otherwise; add as campaign member.
- **New**: create a lead (Salesforce) or contact (HubSpot).
- Same email on several CRM records: flag `crm_duplicate` and leave for the admin.
- Never overwrite owner, lead status or lifecycle stage on existing records unless the user explicitly asks.

### 5. Build the import files
Salesforce:
1. `sf_leads_new.csv`: new leads with required fields (Last Name, Company), Lead Source, owner.
2. `sf_leads_update.csv`: existing leads, only fields to fill, with the Lead ID if known.
3. `sf_campaign_members.csv`: Campaign ID or name, Lead ID or Contact ID (or email for the wizard), Status.
HubSpot:
1. `hs_contacts.csv`: email plus properties, including the event status property, ready for the contacts import with "add to a static list".
2. One file per status if the user prefers a list per status.
Any CRM: `import_exceptions.csv` with every row held back and why.

Salesforce has three common routes: the Data Import Wizard (launched from the campaign's members list it can add leads and contacts to the campaign, and the lead import can assign leads to a campaign), "Add to Campaign" from a report or list view (lets you pick the member status for existing records), and Data Loader (load leads first, export the new IDs, then insert CampaignMember rows with CampaignId, LeadId or ContactId, and Status). Wizard options change between releases, so confirm the member status step in the user's org. Ask the admin to confirm the lead matching rule checks contacts as well as leads, or the import can create duplicates.

### 6. Pre-import and post-import checks
Use the validation checklist below. After the import, compare CRM counts per status with the status table.

## Output

**1. Campaign design**

| Item | Value |
|---|---|
| Campaign name | |
| Parent campaign | |
| Type | |
| Dates, region, budgeted cost | |
| Status set (Responded) | |
| Default status | |

**2. Status counts**

| Campaign member status | Responded | People | Source of truth |
|---|---|---|---|

**3. Field mapping table**

| Source column | CRM object.field | Transform | Required | Notes |
|---|---|---|---|---|

**4. Import files** as listed in step 5, plus `import_exceptions.csv`.

**5. Pre-import checklist and import steps**, numbered, for the tool the user will use.

A worked example, built from `assets/sample-registrations.csv` and `assets/sample-crm-records.csv`, is in [references/examples.md](references/examples.md).

## Validation checklist

- [ ] Every person in the source files appears in exactly one import file or in the exceptions file.
- [ ] Status counts add up to the number of unique people.
- [ ] No email appears twice in a file.
- [ ] Existing contacts aren't in the new-leads file.
- [ ] Required fields are filled; picklist values match existing values exactly.
- [ ] Responded statuses are exactly the ones in the design.
- [ ] Dates use the format the import tool expects (ISO 8601 unless told otherwise).
- [ ] EU/UK contacts without opt-in aren't marked as opted in or added to marketing lists.

## Approval gates

- Show the campaign design and status set and get a yes before creating anything.
- Before any connector write (create campaign, create statuses, create or update records, add members), show a preview: object, number of records, sample rows, fields changed. Get an explicit yes. Load a test batch of 5 to 10 records first, check them, then the rest.
- Default to producing files for the user or their admin to import.

## Privacy and consent

- Keep personal data inside the user's own files and CRM.
- Don't map a badge scan or registration to marketing consent unless the source shows an explicit opt-in. Carry consent fields as they are.
- Flag EU, EEA and UK records without opt-in in the exceptions or with a field so they don't land in marketing lists.

## Pushback

- "Make a new status for this event": suggest using the shared set so reports compare across events; add a custom status only if it'll be reported, and add it to every event.
- "Just import everyone as new leads": explain that existing contacts become duplicate leads and break account reporting; match first.

## Related skills

badge-scan-cleanup (clean first), event-lead-scoring (lead tier and owner fields), no-show-recovery (uses the No Show status), webinar-attendee-scoring (Attended and Attended On-Demand).
