LinkedIn Sales Navigator
Salesforce Contacts6 fieldsHow to import LinkedIn Sales Navigator data into Salesforce Contacts
LinkedIn Sales Navigator lead lists are pulled into a CSV by a scraper like Evaboot. This template maps that export to Salesforce's standard contact fields: first name, last name, job title, and the work email. Email carries data on Evaboot Pro tiers and is blank on the baseline export. Names are title-cased before import. The LinkedIn profile URL is mapped to a custom Salesforce field called LinkedIn_URL__c. Salesforce Contacts associate to an Account rather than carrying a company name, so Company Name is left for you to link after import. Mutual connections and the contact's two previous roles are composed into Salesforce's Description field as a multi-line block, one labeled line per non-empty slot, so reps see the warm-intro and champion signals on the contact record. Everything else is listed in the Columns we don't use section.
Field-by-field mapping
This is the complete column mapping from LinkedIn Sales Navigator to Salesforce Contacts. The left column is the header in your CSV export. The right column is the Salesforce Contacts field it should map to.
| LinkedIn Sales Navigator column | Salesforce Contacts field | |
|---|---|---|
| Email Sales Navigator's standard export ships an Email column, populated on Evaboot Pro and higher tiers and empty on the baseline tier. When populated, the work email maps here. TransformLowercased and trimmed | ||
| First Name | First NameFirstName TransformTitle-cased and trimmed | |
| Last Name | Last Name*LastName Salesforce requires a Last Name on every Contact. This template creates Contacts; link each one to its Account by company name after import. TransformTitle-cased and trimmed | |
| Job Title | Title | |
| Profile URL | LinkedIn URLLinkedIn_URL__c Maps to a custom Salesforce field called LinkedIn_URL__c. Create that field on the Contact object in Salesforce before importing, or open the mapping in Operelio and point the column at a different field instead. | |
| Description Three slots compose into Salesforce's Description field as a labeled multi-line block. Slot 1 is Mutual Connections on its own. Slot 2 is the most recent previous role (Past Title 1, Past Company 1, Past Company Duration 1). Slot 3 is the role before that (Past Title 2, Past Company 2, Past Company Duration 2). Each slot renders as '- column: value | column: value' on its own line. Empty slots are skipped, so contacts with no past roles or no mutual connections land with whichever subset is populated. Remove the row in the column mapper if you don't want it. TransformComposed into a multi-line block |
Required by Salesforce Contacts.
Columns we don't use
Your LinkedIn Sales Navigator export includes 27 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Salesforce Contacts.
- Personal Email
This CRM has one email field, and the work Email column is mapped to it. The work email is the higher-fidelity channel for B2B outreach and the lower-risk channel under GDPR, since a personal address needs explicit consent in most EU jurisdictions.
If you need it. Map it by hand to a custom email field in the column mapper if you want the personal address kept as a fallback.
- Company Name
Salesforce Contacts associate to an Account rather than carrying a company name on the Contact itself. This template creates Contact records; the Account link is a separate step.
If you need it. After import, link each Contact to its Account in Salesforce, or run a LinkedIn Sales Navigator to Salesforce Accounts pass first and match on company name.
- Full Name
First Name and Last Name are mapped separately, so Full Name is redundant. It is the same person's name in one field instead of two.
If you need it. None needed. Salesforce shows the contact name from First Name and Last Name.
- Sales Navigator URL
Salesforce Contacts have no native field for the Sales Navigator lead URL. The Profile URL is mapped to the custom LinkedIn_URL__c field instead, since that is the canonical public profile.
If you need it. Add a second custom Contact URL field if you want the sales.linkedin.com URL kept as well.
- Location, Country
This template's Salesforce Contacts schema has Mailing City, State, and Country, but the standard Sales Navigator export has no person-level city or state column to fill them, and Location is a free-text string. The Country column has no clean Mailing partner without the rest of the address.
If you need it. If you only need the country, map Country to Mailing Country by hand in the column mapper.
- Company Industry, Company Size, Company Headcount, Company URL, Company Website, Company Founded, Company Description, Company Specialties
These are company-level data points. Salesforce Contacts have no native fields for them, they belong on the Salesforce Account record.
If you need it. Run a separate LinkedIn Sales Navigator to Salesforce Accounts pass to land these on the Account record.
- Company Location, Company Country, Company City
These describe where the company is, not where the contact is. They belong on the Salesforce Account record.
If you need it. Land the company location on the Salesforce Account record in a separate pass if you need it.
- Years in Role, Years in Company
Salesforce Contacts have no native fields for role or company tenure. The data is a useful 'just changed jobs' filter, Salesforce just has no standard place for it.
If you need it. Map them by hand to custom number Contact fields if you want to filter on tenure in Salesforce.
- Description, Education Top
Salesforce Contacts have no native field for a LinkedIn About summary or a top education entry. The data is real, Salesforce just has no standard place for it.
If you need it. Map them by hand to custom Contact fields if you want them in Salesforce.
- Skills, Languages
Salesforce Contacts have no native multi-select field for skills or languages. Both columns are comma-separated lists of several values.
If you need it. Map them by hand to custom multi-select picklist Contact fields if you want them in Salesforce.
- Connection Degree, Shared Connections
Salesforce Contacts have no native fields for the connection-degree integer or the shared-connections count. Mutual Connections (the named-list column) is composed into the Description field; these two are the numeric signals beside it.
If you need it. Map them by hand to custom Contact fields if you run warm-intro plays from connection data.
- List Name, Scraped At
Salesforce Contacts have no native field for the Sales Navigator list a row came from or the date it was scraped.
If you need it. Map them by hand to custom Contact fields if you want to record which Sales Navigator search a contact came from.
Formatting and cleanup
LinkedIn Sales Navigator exports rarely match the format Salesforce Contacts expects. Fix these before you import.
- 1.Maps the work Email column to the Contact's Email field when the export includes it
- 2.Title-cases name fields
- 3.Maps Profile URL to the custom Salesforce field LinkedIn_URL__c
- 4.Composes Mutual Connections and the two previous-role slots into the Description field as a labeled multi-line block, skipping empty slots
- 5.Trims whitespace and removes blank rows
Or skip the manual work
Operelio runs this cleanup and mapping for you. Upload your LinkedIn Sales Navigator export and download a clean, import-ready file for Salesforce Contacts.
LinkedIn Sales Navigator to Salesforce Contacts FAQ
How do I get a CSV out of LinkedIn Sales Navigator?
Sales Navigator no longer has a built-in CSV export for lead lists. Most teams use a scraping tool such as Evaboot, Wiza, or PhantomBuster, which reads your Sales Navigator lead list and gives you a CSV. This template is built for the standard Evaboot column set. Upload that file to Operelio to map it to Salesforce contact fields.
Should I use the Leads template or the Contacts template?
Use the LinkedIn Sales Navigator to Salesforce Leads template for cold prospecting lists you want to work before they convert. Use this Contacts template when you want the people to land directly as Contacts, for example because they already belong to Accounts you track. Salesforce Leads and Contacts are different objects with different fields, so the two templates map the export differently.
Why isn't Company Name mapped?
Salesforce Contacts associate to an Account rather than storing a company name on the Contact record itself. This template creates Contacts; linking each one to its Account is a separate step. You can link them in Salesforce after import, or run a LinkedIn Sales Navigator to Salesforce Accounts pass first and match on company name.
Why does this template map so few columns?
The standard Sales Navigator export has no phone, department, or person-level address column, and Salesforce Contacts associate company data to the Account rather than the Contact. That leaves first name, last name, job title, Profile URL, and the tier-gated Email column as the core Contact fields this export can fill directly. Everything else is listed in the Columns we don't use section with a workaround for each.
Does this template map email?
Yes. Sales Navigator's standard export ships an Email column that is populated on enrichment tiers (Evaboot Pro and up) and empty on the baseline tier. The template maps that work Email column to the Contact's Email field, so a Pro-tier export lands email and a baseline export leaves it blank. The separate Personal Email column is left unmapped, since the Contact has one email slot and the work email is the higher-fidelity B2B channel. The export has no phone column, so phone is not mapped.
Does this template handle the LinkedIn URL?
Yes. The Profile URL column is mapped to a custom Salesforce field called LinkedIn_URL__c. Create that field on the Contact object in Salesforce before importing, or open the mapping in Operelio and point the column at a different field instead. The separate Sales Navigator URL column is not mapped.
Will this create duplicate contacts?
Salesforce checks for duplicates based on your org's matching rules. Review your duplicate settings in Salesforce Setup before importing, especially if you already have contacts from the same Sales Navigator searches.
