Column mapping
Match every CSV column to the right Nomow field before importing.
Column mapping is step 3 of the import wizard. It decides where each column in your file lands in Nomow — on the contact record, on the linked company, or in a raw overflow bucket for custom data.
CSV column
Maps to Nomow field
How the mapping screen works
The left column lists every header from your file along with a few sample values. The right column is a dropdown for each row where you select the target field. Nomow auto-suggests a mapping based on header names — review the suggestions before proceeding, as column names that are close but not exact may be mismatched.
Standard target fields
| Target field | Where it lands | Notes |
|---|---|---|
email | Contact | Required. Used as the deduplication key |
first_name | Contact | |
last_name | Contact | |
full_name | Contact | Split into first / last if no separate columns |
title | Contact | Job title |
phone | Contact | Include country code for best formatting |
linkedin_url | Contact | |
company | Company | Name; used to find or create the company record |
industry | Company | Stored on the linked company |
employees | Company | Stored on the linked company |
country | Company | Stored on the linked company |
city | Company | Stored on the linked company |
technologies | Company | Comma-separated tech stack tags |
Custom fields with raw.<key>
Any column that does not fit a standard field can be stored in the contact's raw data bucket. Map it to raw.<key> where <key> is any lowercase slug you choose — for example raw.lead_source or raw.account_tier. These fields appear on the contact's Data tab and can be referenced in saved views and custom rules.
Auto-slugging unrecognized columns
If Nomow cannot match a column to a standard field and you leave the auto-suggestion in place, it writes the value to raw.<slug> where <slug> is the normalized column header. For example, a header called "Lead Source" becomes raw.lead_source. This is safe — no data is lost — but review the mapping to confirm the auto-slug names make sense for your workspace.
Columns you can skip
Set a column's target to — Skip — to exclude it from the import entirely. Skipped columns are not stored anywhere.
Tips for accurate mapping
- Match email first. The dedup engine runs on email; everything else follows.
- Check company columns.
industry,employees,country, andcityland on the company, not the contact. If you have separate company-level columns and contact-level columns with the same concept, map only the company-level one. - Use
full_namewhen there is no split. Nomow splits it heuristically into first and last name. Results are good for Western names; review a few rows in the preview step. - Avoid mapping two columns to the same field. The last column wins, which can overwrite the better value. Instead, keep the better column and skip the duplicate.
Next steps
After mapping, go to step 4 (Preview) to inspect the dedup verdict per row. If verdicts look wrong, the most common cause is a misconfigured email mapping — return to this step and correct it. Full troubleshooting is in Import problems. After a successful import, check the history and revert options in Import history & revert.
Was this article helpful?