The Import feature is available only for events with Preview Features enabled. If you wish to enable this feature, please chat with the ClearEvent support team and request access.

Trial events cannot import registrants. If you are trialing, you will see a message that importing is not allowed.

You must have at least one registration form created. If your event has no forms, importing is blocked.

Column names are not case-sensitive. A name in square brackets, such as [ShirtSize], also works, so you can re-import a registrant export without renaming its columns.

Custom field columns are optional. Include only the fields you want to import.

A required field must have a value in every row, but only when its column is in your file.

A blank cell imports no answer for that field.

Columns that don’t match a field on the form are ignored. After the import, ClearEvent lists the ignored columns so you can catch typos.

File attachment fields cannot be imported. Their columns are ignored and listed after the import.

If a field’s Short Field Name (Id) is the same as a profile column (for example, Notes), that column imports into the profile field, not the custom field.

If two fields on the form have the same Short Field Name (Id), the file is rejected. Give each field a unique name, then import again.

Options that are hidden on the form cannot be imported.

If a required dropdown or multiple choice field has a visible option with a blank value, a blank cell selects that option.

Use the same date format throughout a column. A date like 03/04/2026 is read month first, unless a date in the same column has a day above 12 (such as 25/04/2026). Read Formatting Dates In Your Import Data to learn more.

Fields whose Field Visibility hides them from registrants can still be imported, which is useful for organizer-only data. They are never required.

Fields shown only between certain dates can be imported at any time.

A field shown only when another field has a certain value (Display when) can have a value only in rows where the other field’s answer would show it. It is required only in those rows.

A field limited by Fee Group Filters to a fee group other than the import’s selected fee cannot have a value.

Use MobilePhone for Mobile Phone and OtherPhone for the primary business or home phone number.

A phone number value is saved only when that field is enabled (visible) on the selected registration form. If the field is not enabled, the phone number value in the CSV import file is ignored and the row can still import.

Making a phone field required on the form does not require it in the CSV. Blank phone cells are allowed.

Phone numbers are stored as text (up to 30 characters). Import does not validate phone format.

Address columns (Address1, Address2, City, StateProv, ZipPostal, Country) are saved on import even if Address is not enabled on the form.

Making Address required on the form does not require address columns in the CSV. Blank address cells are allowed.

Leave Country blank if you are not importing a country.

If Country is filled, it must be a 3-letter ISO country code from the same list used by the Country dropdown on registration forms (for example, USA, CAN, GBR, AUS).

Do not use 2-letter codes (such as US or CA) or country names (such as Canada). Codes are not case-sensitive.

An invalid country code rejects that row with an error asking you to use a 3-letter code from the allowed list.

ClearEvent checks each row’s required profile fields and custom field values first. A row with any problem is not imported.

ClearEvent looks up each registrant by Email.

If the email already belongs to an existing ClearEvent account:

If the email does not match an existing account, a new ClearEvent account is created and linked to the new registration.

If you enabled confirmation emails:

Maximum import errors: Registrant import stops after 50 rows with errors in the CSV import file. The result tells you which row it stopped at; rows after it were not processed. Duplicate registration detections count as row errors.

Form capacity reached: Import is blocked if the form registration limit would be exceeded. The error explains how many registrants you tried to add and how many spots remain. The registrant import will stop at the form capacity if it is reached. If you increase the form capacity and import registrants again, you should remove previously imported registrants from the import file to avoid duplicate registration import errors.

Invalid or missing required fields: Rows missing Email, First Name, or Last Name, rows with an invalid country code, and rows with an invalid custom field value are reported with their row number so you can fix the CSV and re-upload.

Previously imported rows: When you re-upload, ClearEvent skips records that match the same Email, First Name, Last Name, form, and fee (if used). An error is logged.

File attachment fields

Updating the answers of registrants who are already registered

Payment details and online payments

Booth fees

Products associated with an imported registration

Discounts associated with an offline fee

Availability periods associated with a registration form

Custom form field defaults (a field without a column, or with a blank cell, gets no answer)

Consent First: Only import registrant data for individuals who have explicitly consented to receive communications about your event (for example, they registered offline or provided permission).

Payment Details: Never upload any document containing payment details (credit card numbers, bank account details, etc.).

Do Not Buy Lists: Never import purchased, rented, or third-party email lists. These are considered spam sources and are strictly prohibited.

Transparency: Make sure registrants understand their information will be used for event-related communications when you collect it.

Preference Respect: Respect opt-outs and unsubscribe requests. If a registrant no longer wishes to receive communication, you must not re-import them or attempt to bypass their request.

Direct Sign-Up Recommended: Whenever possible, allow registrants to sign up directly through the Event Portal registration forms. This supports compliance, creates a clearer audit trail of consent, and reduces risk to you and ClearEvent.