Import Tickets

Modified on 11 March

You can import tickets that you've sold offline (via check or cash, or via another platform) to your TicketSignup ticket event. Ticket imports are also a great way to generate tickets for sponsors or employees in some scenarios.

Choosing your import method

There are two ways to import: Manual and Bulk (via CSV). Manual imports are done in the dashboard and allow you to input one ticket purchase at a time (ticket purchases can contain multiple tickets under the same name and email address). Bulk imports are done via CSV upload and can import many offline purchases in just a few steps. Bulk imports are better if you need to import more complicated information, like names and ages for each person associated with each ticket in a purchase.

To import tickets, start at Tickets >> Ticket Imports in your dashboard.

Manual Ticket Import

Manual ticket imports are done at the purchase level, meaning that you will enter contact information for a ticket purchaser and then add their tickets to that purchase. This means that you can associate many tickets to a single ticket purchaser if needed.

First, add the contact information for the ticket purchaser. Then select the tickets that you would like to add to their purchase. Note that you can add multiple ticket types to a single purchase by clicking the green Add Ticket button. The Paid Amount will adjust based on the quantity of tickets purchased and the pricing you have set for each ticket. (Note that this assumes offline payment has been collected for these imports. This will show in your reports. You can change it to $0 or any other amount if needed).

If you'd like to automatically send a confirmation email to the email address you've imported, check the box for Send confirmation notifications to ticket purchaser. This will send a confirmation email with a QR code for checkin and a copy of the information you've imported to the person immediately. (You will also be able to do this later by using Resend Confirmation Email on the purchase details page for this ticket purchase.)

Once you have added your tickets, click Continue. 

If you are collecting per-ticket information (like name, email, or age for each ticket in addition to the purchaser's info), those additional per-ticket data collection fields that you have enabled will show so you can enter any information you have. Click Save once you have entered Per Ticket Information.

When you click Save, the form will refresh so that you can import more tickets. You’ll see a success message at the top of the screen indicating that your import was successful.

CSV Import

For CSV Imports, you will use a CSV and column matching to import your ticket data.

The recommended columns to import are: 

Contact First Name: Required. This is the first name of the ticket purchaser you are importing.

Contact Last Name: Required. This is the last name of the ticket purchaser you are importing.

Contact Email: Required. This is the email address of the ticket purchaser you are importing.

Ticket Name: Required. This is the ticket that they purchased. This corresponds to the tickets you have created in the system, so use the same names for tickets here that you used when you created your ticket groups and levels. 

Ticket Quantity: This is the number of tickets (of the type in the Ticket Name column) that they purchased. 

Ticket Amount Paid: This is the amount of any offline payment you'd like to record for this purchase. 

Ticket Purchase Date: This is the date of their purchase. If you don't use this column, the import date will be used in your reports.

You can import purchases under the same name and email address in separate rows. They will be grouped together as a single purchase after the import if their data is the same for the First Name, Last Name, and Email columns. This is how you would import a purchase that includes more than one ticket type. 

You can also import per-ticket information in addition to the purchaser information. If you are requiring names, ages, or contact info for each individual ticket to the event, you may have this information to import. This example is of importing a file from another ticket platform. There is data for both ticket holders and the ticket purchasers as highlighted in the image below. 

Once you have your CSV of data, drag and drop your CSV file, then press Continue.

This will take you to a column matching page. The system will auto-match the columns in your CSV to the fields in your ticket event. You can review the matches and make any updates by selecting a new field from your CSV file. Note that the Contact fields are equivalent to Ticket Purchaser or Buyer.

After you have confirmed your CSV headers match the data in TicketSignup, click Continue. You’ll be asked to confirm whether your CSV upload file contains headers. In this example, the file contains headers in the first row so I will leave this setting checked.

You'll see a checkbox that you can use if you'd like to send out confirmation emails automatically to the email addresses you've imported. 

Finally, you’ll match the ticket names from your imported file.

Click the Import button to upload your file.

Finally, you’ll get a success message. You can navigate anywhere on the dashboard, or view the ticket purchase or ticket report. The data from your CSV file will indicate that the ticket (or purchaser) was Imported. If you imported an amount paid for offline ticket purchases, the amount will show in the Offline Payment column. If you have caps enabled for your tickets, the number of tickets remaining will be reduced by the imports.

Ticket CSV imports make it easy for nonprofits to transfer large amounts of offline ticket purchases into any TicketSignup ticket event. 


Reports for Ticket Purchases and Individual Tickets will show all imported tickets. You can use the Offline Payment column and the Imported column to determine which tickets have been imported.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article