Please note: This article refers only to legacy event registration data. At this time, Import Manager does not import event registration data for the Next Generation Events module.
Learn how to prepare your legacy event registration data for import in this step-by-step guide. Taking the time to properly format your data will allow you to conduct a seamless import. This help guide will cover how to prepare your legacy event registration data for import.
Recommended Reading Before You Start
Content
Preparing Your Legacy Event Registration Data for Import
Instructions
Preparing your Legacy Event Registration Data for Import
To prepare your Legacy Event Registration data for import using Import Manager, you must first have your data properly formatted in a .csv file. We will use this sample spreadsheet to demonstrate the formatting process.
Event Registration Data Import Template
Start by ensuring:
- There is only one header row
- Each column header is different
- The spreadsheet is saved as a .csv file.
In the sample we will use, there will be an account ID column. The IDs in this column can be either from your old database or Neon CRM IDs. You do not need to have an Account ID column.
Also, as you can see, our data contains the non-related data fields of First Name, Last Name, and Email. Neon CRM allows you to simultaneously import multiple types of data, so we will import this new account data along with our new event registration data in this import example.
Required Fields
When importing legacy event registration data, the following fields are required:
|
Column |
Description |
|
Cost |
If the event is new to the system, Neon CRM will create the event along with the cost and dates during the import process. |
|
Event Name |
If the event is new to the system, Neon CRM will create the event during the import process. |
|
Registration Date |
This is the date an individual registered for an event. |
Note: For information on how to manipulate spreadsheet data in Microsoft Excel, consult the Microsoft Excel support materials.
Standard Fields
For Legacy Event Registration data, there are many standard, non-required fields available for import, including:
|
Field Name |
Explanation/ Note |
|
Attended |
Did they attend the event? (1=yes, 0=no) |
|
Attendee First Name |
First name of the person who attended the event |
|
Attendee Last Name |
Last name of the person who attended the event |
|
Attendee Email |
Email address of the person who attended the event |
|
Check # |
Check number (if someone pays by check) |
|
Cost |
Amount paid to attend the event |
|
End Date |
The end date of the event |
|
Event Name |
Name of the event |
|
Event Registration Note |
Applicable staff note(s) for a specific registration |
|
Event Registration Status |
Status of the transaction |
|
Tender Type |
Method of payment for the event |
|
Registration Date |
Date the attendee registered for the event |
|
Source |
Source of the event (i.e. web) |
|
Start Date |
The start date of the event |
Although these fields are not required, entering this data now, before import, may save you time in the future.
Import Manager Limitations
For legacy event registration data, there are a number of limitations on various types of data available for import using the Import Manager, including:
- Attendee Event Custom Fields
- Event Sessions
- Events with multiple ticket prices or multiple attendees per ticket
- Multiple event attendees per registration
- Event registration data pertaining to the Next Generation Events module
If your data contains any of these data types, they will need to be removed before import.
Common Formatting Errors
There are many common formatting errors which occur when importing donation data. These include:
- Negative numbers
- Invalid file format: Neon CRM supports .csv files for import
- Incorrect date field formatting (Ex: date fields must be in MM/DD/YYYY or MM-DD-YYYY format)
- Blank required fields
- Multiple spreadsheet tabs
Note: In the Attended column, our data included a zero and a one. A one indicates the registrant attended the event. A zero indicates the registrant did not attend the event.