Your import has errors or skipped rows
This page helps you understand the import error report and fix common causes of row failures.
How to fix it
Section titled “How to fix it”Get the error report
Section titled “Get the error report”After an import completes with failures, select Download error report on the import summary page. The error report is a CSV file with one row per failure. Each row includes:
- The original row number from your source file
- The original row data
- A plain-English error description
If the error report is very large (over 1,000 errors), it’s sent to your email rather than downloaded immediately.
Common errors and how to fix them
Section titled “Common errors and how to fix them”“Email format invalid” — The email address in that row is malformed (for example, missing the @ symbol, or ending in . instead of a domain). Fix the email address in your source file.
“Email already exists — duplicate in this file” — Two or more rows in your file have the same email address. If they’re the same person, delete the duplicate row. If they’re different people sharing an email, one will need a different address before it can be imported.
“Email already exists — member in this org” — An existing member in your organization already has this email. The import treated this as an update (not a create), which is normally correct. If you’re seeing this in the error report, it means an update constraint failed — check the other error details in the same row.
“Required field missing: [field name]” — A column that is required for the selected import type had no value in this row. Check your source file for blank required cells, or ask your previous system to re-export with the missing data included.
“Member not found” — For historical payment or event imports, this means no member account exists for the email address in that row. Import your members first, then re-import the historical rows.
“Membership level not found: [level name]” — The level name in this row doesn’t match any level in your organization. Either create the level (go to Membership > Levels) or correct the name in your source file to match an existing level exactly, including capitalization.
“Value out of range” — A numeric field (for example, a payment amount) has a value outside the allowed range. Check the row’s original data and correct the value.
“Formula cell — not imported” — This cell contained a spreadsheet formula rather than a plain value. Open your file, select the cells, and paste as values only (in Excel: Paste Special > Values) to remove the formulas, then re-upload.
What to do after fixing errors
Section titled “What to do after fixing errors”- Fix the rows in your source file based on the error report.
- Save a new file with only the fixed rows (don’t include rows that already succeeded).
- Go to the import summary page for the original import.
- Select Retry failed rows only — this runs a new import using your saved column mapping, so you don’t have to re-map everything.
If that didn’t work
Section titled “If that didn’t work”If rows continue to fail after several retry attempts and the error descriptions don’t point to a clear fix, contact support. Include your import ID (visible in the import history list) and attach the error report CSV. Support can inspect the row-level error log and escalate to the data team if there’s a systematic issue.