LinkedIn Sales Navigator
Pipedrive Contacts5 fieldsHow to import LinkedIn Sales Navigator data into Pipedrive
LinkedIn Sales Navigator lead lists are pulled into a CSV by a scraper like Evaboot. This template maps that export to Pipedrive's contact fields: it combines First Name and Last Name into Pipedrive's single Name field, matches the company to an organization, and maps job title and the work email. Email carries data on Evaboot Pro tiers and is blank on the baseline export. Pipedrive's contact model is leaner, so most other columns belong on the organization. Mutual connections and the contact's two previous roles are composed into Pipedrive's Notes 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. The Columns we don't use section covers each one.
Field-by-field mapping
This is the complete column mapping from LinkedIn Sales Navigator to Pipedrive. The left column is the header in your CSV export. The right column is the Pipedrive field it should map to.
| LinkedIn Sales Navigator column | Pipedrive field | |
|---|---|---|
| Emailemail 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 + Last Name | Name*name Pipedrive uses a single Name field, so First Name and Last Name are combined into one with a space between them. TransformFirst Name and Last Name combined with a space | |
| Job Title | Job Titlejob_title | |
| Company Name | Organizationorg_name Matched to an existing Pipedrive organization, or a new one is created. | |
| Notesnotes Three slots compose into Pipedrive's Notes 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 Pipedrive.
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 Pipedrive.
- 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.
- Full Name
First Name and Last Name are combined into Pipedrive's Name field, so Full Name is redundant. It is the same person's name the template already builds.
If you need it. None needed. The template builds the Name field from First Name and Last Name.
- Profile URL, Sales Navigator URL
Pipedrive contacts have no native LinkedIn field.
If you need it. Add a custom Link field on the Pipedrive contact called LinkedIn, then map Profile URL to it by hand.
- Location, Country
Pipedrive contacts have no native address fields. Addresses live on the Pipedrive organization in Pipedrive's data model.
If you need it. Add custom contact fields if you need the location on the contact, or move it to the matched organization's address after import.
- Company Industry, Company Size, Company Headcount, Company URL, Company Website, Company Founded, Company Description, Company Specialties
These are company-level data points. Pipedrive contacts have no native fields for them, they belong on the Pipedrive organization.
If you need it. Enrich the matched Pipedrive organization after import using Sales Navigator's company data, or add custom organization fields and update by organization name.
- Company Location, Company Country, Company City
The company location belongs on the Pipedrive organization, not the contact. Pipedrive contacts have no address fields.
If you need it. Land the company location on the matched Pipedrive organization's Address field after import.
- Years in Role, Years in Company
Pipedrive contacts have no native fields for role or company tenure. The data is a useful 'just changed jobs' filter, Pipedrive just has no standard place for it.
If you need it. Add custom contact fields in Pipedrive for tenure, then map them by hand in the column mapper.
- Description, Education Top
Pipedrive contacts have no native field for a LinkedIn About summary or a top education entry. The data is real, Pipedrive just has no standard place for it.
If you need it. Add custom contact fields in Pipedrive, then map them by hand.
- Skills, Languages
Pipedrive contacts have no native multi-select field for skills or languages. Both columns are comma-separated lists of several values.
If you need it. Add custom contact fields in Pipedrive if you want them, then map them by hand.
- Connection Degree, Shared Connections
Pipedrive 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 Notes field; these two are the numeric signals beside it.
If you need it. Add custom contact fields in Pipedrive if you run warm-intro plays from connection data.
- List Name, Scraped At
Pipedrive contacts have no native field for the Sales Navigator list a row came from or the date it was scraped.
If you need it. Add custom contact fields in Pipedrive if you want any of these kept, or use Pipedrive's labels for list segmentation.
Formatting and cleanup
LinkedIn Sales Navigator exports rarely match the format Pipedrive expects. Fix these before you import.
- 1.Maps the work Email column to Pipedrive's email field when the export includes it
- 2.Combines First Name and Last Name into Pipedrive's single Name field
- 3.Title-cases name fields
- 4.Matches Company Name to an existing Pipedrive organization, or creates a new one
- 5.Composes Mutual Connections and the two previous-role slots into the Notes field as a labeled multi-line block, skipping empty slots
- 6.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 Pipedrive.
LinkedIn Sales Navigator to Pipedrive 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.
Why does this template combine First Name and Last Name?
Pipedrive contacts use a single Name field, not separate first and last name fields. The template combines the two columns with a space so the contact records look right in Pipedrive.
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 Pipedrive'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 Pipedrive 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.
What if the contact's company doesn't exist in Pipedrive?
The template creates a new organization in Pipedrive and links the contact to it. If the company already exists, the contact links to the existing organization.
Why are most columns not mapped?
Pipedrive contacts use a leaner field set than HubSpot or Salesforce. LinkedIn URL, the location, industry, and the company firmographics have no native Pipedrive contact field, and most of that data belongs on the Pipedrive organization rather than the contact. The Columns we don't use section above explains the workaround for each one.
Will this create duplicate contacts?
Pipedrive's import dedupes on Name plus one of email, phone, or organization, so a row matches an existing contact only when all three of those bits align. Sales Navigator's baseline-tier exports ship a blank Email column, so dedup falls back to Name plus phone or organization. Review your Pipedrive import settings to control how those rows match existing contacts.
