Written by Jeff Blake Updated May 28, 2026

A CSV import brings an existing attendee or ticket list into an event for check-in. You upload a spreadsheet, map each column to a field, and Guest Manager creates the tickets. This is the bridge for guest lists from a planner, a registration tool, or another ticketing platform.

Requirements: An event to import into. A file saved as CSV (UTF-8). Imports over 100 rows need an approved account — see the FAQ.

Upload the file

1. Open your event and go to its Imports section.

2. Start a new ticket import, select your CSV file, and submit. A sample file is offered on the import form — download it to see the expected layout.

3. If every column header is recognized, the import starts immediately. If any header is unrecognized, the Map your data screen opens.

4. On Map your data, set the field for each column. To skip a column, open its dropdown and choose Do not import (or select it and press Delete). Submit to start the import.

The import runs in the background, and the tickets appear in the event’s attendee list when it finishes. To undo an import, open its results and revert it; reverting deletes the records that import created.

How columns are matched

Columns can be in any order and named anything — you map them on the Map your data screen. If you name a column to match a field below, it is pre-mapped for you, which reduces errors. Headers are matched case-insensitively. Any column that doesn’t match a known field still appears on the mapping screen, where you assign it by hand or import it as a custom field.

Column reference

Attendee identity

• Name — the attendee’s full name, or split into First Name and Last Name. Using any of these also creates a contact record (a reusable profile for that person). To skip contact creation, use Ticket Name (or Ticket First Name / Ticket Last Name) instead — these set the attendee name without a contact.
• Email — assigned to the contact. A contact email must be unique, and it links to whichever name shares its row. Ticket Email is the forgiving alternative: it attaches the email to the ticket only, may repeat across rows, and skips contact creation.
• Phone Number — assigned to the contact. Ticket Phone Number attaches to the ticket only; pair it with Ticket Phone Number Country for a non-default country.
• Member ID — a unique identifier stored on the contact (member number, student ID, badge number). An existing contact found by the same email, phone, or Member ID is updated rather than duplicated.

Ticket

• Barcode — the ticket’s barcode. Provide this to import tickets that already carry their own barcode numbers — pre-printed tickets, or barcodes exported from another system. Barcodes are 2 to 255 characters. A row whose barcode matches an existing ticket in the event updates that ticket in place instead of creating a duplicate.
• Quantity — number of tickets to create from the row. Leave Barcode blank when using Quantity; you can’t combine a quantity above 1 with a single barcode.
• Kind — ticket or pass. A pass is reusable across the dates of a multi-date event; a ticket is single-use. Leave blank for a normal ticket. See Scan validity rules and multi-use passes.
• Ticket Type — segments attendees and is visible to them; each ticket type can carry its own design and check-in rules. A ticket type matched by name is reused; an unmatched name creates a new one.
• Expires At — the date after which the ticket no longer scans valid.
• Send Email — set to Yes to email the ticket to the attendee on import. The row needs an email address, and your account must be approved to send. See the FAQ.
• Photo — a URL to a JPG or PNG; the image is downloaded and stored on the ticket.
• Notes, Tags (comma-separated), and Guests (comma-separated names, which create a party under one ticket) are also recognized.

List

• List — an event-specific segment (VIP, Sponsor, Press). A list matched by name on the event is reused; otherwise a matching permanent list on your account is added to the event, and failing that a new list is created. Rows with no List column go to the event’s default list.

Address

The contact’s address maps from Country and State (ISO two-letter codes, e.g. US, CA), Address, City, and Zip Code.

Custom fields

Any extra column (for example Title or Company) becomes a custom field. Map it to a ticket custom field on the Map your data screen — not to a contact field — unless you intend it to live on the contact.

Advanced columns

These columns target session-based and conference setups, and most require setup before importing.

• Vouchers — pre-allocate voucher types that an attendee can redeem for entry to specific sessions. Set up your voucher types in the event’s Design and setup before importing.
• Pickups — allocate a quantity of an item (meal, t-shirt, parking) per attendee. Define the items first; see Product pickups for the column-per-item layout.
• Session — pre-create session tickets for an attendee who already knows which sessions they’ll attend. Name the column to match the session exactly; each row’s value is a quantity (usually 1).
• Registration — for a session ticket, the barcode of the parent registration it belongs to. Advanced use.
• Party Grouping Identifier — groups rows that share a value into one party under a single primary ticket, so a family or group is created together.

Related articles

• Collecting custom fields — make imported custom columns appear at check-in and in the attendee list.
• Attendee export and email campaigns — export your current list to re-import for updates, and email a guest list.
• RSVPs — collect free responses with a public form instead of importing.
• Product pickups — allocate items to attendees with a quantity column per item.
• Scan validity rules and multi-use passes — how the pass kind behaves across multiple dates.

FAQ

Why won’t my Excel file upload?

You can only upload a CSV, not an .xls/.xlsx workbook, and it must be saved as CSV UTF-8 (Excel offers two CSV options — pick UTF-8, under “Common Formats”). If a UTF-8 error persists, open the sheet in Google Sheets and export to CSV from there.

Can I import from Ticketmaster, Skiddle, or another ticketing platform?

There is no direct integration, but any platform that exports its data works through CSV. Export your list with a Barcode column (and a Ticket Type if you want them segmented), then import. The iOS scanner recognizes those barcodes at the door. The barcode value must export as actual text — if the source only renders a barcode image without an exportable value, there is nothing to import.

How do I update tickets I already imported?

Export your attendee list, trim it to Barcode plus the columns you want to change, and re-import. Rows whose barcode matches an existing ticket update in place rather than creating duplicates.

How do I undo a bad import?

Open the import’s results and revert it, which deletes the records that import created. If you’ve navigated away, bulk-delete the imported tickets from the attendee list instead.

My Send Email column isn’t sending tickets — why?

The value must be exactly Yes, the row must have an email address, and your account must be approved to send email. To send one consolidated email per contact (rather than per ticket) after import, use a campaign instead — see Attendee export and email campaigns. If a custom field named “Send Ticket” exists, delete it under your ticket-field settings, as it can interfere.

Will imported tickets show up in Shopify Orders?

No. An import creates tickets directly and never creates a Shopify order, so imported tickets appear only in the Guest Manager attendee list and do not change Shopify inventory. For check-in, scan them with the iOS app, or use the POS check-in action — POS order lookup won’t find them because there is no order.

Why does my import need approval?

Uploads over 100 rows are held pending account approval to prevent spam. Approval is automatic once you subscribe to a paid plan or buy a credit package. Otherwise, message support with a note about your event for a manual approval, which is usually quick.