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 an .xlsx (Excel) or .csv file. (Please note: The Import Manager, after you answer the first few questions in the process, will generate a personalized spreadsheet template for you to use with instructions for each field value. While you may use your own configured spreadsheet, it is highly recommended you use this CRM-generated template to ensure all data is properly formatted for a seamless import.)
For any spreadsheet you use for import, ensure:
- There is only one header row (the names of CRM fields as listed in the Standard Fields section below).
- Each column header is different
- The spreadsheet is saved as an .xlsx (Excel) or .csv file.
Required Fields
When importing legacy event registration data, the following fields are required:
|
Column |
Description |
|
Event Name |
The event name. If the event is new to the system, Neon CRM will create the event during the import process, or you may create the event prior to importing your data. |
|
Event Registration Amount |
The cost of the event. |
|
Event Registration Date |
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 |
Required Field? |
|
Attended |
Optional. Enter "Yes" for attended or "No" for not attended. |
|
|
Attendee First Name |
Optional. First name of the person who attended the event |
|
|
Attendee Last Name |
Optional. Last name of the person who attended the event |
|
|
Attendee Email |
Optional. Email address of the person who attended the event |
|
|
Check Number |
Optional. Check number (if someone pays by check) |
|
|
Custom Fields |
Optional. See the Custom Fields section. |
|
|
Event Name |
The event name. If the event is new to the system, Neon CRM will create the event during the import process, or you may create the event prior to importing your data. |
Yes |
|
Event Registration Amount |
The cost of the event. |
Yes |
|
Event Registration Date |
The date an individual registered for an event. |
Yes |
|
Event Registration Note |
Optional. |
|
|
Event Registration Status |
Optional. Indicates the status of the registration payment (ex: pending, succeeded, cancelled). |
|
|
Event Start Date |
|
Required only if the event does not already exist in Neon CRM. |
|
Event End Date |
|
Required only if the event does not already exist in Neon CRM. |
|
Non-Deductible Amount |
Optional. The amount of the event that is not tax deductible. |
|
|
Non-Deductible Amount Description |
Optional. A description of the non-deductible portion of the event cost. |
|
|
Registration Source |
Optional. The origin of the registration (ex: social media, appeal letter). |
|
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:
- Legacy Event Sessions
- Legacy Events with multiple ticket prices or multiple attendees per ticket
- Multiple event attendees per registration
- Event registration data pertaining to the new Events module
If your data contains any of these data types, they will need to be removed before import.
Custom Fields
If you require custom fields (i.e. any field not listed in the Standard Field section), you have two options to create such fields: 1) You may create the custom field in the CRM before you import your data via the Import Manager, or 2) You may create the custom field in the Import Manager during the import itself. For more information about custom fields visit Legacy Events Custom Fields.
Common Formatting Errors
There are many common formatting errors which occur when importing donation data. These include:
- Invalid file format: Neon CRM supports .xlsx (Excel) or .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