How to import contacts from a CSV
A CSV import is the most common way data enters a CRM, and the most common way duplicates and mismapped fields get created.
The fix is preparation: a clean file and a checked mapping mean the import lands right the first time.
Short answer
Import contacts from a CSV by cleaning the file (consistent columns, standardized values, no junk rows), mapping each column to a CRM field, de-duping against existing contacts on email, testing a small batch, then loading the rest. A well-formatted CSV and a mapping check up front prevent the duplicates and mismapped fields that plague careless imports.
Step by step
Format the CSV cleanly
One header row, consistent columns, standardized values, and no merged cells or junk rows. A messy file imports as messy data.
Map columns to fields
Match each column to the correct CRM field and translate picklist values to the CRM's accepted options.
De-dupe on email
Match rows against existing contacts by email so returning people update their record instead of creating a duplicate.
Test then load
Import a few rows first, confirm they landed correctly, then run the full file.
A clean file is half the battle
Most import problems trace back to the file: inconsistent columns, values that do not match the CRM's picklists, and stray junk rows. Ten minutes formatting the CSV cleanly prevents hours untangling a bad import. Prepare the file, then the mapping is easy.
How Ardovo helps
Ardovo auto-maps CSV columns to fields, de-dupes rows against existing contacts, and previews the import before committing. Rook flags format and mapping issues on a test batch, so a CSV import updates the right records and never quietly floods the database with duplicates.
Frequently asked questions
How do you avoid duplicates when importing a CSV?
De-dupe the import against existing contacts on a strong key like email before loading, so returning people update their existing record instead of creating a duplicate. Also de-dupe within the file itself, since CSVs often contain their own repeats.
How should a CSV be formatted for import?
One header row, consistent columns, standardized values that match the CRM's picklists, and no merged cells, blank rows, or junk. A cleanly formatted file is the single biggest factor in whether an import lands correctly or creates a mess.
Why test a CSV import before loading everything?
Because mapping errors and format mismatches that would corrupt every row show up on a small test batch, where they are trivial to fix. Testing a few rows first turns a potential large-scale mess into a quick correction before the full load.