SuperUser only: supported ticket imports instructions
Supported imports does NOT mean that customer sends us a spreadsheet and it's on us to import their data - we will reformat their spreadsheets - but NOT clean up their data. Once the spreadsheet is finalized, we'll handle the upload for them.
Use your best judgment re: when to kick it back to the customer and when it's easier to do it yourself than explain what needs to be done. My general rule is it's usually easier for me to paste existing data into new columns/empty cells (when the data is already present on the spreadsheet)- but I won't add/edit data that I'm not 100% sure is accurate.
Ticket Imports that are intended to create viable orders - including buyers, ticket price, amount paid, guests/unassigned tickets - are difficult - but here are tricks to make it less painful:
Instead of trying to provide written instructions for reformatting, provide them a visual example they can refer to
- Start by re-ordering their spreadsheet columns to the logical order: Buyer Info > Ticket Info > Guest Info > UDFs. This will help you make sense of what they have, what they're trying to do, and what needs to be added/changed.
- Add any columns for data they'll need (usually to correctly build orders)
- Highlight (red) any columns that can't be imported
- Reformat the data in as many rows as needed to provide examples for each existing scenario (single vs multi-seat tickets, paid/unpaid, unassigned guests etc) - then highlight them in green.
- Return the updated spreadsheet to the customer, along with simple, step by step instructions on what they need to add/rework - referring to the exact spreadsheet column names.
Adv. Import Format:

- Ordered Buyer Info > Ticket Info > Guest Info
- Note that the first 5 columns (Buyer name, ticket id/name/admits/price) contain IDENTICAL data for each row pertaining to that ticket (2 rows for couples etc). The ONLY buyer/ticket element that is different on the pertaining rows is Paid Amount (see below).
- Don't divide the ticket price/admits data for multi-seat tickets - if a Couples ticket admits 2 and costs $200 - those are the amounts listed on every row.
- Price/paid columns. If Price column is omitted, or cell is empty - rows will import as $0 price. If Paid column is omitted, or cell is empty - rows will import as paid. If spreadsheet contains price and paid columns - record the price paid for a multi-seat ticket on one row only - then be sure remaining rows contain 0 - otherwise, each empty row will create a separate payment on the order.
Bidder Numbers/linking users:
There are two ways to specify bidder numbers/linking during import:
- Add a column for either Link ID or Bidder Numbers and provide the same number for linked guests, and different numbers for unlinked guests.
- Verify/Set-up matching ticket types on the event site for each ticket name being imported (with sufficient qty and specifying link status) - then the import will assign bidder numbers the same as online/internal ticket sales.
Other important rules/useful tips:
- Link ID and Bidder Number columns work similarly to assign bidder numbers - the only difference is that link id assigns next available number rather than the specified number. The advantage of using Link ID: the importer won't skip any rows in the event one or more bidder number are already in use on the site.
- If ticket buyers are also guests, you only need to provide the buyer name - the importer will use the more complete guest columns for the buyer/guest user record.
- Verify the exact name/set-up of any existing ticket types on the site to avoid having the importer create new, unwanted ticket types.
- For complex imports, It's always a good idea to import the data on a test site first - then you can verify that the orders were created correctly. Do NOT upload to a public sandbox/demo site - and remember to undo the import from test site when you're done to remove their supporters personal info.