Completev1.2.0 · updated 2026-09-28

Upload attendees

Bring an attendee list in from a CSV or a paste, check what the file will actually do before it does it, and read the four ways a row gets rejected.

What it is

A three-step wizard — Source → Map & review → Import. You give it a file or a paste, it matches your columns to the event's attendee fields, and it shows you every row it is unhappy about *before* anything is written.

When to use it

Anything over about twenty people. It is also the safest way to update a list you already imported: matching is by email, so re-importing a corrected file updates people rather than duplicating them.

Before you start

Your attendee fields set up, if you collect anything beyond name and email. Read the guide
A CSV with a header row. One column must be the email address.

Try it — this is a sandbox, nothing here is real

Import a 312-row list that has four problems in it. Take the shortcut first if you want to see what a rushed import costs.

Step 1. A file, or a paste.

1Source 2Map & review 3Import

CSV file

Pick a .csv file — columns are matched automatically.

Email,First name,Company
[email protected],Jane,Acme

Smart paste (AI)

Paste rows — AI maps the columns to your fields.

✓Source 2Map & review 3Import

Column in your file	Maps to
First name	First name
Surname	Last name
Work Email	— not mapped —
Company	Company
Ticket	Ticket ID

Map a column to Email — it identifies each attendee.

Import cannot run

Map a column to Email — it identifies each attendee.

Without an email there is no way to tell whether a row is a new person or an update to someone already on the list. Every re-import would duplicate everyone.

312

Rows

308

Will import

Needs a look

Cannot import

Row	Email	Name	Ticket ID	Flag
14	[email protected]	Jane Tan	NS-0142	Likely duplicate of an existing attendee
87	[email protected]	Sam Ortiz	NS-0087	Duplicate in file (also row 203)
203	[email protected]	S. Ortiz	NS-0219	Duplicate in file
245	(blank)	Rae Kim	NS-0245	No email

Cells are editable here — fix row 245 without leaving the page.

I reviewed the flagged rows

310

Imported

Updated

Skipped

Row	Name	Reason
245	Rae Kim	No email

Rae Kim is not in your event

She will be told Ticket not found at the door. Nothing else will mention this again.

311

Imported

Skipped

Row	Email	Ticket ID	Reason
203	[email protected]	NS-0087	Ticket ID clash

Ticket IDs are unique per event

A ticket number is what a scanner reads at the door. Two people holding one number is not something the product can resolve on their behalf.

311

Imported

Updated

Skipped

Every row in the file landed.

Attendees
The list, with your new rows in it

Tickets by Email
Check whether one address is holding six passes

Click a control above to carry on.

Step by step

1
Choose a sourceRegistration → Upload Attendees
Pick a .csv file, or use Smart paste (AI) and paste rows straight out of a spreadsheet. Both end up in the same review grid.
Tip. Download a sample gives you a file with the right headers for *this* event, including your custom fields.
2
Check the column mapping
Columns are matched to your fields automatically. Anything it is unsure about is left unmapped rather than guessed at — you set those by hand. Re-map with AI starts the matching again if you have changed the file.
Careful. Email must be mapped. It is what identifies an attendee, so without it the import cannot tell one person from another and will not run.
3
Read the flagged rows
The grid colours anything it wants you to look at. Amber means *this will surprise you*; red means *this row cannot import*. You can edit cells right there in the grid.
Tip. Rows are also checked against the attendees already in the event, not just against each other — that is where Likely duplicate of an existing attendee comes from.
4
Confirm and import
Tick I reviewed the flagged rows and run it. You get a tally of Imported / Updated / Skipped, and every skipped or failed row is listed with its reason.
5
Come back to the batch later
Every run is kept. Open it from the imports list to see exactly which rows went in, what was updated, and what was rejected — long after the toast has gone.

When it goes wrong

Every one of these has happened to someone. Symptom first, because that is what you will have.

No email column mappedblocker

What you see: Map a column to Email — it identifies each attendee. The import will not start.

Why: Email is the identity of an attendee. Without it the wizard cannot tell a new person from an update to an existing one.

Fix: Map any column holding addresses to Email in step 2. If your file genuinely has no addresses, you cannot use ticket-based sign-in with that list — see the sign-in methods first.

Rows were skipped and nobody noticedwarning

What you see: The import reports success, but the attendee count is lower than the row count, and someone is missing at the door.

Why: Flagged rows do not stop the run — they are skipped and listed. If you leave the results screen without reading the Skipped list, the record of it only survives in the batch.

Fix: Read the Skipped tally before you leave. If you already left, open the batch from Upload Attendees — it lists every rejected row and its reason permanently.

Ticket ID clashblocker

What you see: A row is skipped with Ticket ID clash.

Why: Two rows in the file, or a row and an existing attendee, carry the same ticket number. Ticket IDs are unique per event because a door scanner resolves a person from one.

Fix: Give each person a distinct ticket number and re-import. If your ticketing system reused a number, fix it there first — the clash will come back on the next export.

Likely duplicate of an existing attendeegotcha

What you see: An amber row says the person is already on your list, by name.

Why: The name matches someone already in the event but the email does not — usually a personal address on one list and a work address on the other.

Fix: Decide which address is the real one and correct the cell in the grid. Importing both creates two attendees, two badges and two sets of session bookmarks.

Afraid to re-import a corrected filegotcha

What you see: You have a fixed CSV but do not want to double everyone.

Why: Reasonable caution — but matching is by email, not by row.

Fix: Re-import the whole file. Rows whose email already exists are updated; only genuinely new addresses are added. The result tally shows the split. An update only changes what the file says: blank cells, and everything the file has no column for — registration status, answers people gave when they registered, privacy choices, ticket numbers already printed on badges — are kept.

AI mapping failed — mapped automaticallygotcha

What you see: A notice says the AI mapping did not run.

Why: The AI assist was unavailable; the wizard fell back to plain header matching.

Fix: Nothing is broken — check the mapping table yourself and set anything left unmapped. Re-map with AI retries.

What people ask

Kept in the words people use, because that is what you are about to type.

Excel file?

Save it as CSV first, or copy the rows and use Smart paste (AI).

Can I import custom fields?

Yes — any field you defined under Attendee Fields appears in the mapping list. Download a sample includes them as headers.

How do I undo an import?

There is no single undo. Attendees deleted from the list go to the Recycle Bin, so a wrong import can be cleaned up from there.

attendees attendee fields tickets by email

What it is

When to use it

Before you start

Step by step

When it goes wrong

What people ask

Next