LinkedIn Sales Navigator
HubSpot Contacts11 fieldsHow to import LinkedIn Sales Navigator data into HubSpot
LinkedIn Sales Navigator lead lists are pulled into a CSV by a scraper like Evaboot. This template maps that export to HubSpot's contact fields: names, job title, LinkedIn profile, country, company, and industry. The work Email column is mapped too; it carries data on Evaboot Pro tiers and is blank on the baseline export. Lifecycle Stage and Lead Status, which the export doesn't carry, are set to Lead and New on every row. Mutual connections and the contact's two previous roles are composed into HubSpot's Notes property 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. Data HubSpot has no standard field for 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 HubSpot. The left column is the header in your CSV export. The right column is the HubSpot field it should map to.
| LinkedIn Sales Navigator column | HubSpot 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 | First Namefirstname TransformTitle-cased and trimmed | |
| Last Name | Last Namelastname TransformTitle-cased and trimmed | |
| Job Title | Job Titlejobtitle | |
| Profile URL | LinkedIn Biohs_linkedinbio Maps to HubSpot's LinkedIn Bio property, the home for a contact's LinkedIn profile. Company URL is the LinkedIn company page and is not mapped here. | |
| Country | Country/Regioncountry Sales Navigator ships a person Country column parsed from the contact's Location. It maps to HubSpot's Country/Region field. The free-text Location string is not mapped. | |
| Company Name | Company Namecompany | |
| Company Industry | Industryindustry A Sales Navigator export ships one industry value per row, so it maps straight to HubSpot's Industry field. | |
| "Lead" | Lifecycle Stagelifecyclestage Set on every row. A Sales Navigator export doesn't ship a lifecycle stage, and a freshly scraped list is a Lead. Change the value, or remove it, in the column mapper if your process is different. | |
| "New" | Lead Statushs_lead_status Set on every row. A Sales Navigator export doesn't ship a lead status, and a newly imported prospect starts as New. Change the value, or remove it, in the column mapper if your process is different. | |
| Notesnotes Three slots compose into HubSpot's Notes property 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 |
Columns we don't use
Your LinkedIn Sales Navigator export includes 24 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in HubSpot.
- 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 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. HubSpot builds the display name from First Name and Last Name.
- Sales Navigator URL
HubSpot Contacts has no native field for the Sales Navigator lead URL. The Profile URL is mapped to LinkedIn Bio instead, since that is the canonical public profile.
If you need it. Map it by hand to a custom contact property if you want the sales.linkedin.com URL kept.
- Location
Sales Navigator's Location is a free-text string like 'London, England, United Kingdom'. HubSpot Contacts has no native field for an unstructured location. The parsed Country column is mapped instead.
If you need it. Map it by hand to a custom contact property if you want the verbatim location string kept.
- Company URL, Company Website, Company Size, Company Founded, Company Description, Company Specialties
These are company-level data points. HubSpot Contacts has no native fields for them, they belong on the HubSpot Company record.
If you need it. Run a separate LinkedIn Sales Navigator to HubSpot Companies pass to land these on the Company record.
- Company Location, Company Country, Company City
These describe where the company is, not where the contact is. HubSpot Contacts has one address block and it belongs to the person, not their employer.
If you need it. Land the company location on the HubSpot Company record in a separate pass if you need it.
- Years in Role, Years in Company
HubSpot Contacts has no native fields for role or company tenure. The data is a useful 'just changed jobs' filter, HubSpot just has no standard place for it.
If you need it. Map them by hand to custom number properties if you want to filter on tenure in HubSpot.
- Description, Education Top
HubSpot Contacts has no native field for a LinkedIn About summary or a top education entry. The data is real, HubSpot just has no standard place for it.
If you need it. Map them by hand to custom contact properties if you want them in HubSpot.
- Skills, Languages
HubSpot Contacts has 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 or long-text properties if you want them in HubSpot.
- Connection Degree, Shared Connections
HubSpot Contacts has no native fields for the connection-degree integer or the shared-connections count. Mutual Connections (the named-list column) is composed into the Notes property; these two are the numeric signals beside it.
If you need it. Map them by hand to custom contact properties if you run warm-intro plays from connection data.
- List Name, Scraped At
HubSpot Contacts has no native field for the Sales Navigator list a row came from or the date it was scraped. HubSpot lists are managed inside HubSpot.
If you need it. Map them by hand to custom contact properties if you want to record which Sales Navigator search a contact came from.
- Company Headcount
HubSpot Contacts has no native employee-count field. Company Headcount is company-level data that belongs on the HubSpot Company record.
If you need it. Run a separate Sales Navigator to HubSpot Companies pass to land headcount on the Company record.
Formatting and cleanup
LinkedIn Sales Navigator exports rarely match the format HubSpot expects. Fix these before you import.
- 1.Maps the work Email column to HubSpot's email field when the export includes it
- 2.Title-cases name fields
- 3.Maps the parsed Country column to HubSpot's Country/Region field
- 4.Sets Lifecycle Stage to Lead and Lead Status to New on every row, since the export carries neither
- 5.Composes Mutual Connections and the two previous-role slots into the Notes property as a labeled multi-line block, skipping empty slots
- 6.Normalizes country names to a standard form
- 7.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 HubSpot.
LinkedIn Sales Navigator to HubSpot 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.
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 HubSpot'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 HubSpot 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.
Why does the template set Lifecycle Stage and Lead Status?
The export doesn't carry a lifecycle stage or a lead status, but HubSpot has both fields and reps expect them filled. A freshly scraped Sales Navigator list is a Lead in the New status, so the template sets Lifecycle Stage to Lead and Lead Status to New on every row. If your process uses different values, change them, or remove them, in the column mapper before you run the job.
Where does the LinkedIn profile URL go?
The Profile URL column maps to HubSpot's LinkedIn Bio property. The separate Company URL column, which is the LinkedIn company page, is not mapped here because the company's page belongs on the HubSpot Company record.
Why isn't the Location column mapped?
Sales Navigator's Location is a free-text string like 'London, England, United Kingdom'. HubSpot Contacts has no native field for an unstructured location, so the template maps the parsed Country column instead. The Location column is listed in the Columns we don't use section.
Will this create duplicates if a contact already exists in HubSpot?
HubSpot uses email as the unique identifier for contacts. This template maps the work Email column, so when your export includes email, HubSpot dedupes on it and updates the existing contact instead of creating a new one. On baseline-tier exports the Email column is empty, so review your import settings in HubSpot to control how those rows match existing records.
