Column mapping during import
How to map the columns of your file to Nexcal fields during CSV import and which rules apply.
Last reviewed: 2026-07-22
Column mapping during import
During the CSV import, column mapping connects the columns of your file to the fields in Nexcal. Only through this mapping does Nexcal know which column contains the phone number, the name or other details.
How the mapping works
After you upload the file, Nexcal shows the columns it recognized from your header row. For each column you select the matching Nexcal field. Nexcal often suggests a mapping based on the column names, which you review and adjust if needed.
Important rules
- Required fields must be mapped to a column, especially the phone number.
- Each column is mapped to at most one field.
- Columns you do not need can be excluded from the import.
- A clear header row in the source file makes mapping much easier.
Hinweis: Check the mapping in the preview before you confirm the import. An incorrect mapping causes data to end up in the wrong field.
When the mapping does not fit
If a mapping is wrong, correct it before confirming. If you only notice the error after the import, correct the source file or the mapping and import again. For guidance on common problems, see fixing CSV import errors.
Common questions
Why does Nexcal already suggest a mapping?
Nexcal evaluates the column names from your header row and suggests matching fields based on them. Clear, unambiguous column names improve the quality of these suggestions.
Can I map one column to several fields?
No. Each column is mapped to at most one field. If you need a piece of information in two fields, create two separate columns in the source file.
What happens to unmapped columns?
Unmapped columns are not imported. This lets you keep additional information in the file without importing it.