Fixing CSV import errors
The most common CSV import errors and how to correct the source file and import again.
Last reviewed: 2026-07-22
Fixing CSV import errors
Not every import succeeds on the first try. The cause usually lies in the source file and can be fixed quickly. This article describes the most common errors and how to resolve them.
Common causes
- Wrong encoding: special characters are displayed incorrectly. Save the file in UTF-8.
- Missing or unclear header row: without clear column names, mapping is difficult. Add a clear header row.
- Empty required fields: rows without required details are flagged. Fill in the missing fields.
- Invalid phone numbers: numbers without a country code or with disallowed characters are rejected. See formatting phone numbers correctly.
- Duplicate records: detected duplicates are reported or rejected. See detecting duplicate contacts.
How to proceed
- Read the import summary and note the causes it lists.
- Open the source file and correct the affected rows.
- Check the encoding, header row and column mapping.
- Import the corrected file again.
Hinweis: Correct errors in the source file and import again, instead of adding individual records one by one afterwards. This keeps your data consistent.
If the import still fails
If the import remains unsuccessful even though the file appears correct, the article CSV import fails can help. It contains further steps and guidance on when to contact support.
Common questions
Can I re-import only the faulty rows?
Correct the affected rows in the source file and import the cleaned file again. This is more reliable than adding individual records manually afterwards.
Why are special characters displayed incorrectly?
This usually indicates a different encoding. Save the file in UTF-8 so that special characters are imported correctly.
When should I contact support?
If the import remains unsuccessful even though the file appears correct, follow the steps in CSV import fails and reach out to support if needed.