CRM
Importing contacts from CSV
Column mapping, the email uniqueness rule, and what happens to duplicates.
Updated
Contacts → Import. The delimiter (comma, or the Hungarian Excel semicolon) and the headers are detected, and common column names — Hungarian and English — map themselves; you fix only the odd one out.
The target fields
A column maps onto one of: first_name, last_name, email, phone, mobile, position, company_name, status, source, birthday, city, postal_code, address, country, notes, subscribed, owner, tags. Every custom field on contacts is offered as well.
The status column accepts one of: lead, prospect, customer, inactive. The subscribed column takes yes/no, 1/0, true/false.
Email is unique
Within one company an email address belongs to at most one live contact. If an imported row's address already exists, the existing record is updated with the file's filled-in fields — no twin is created. That is why duplicate detection does not use email: it matches on phone number and on name + company.
Subscription and the suppression list
An address that unsubscribed, bounced or complained earlier is on the suppression list, and a subscribed=yes in the file cannot subscribe it again. Only the person's own click (double opt-in) outranks their earlier refusal.
The import is recorded in the audit log with its row count. If something went wrong, Contacts → Duplicates offers phone or name + company matches for merging.