Import contacts from a file
Click Import on the Contacts list. The wizard has three steps.
1. Upload
Section titled “1. Upload”Choose a CSV with a header row (up to 25 MB, up to 5,000 rows — split a larger file). Or choose the Connections.csv from LinkedIn’s data export: the wizard recognizes it on its own and switches to LinkedIn mode, described below.
2. Map columns
Section titled “2. Map columns”Each CSV column is matched to a contact field automatically. Change any mapping or skip a column. Fields your Admin added under Entities and fields are available here too.
3. Review and commit
Section titled “3. Review and commit”A dry run reports N valid, M errors, with the reason on each bad row. Commit import takes you to a progress page (/import-jobs). Small imports finish in a moment; large ones (over 2,000 rows) run in the background and the page updates as they go. Bad rows are skipped and listed; the good rows import regardless.
Importing your LinkedIn connections
Section titled “Importing your LinkedIn connections”LinkedIn lets you download your data (Settings & Privacy → Get a copy of your data). Inside the zip is Connections.csv. Import that file and the wizard:
- Skips the mapping step — the columns are known.
- Skips and counts the connections LinkedIn withholds (people whose privacy setting hides their name and profile export as a row with only a date). They are reported, not silently dropped.
- Updates people already in the CRM instead of duplicating them, matching by LinkedIn URL and then by email. Only fields you left blank are filled in — anything you typed or corrected is kept — so re-importing a fresh export every few months is safe and expected.
- Matches each employer to a company by name, creating the company when it is new.
- Stamps Source = LinkedIn on the contacts it creates (never on ones it merely updates).
The progress page splits the result four ways: Added / Updated / Already current / Skipped.
If you edit the column mapping, the run becomes a plain CSV import (a banner says so) and existing contacts would be duplicated — leave the mapping alone for a LinkedIn file.
What imports do not do
Section titled “What imports do not do”An import stamps a contact’s temperature if the file has one, but never creates follow-up tasks — importing a year of history must not produce dozens of reminders. Set the temperature in the app when you actually want the follow-up rule to fire.