How to prepare tickets for import

Most platforms let you download sold tickets as a spreadsheet or CSV. Names and menus differ, but you are looking for a row-per-ticket export that includes at least a stable ticket identifier and something that identifies which product or tier each row belongs to.

Before you leave the export screen:

• Prefer UTF-8 encoding so names and special characters import cleanly.
• Keep one ticket per row (no merged cells or subtotals in the data rows).
• Note how ticket types are labeled in the file; those labels must be mappable to your event’s ticket types in step 4.

Imports always run in the context of a single event. Run through the create-event flow so the event has the correct location, dates, and ticket types that match what you sell. See How to set up an event for the full wizard.

When the event exists, open it in the web app and go to Tickets, then start Import tickets. You will choose ticket source, which date(s) the file applies to, the file itself, and then the mapping screens shown in the video.

Your ticket sources and ticket types must already exist under the account; the import UI only maps CSV data to what you configured during setup.

The import wizard expects to map your file to these system fields:

• Ticket ID (required): the unique code or number printed on or embedded in the ticket.
• Type (required): a column whose values identify the ticket tier or product; you will match each distinct value to an event ticket type.
• Ticket Holder and E-mail address (optional): map if present, or mark as not in the file.

Every selected ticket type for the event should either appear in the file or be explicitly skipped for that import, so the wizard can confirm coverage.

For a minimal file layout, you can start from the site’s example CSV. Barcode expectations for scanning are summarized on the barcode formats page.

In the import flow you will:

• Upload the CSV and pick the ticket source that describes where these rows came from.
• Select which event date(s) this batch applies to.
• Map each CSV column to Ticket ID, Type, and optional fields.
• Map each distinct type value in the file to one of the event’s ticket types.
• Review and confirm; the app then creates tickets ready for validation.

If something fails, fix the file or mapping and upload again; avoid duplicating ticket IDs across imports unless your process allows it.

• Import blocked or incomplete mapping: ensure Ticket ID and Type are both mapped, every type value in the CSV is linked to a ticket type (or marked not in this import), and a source plus at least one event date are selected.
• Type labels do not match: align spelling with ticket type names in the event, or normalize the CSV before upload.
• Wrong or missing source: create the ticket source under account setup first, then retry import.
• Strange characters in names: re-export as UTF-8 or save the CSV as UTF-8 from your spreadsheet tool.

• Ticket types on the event match what you sell and what appears in the CSV.
• Ticket source exists in the account before import.
• Header row is a single line of column names; data starts on the next row.
• Ticket IDs are unique for this import batch.