CSV import fails
Common causes when a CSV import fails, from the header line and character encoding to invalid phone numbers, and how to correct the file.
Last reviewed: 2026-07-22
CSV import fails
When a CSV import does not work as expected, the cause is usually the file itself: its format, character encoding, header line or individual records. This article helps you recognize and fix the most common causes.
Check before importing
- Use a CSV file with a clear header line.
- Use a common character encoding so that special characters appear correctly.
- Make sure phone numbers include a country code.
- Fill in all required fields.
A complete preparation is described in preparing a CSV file.
Common causes
- Wrong header line: Columns cannot be mapped if the header line is missing or unclear.
- Character encoding: Incorrectly displayed characters point to an unsuitable encoding.
- Invalid phone numbers: Numbers without a country code or with invalid characters are rejected. See invalid phone number.
- Empty required fields: Records without the required details cannot be imported.
Reading the import summary
After an import, Nexcal usually shows a summary of imported and rejected records. Use this information to correct the affected rows specifically, rather than rebuilding the entire file.
Hinweis: First fix the errors named in the summary in the source file, then import the corrected records again.
Detailed troubleshooting is available in fixing CSV import errors.
If the import still fails
If the import remains unsuccessful even with a correct file, contact support. A small, anonymized excerpt of the file with the header line helps with the analysis. You can find guidance in sending attachments securely.