How to migrate data from EventsAir to InEvent
Updated 17 hours ago
by
Chioma Okenwa
This guide will help you export your data from EventsAir and import it into InEvent. By following the steps below, you can ensure a smooth migration of attendees, activities, and speakers.
Exporting data from EventsAir
- Log in to your EventsAir account.
- Navigate to Data Management or Reports.
- Select the event and the dataset you want to export (e.g. Attendees, Sessions, Speakers).
- Export the file in CSV or Excel format.
- Make sure the export includes all necessary fields such as first name, last name, email, company, job title, etc.
- For sessions, include session title, date/time, and speaker assignments.
- Save the exported files on your computer.
Setting up your event on InEvent
Before importing your data into InEvent, you need to first set up your event on InEvent's platform.
To help you set up the event let's take a look at this step-by-step. In this article you will learn how to:
- Create an event and add information on the Details page
- Add Sponsors, Speakers, and Content
- Create activities and choose the settings for the Virtual Lobby
- Learn more about Customization, Communication, and Registration
- Add Attendees, Invitees, and Leads
- Learn about the Interactions with attendees and finally Dry run
Importing data to InEvent
After setting up your event, you can start importing data from EventsAir into InEvent. To make this easier, InEvent provides a demo Excel file. Log into your InEvent platform and navigate to the page where you want to import data. Click the Edit button at the top right corner, and the Import button will appear at the top left. Click Import to download the demo file, then transfer and consolidate your exported data from EventsAir into this spreadsheet.
What data can be imported?
Below are some of the data that can be imported EventsAir into InEvent's platform:
Field Mapping Overview
This table shows how information from EventsAir maps to InEvent, grouped by feature type. Each feature (e.g., Attendees, Activities, Tickets, Sponsors) have its own separate spreadsheet or report. Notes explain what each field means for you and highlight any special considerations when importing data.
Attendees
EventsAir Field | InEvent Field | Notes (what this means for you) |
First Name | First Name | Goes directly into InEvent’s First Name field. Make sure names are entered consistently to avoid duplicates. |
Last Name | Last Name | Goes directly into InEvent’s Last Name field. Ensure correct spelling to maintain accurate attendee lists. |
Email Address | Primary unique identifier. Must be valid and unique to avoid import errors. | |
Username | Username | Used for attendee login and as an identifier. Can match email or be customized. Must be unique. |
Company | Company | Optional. Helps with networking/reporting. Can be left blank. |
Job Title | Role | Same information, but InEvent calls it Role instead of “Job Title.” Useful for attendee segmentation or internal reporting. |
Registration Type | Tag | EventsAir may use VIP, Regular, etc. Create corresponding tags on InEvent's platform. |
Activities / Sessions
EventsAir Field | InEvent Field | Notes |
Session Name | Activity Name | Map each session to an activity to track attendance correctly. |
Session Date/Time | Activity Date/Time | Import with correct time zone settings. |
Speaker Name | Speaker Full Name | Goes under People > Speakers. Use full names to associate with sessions. |
Tickets
EventsAir Field | InEvent Field | Notes |
Ticket Type | Ticket Name | Map only if tickets exist. Ensure the type exists in InEvent. |
Ticket Price | Ticket Price | Map this field only for paid tickets. Ensure the currency format matches InEvent’s format to maintain accuracy and avoid import issues. |
Sponsors / Exhibitors
EventsAir Field | InEvent Field | Notes |
Sponsor Name | Sponsor | Map if using sponsors in your event. Maintains visibility and branding. |
Exhibitor Name | Exhibitor | Map if using exhibitors in your event. Useful for booth assignments and lead tracking. |
Notes & best practices
- Data cleaning: Remove duplicates and correct missing data before import.
- Custom fields: Create corresponding custom fields in InEvent to capture any extra data from EventsAir.
- Separate imports: Each feature such as Attendees, Activities, Speakers, etc should be imported separately in their dedicated menus.
