Skip to main content
Registration: Export

Learn how to export registration data from ClearEvent.

Updated over 8 months ago

Once registrations have been received for your event, you may wish to export this list of registrants. Registration details can be exported to a .CSV (Comma Separated Values) format and can be opened in any capable editor (e.g. Microsoft Excel, or Google Sheets)

How to Export Registration Data

To export registrant data from ClearEvent:

  1. Go to the Event Manager App > Registration section > Registrants tab.

  2. Click the Export button in the toolbar.

  3. From the Export registrations popup window, choose one of the following options:

    1. Choose "All Registrant Types (single file)" to export all registrant types at once as one file. Please click here to learn more details on how the data is combined into one file, or

    2. Choose "All Registrant Types (multiple files - .zip)" to export all registrant types at once as individual files, or

    3. Choose a specific registrant type to export to a single file.

  4. Choose if you would like to also include test registration data in the export. Test registrations requiring online payment that were processed while your Payment Gateway was in Test Mode.

  5. Click OK.

  6. Your web browser will prompt you to save the downloaded file that contains your exported data. 

That's it! Once you save the file, you'll be able to open it with Excel.

Column Naming Conventions:

The export file will include two types of columns:

  • Built-In Columns

  • Custom Columns

Built-In Columns

These columns are fixed and the column names are fixed.

Custom Columns

These columns are dynamic and vary based on the configuration of your registration form. If you have added custom fields, products, fees, or availability periods, additional custom columns will be included in the exported data. These custom column names will be wrapped with square brackets (e.g. "[WaiverAgreed]" to differentiate these columns from the built-in columns and prevent column naming collisions.

Did this answer your question?