Now that you've set up your events in their spreadsheet, it's time to move on to tickets! Tickets in Novi are what we use to differentiate the types of registrations you have for each of your events. For example, you may have member tickets, non-member tickets, early-bird tickets, etc.
Each of your events that you will be importing attendees into will need a ticket(s) attached.
Importing tickets allows you to see that John Smith didn't just go to your event, he registered as a member for the event. However, some associations don't necessarily feel the need to get into that level of detail. They just want to see that John Smith was registered. In that case, you'll still need to import a ticket, but it can just be one ticket per event, named something like "Import" at $0.
Below, we'll dive in to the columns listed in a ticket import spreadsheet. Remember, events and attendees will be in their own, separate sheets. Each section below represents a column that can be imported via Excel spreadsheet. Required columns are noted as such. The order listed below is the preferred order of the columns.
*Required. All tickets will need their own unique IDs. You won't see this ID again - it's solely for import. Most commonly, the event name + the ticket name is used for the ID for ease (Fall Conference Member). We can handle this column if you're unsure.
*Required. This is the unique ID that you gave your event in the first spreadsheet. Remember that most associations simply use the event's name as the ID for ease. Each event needs a ticket(s) if you will be importing attendees into it.
*Required. This is the name of the ticket at it should appear in Novi. This is where you'd distinguish between member, non-member, early-bird, spouse, etc. (Or, refer to scenario where you don't need this level of detail in opening section.)
*Required. This is the price of the particular ticket at hand. If you do not have this information, simply put 0. Remember - event imports do not touch, create, or affect transactions. We ask this information so that if you will be registering people for the event via Novi in the future, this is already there.
This is the QuickBooks Item that the ticket will be attached to, so if you have people register for the event in the future, the system knows where the money goes. This can be added or updated inside of Novi later. This is mainly only used for tickets on events that have not happened yet.
This is the QuickBooks Class, if you track that information, that the ticket will be attached to. This can be added or updated inside of Novi later. This is mainly only used for tickets on events that have not happened yet.
If you track Continuing Education Units, simply add a column to your spreadsheet called CEUs and add a "Yes" to any tickets that units were tracked on. You can list the specific amount on the attendees in the next spreadsheet (attendees). Note, we cannot currently change the name of this field.
You may add columns to this spreadsheet to represent any custom fields that you need to import relating to events. (To clarify - only events that you are importing. You can always add new custom fields later.)
For example, you may need to collect information about Dietary Restrictions on a particular event. Add a column named Dietary Restrictions, and add a "Yes" next to any ticket that needs this information attached to.