Skip to main content

Importing tickets

Import ticket codes and ticket buyers into Stager.

Updated over a week ago

You can find the Ticket Importer under Ticketing → Ticket Importer.

Are you just starting with Stager and want to import tickets that were sold through your previous ticketing system? Or have you sold tickets via multiple Stager accounts and want to scan everything with one account? The ticket importer can save you a lot of work.

If you add the ticket buyer’s name and email address to the import file, Stager will automatically create the ticket buyer as a contact and include the order details. This makes it easy to find them later and email them if, for example, you need to send extra information about an event they bought tickets for.

First, use the ‘Single Ticket Code’ function to verify that the ticket code format is correct. Import one sample ticket code into a test event, then open the Stager app or go to Door Sales → Scan Tickets and scan the original printed ticket. If the ticket is accepted, you can continue by using the Multi Ticket Importer to upload the remaining codes.

⚠️ Make sure to import each barcode only once per Stager environment, as every barcode must be unique.


Multi ticket importer

When you want to import multiple tickets, open the Multi Ticket Importer page by selecting '+ New Ticket Import' → 'By .csv'.

Select the correct event and choose whether you want to continue importing when the total number of tickets you set on the tickets tab of the event is reached (choose 'Enabled') or whether you want the import to stop when there are no available tickets left (then choose 'Disabled').

Download the sample CSV and use it to add the ticket codes, the names of your ticket buyers and their email address. Save as .csv and drag the file to the white upload box.

Check on the next page whether the correct data is in the correct column. Yes? Then you are ready to import!

The contacts that did not previously have a record in Contacts have been created and can be found via Marketing - Contacts, provided an email address was entered. The order can be found under Contact → Orders. The import date will be shown as the order date.

Imported tickets appear in the Tickets tab of an event, highlighted in yellow.
If you import more tickets than the event’s set capacity, the number shown in the ticket sales status may exceed the 'total number of tickets'.


Single ticket importer

You import one ticket code using the single ticket importer. Here you select the event, add the ticket code and choose whether or not you want new tickets to be created when there are no available tickets for that event.

In the Single Ticket Importer you can find all imported tickets.
When you select an event, you will see an overview of the imported tickets, both those uploaded via a CSV file using the Multi Ticket Importer and those added individually through the Single Ticket Importer.


Previous imports

Under Previous imports you can find an overview of all completed .csv imports. View the status and which ticket codes have been imported by clicking on the blue link under Tickets. If you want to see which contacts have been imported, click on the link under Contacts. If the number of 'imported' differs from the 'total', it is because the contacts already existed in your Stager account and did not need to be imported.


Spaces and signs (+ - =) in barcodes

Some ticketing parties also know the space as a character that can be part of the ticket code. Stager recognizes the space as a separate character if these tickets are scannable with the Stager app. However, the barcodes that start with a space must be imported manually. Barcodes that start with a space as the first character will not be imported correctly when using the multi-ticket importer. Spaces in the middle of the code or at the end do not present a problem.

If a barcode starts with a plus, minus or is sign (+ - =), then Excel must put an apostrophe before this sign, to convince Excel that this is a code and not a formula. Importing does not cause any specific problems, but we advise you to always test a number of printed tickets before the event starts.

Did this answer your question?