Why did some rows of my CSV import fail?
Updated October 19, 2026
A row fails when Breakcold can't write it safely. The other rows still import, unless you chose Stop the import. Open the import and filter the Run import table on failed rows: the Message column says what went wrong.
Common reasons
- A value doesn't fit its field: a date, number, email or option that can't be read. The message names the field and the value.
- A required value is missing: the message ends with "Required value is missing".
- The owner isn't found: an Owner column must hold the exact email address or the exact name of a workspace member. "Workspace member not found" means no member matches; "Workspace member name is ambiguous" means two members share that name, so use their email.
- The row matches different records: its email, phone or social profile values belong to two different records. See Does an import update records that already exist?
- A read-only field is mapped: fields Breakcold fills itself, like Last interaction, can't be imported.
Fix values before the import
The Review values step lists every value that doesn't fit its field, with the number of rows that have it.
- Type a Replacement value, or turn on Skip this value to leave that field empty on those rows. Then click Save and revalidate.
- For a date column, pick ISO date, European date or American date. For a number column, pick Dot decimal or Comma decimal.
- Create missing select options (on by default) adds new options to select fields instead of reporting them as errors.
- Continue with errors moves on: the rows with those values fail during the import.
Limits
- CSV files only. Save an Excel or Numbers file as CSV first.
- Up to 50,000 data rows per file. Split bigger files.
- The first row must hold the column names.
- One row can be at most 512 KB.
Good to know
- Imports cost no tokens. Automatic enrichment can still run on the records an import creates and spend tokens. To avoid it, turn it off for that object in Settings → Enrichment before you import.
- To retry, fix the file and import it again: rows that already went in are matched and updated, not duplicated, when a unique field is mapped.
Related
Still stuck?