Skip to content

Handle Import Errors

Overview

When importing people into a group, Eventene checks each row in your file before adding or updating records. If a row cannot be processed, you will see an error or warning that tells you what to fix.

This article covers the most common issues and how to resolve them, so your import goes through cleanly the second time.

How to Use It

Review errors before confirming

After uploading a file, you will see a preview of the data and any issues that were detected. Review this preview carefully:

  • Confirm column mapping is correct
  • Check that required fields are populated
  • Look for warnings about duplicates or unmatched values

If you confirm the import while errors remain, those rows may be skipped. Fixing issues in the source file before confirming is usually faster than cleaning up afterward.

Common issue: missing required fields

If a row is missing a required field (such as Email), it will not import.

To fix:

  • Open the source file
  • Add the missing values
  • Re-upload

If a participant genuinely has no email, decide whether to use a placeholder, leave them out of the import, or add them manually after the bulk import.

Common issue: column not mapped

If a column in your file does not match an existing field, it will not import.

To fix:

  • Map the column to the correct field during the mapping step, or
  • Create a new custom field that matches the column (Use Custom Fields), then re-upload

Creating fields before importing is the cleanest path. See Import People into a Group.

Common issue: duplicate records

If a row matches an existing person (typically by Email or by EVENTENE_ID), the import will update that record rather than create a new one.

What this looks like:

  • The preview shows the row as an update, not a new add
  • After import, the existing person reflects the new data

If you want to add a separate record instead of updating, change the Email or identifier so it does not match any existing person.

Common issue: invalid field values

If a value does not fit its field type, it will be flagged. Examples:

  • Text in a Number field
  • An invalid date format
  • Free text in a Dropdown field that does not match an existing option

To fix:

  • Correct the value in the source file, or
  • Adjust the field type if your data does not fit it

Common issue: bad email format

Email addresses with typos or missing @ will be flagged.

To fix:

  • Clean up the email column in the source file
  • Re-upload

Catching email errors before sending invitations avoids wasted sends and bounces.

Test with a small sample first

For large imports, test with a few rows before running the full file:

  1. Copy 5–10 representative rows into a test file
  2. Import them into your group
  3. Confirm the result is what you expect
  4. Run the full import

This catches mapping or formatting issues before they affect hundreds of records.

Tips & Best Practices

  • Create custom fields before importing so columns map cleanly
  • Keep column names consistent across recurring imports — it speeds up the mapping step
  • Export your group as a backup before running a large import (Export & Backup Group)
  • Use EVENTENE_ID to update existing records precisely when syncing from another system
  • If the same error appears on many rows, fix it in the source file rather than row by row