CSV reference.
Every column read on import and written on export.
Every column this platform reads on import and writes on export, in one place.
Guest import
A sample is downloadable per ticket tier from the guest list, under Tools, then Upload CSV. Each row names its own tier in ticket_id, so one file can carry several. See importing guests.
| Column | Required | Notes |
|---|---|---|
ticket_id |
Yes | The tier's numeric id. Pre-filled in the sample. |
ticket_type |
Yes | The tier's name, for readability. |
billing_first_name |
Yes | The contact responsible for the registration. |
billing_last_name |
Yes | |
billing_email |
Yes | Must be a valid email address. |
attendee_first_name |
Yes | The person attending. |
attendee_last_name |
Yes | |
attendee_email |
Yes | Must be a valid email address. |
After those, one column per question in that tier's fieldset, headed by the field key rather than the label. Select answers must match one of the option values.
If the attendee paid for themselves, repeat the same values in both sets of columns.
Schedule import
Downloaded from the schedules page. See schedules.
| Column | Required | Notes |
|---|---|---|
name |
Yes | The session name. |
location_id |
Yes | The numeric id of a saved location, not its name. |
start_date |
Yes | YYYY-MM-DD. |
end_date |
Yes | YYYY-MM-DD. |
start_time |
Yes | 24-hour time. |
end_time |
Yes | 24-hour time. |
details |
No | Notes shown with the schedule. |
is_published |
No | Whether it appears on the public page. |
is_check_in_enabled |
No | Whether the scanner accepts it. |
sort_order |
No | Display order, lowest first. |
Guest sheet export
One CSV per ticket tier, inside a zip. See exports.
| Column | Contents |
|---|---|
first_name, last_name, email |
The attendee. |
ticket |
The tier name. |
qr_code_url |
The address of this guest's QR code. |
source |
How the guest arrived: the event site, or manual. |
registration_date |
When the guest record was created. |
amount_paid |
The amount in major units of the team's billing currency. |
payment_status |
The payment state of the registration. |
archived |
Yes or No. |
| One per fieldset question | Headed by the question's label. |
checked_in: <schedule name> |
The check-in time for that schedule, blank if they did not attend. |
Order sheet export
One CSV, one row per order line. See exports.
| Column | Contents |
|---|---|
order_reference |
The short reference the buyer and the Orders page quote. |
order_id |
The order's numeric id. |
order_status |
paid, pending, free, partially_refunded, refunded, rejected or expired. |
placed_at, completed_at |
When the order was placed, and when it was paid. Blank if not yet paid. |
order_source |
public, panel or backfill. |
currency |
The order's currency code. |
billing_first_name, billing_last_name, billing_email |
The billing contact. |
payment_method |
The payment option used, for example Manual or the gateway's name. |
payment_reference |
The gateway's own id for the payment. Blank for offline payments. |
order_total |
What the order is for. |
order_collected, order_refunded, order_net |
Money settled in, money returned, and the difference. |
order_outstanding |
What is still unpaid. |
line_number |
The line's position in its order, from 1. |
attendee_first_name, attendee_last_name, attendee_email |
The attendee the line is for. |
ticket |
What was bought. |
quantity, unit_price, line_amount |
The line as billed. |
line_collected, line_refunded |
Money settled against this line, and returned from it. |
line_status |
paid, unpaid, free or refunded. |
Amounts are in major units of the order's currency, with no thousands separator. The order_ columns repeat on every row of an order, so total the line_ columns.
Schedule attendance export
Downloaded per schedule from the door desk.
| Column | Contents |
|---|---|
first_name, last_name |
The attendee. |
email |
Blank where no email is on file. |
ticket |
The tier name. |
checked_in_at |
When they were checked in. |
General rules
- Files are comma separated, with a header row.
- The header row must match exactly. Extra columns the importer does not recognise are treated as custom fields.
- Blank optional values are allowed. Leave the cell empty rather than writing
null. - An import shows you a preview of every row, with problems flagged, before anything is created. Use it. Re-uploading a corrected file costs nothing.
Last reviewed August 21, 2026