LinkedIn Sales Navigator
Copper People5 fieldsHow to import LinkedIn Sales Navigator data into Copper
LinkedIn Sales Navigator lead lists are pulled into a CSV by a scraper like Evaboot. This template maps that export to Copper's People fields: it combines First Name and Last Name into Copper's single Name field, then maps job title, company name, and the work email. Email carries data on Evaboot Pro tiers and is blank on the baseline export. Copper stores firmographics on the Company record, not People. Mutual connections and the contact's two previous roles are composed into Copper's Details 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 company data and the location are listed in the Columns we don't use section.
Field-by-field mapping
This is the complete column mapping from LinkedIn Sales Navigator to Copper. The left column is the header in your CSV export. The right column is the Copper field it should map to.
| LinkedIn Sales Navigator column | Copper 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 Copper uses a single Name field on the People record, 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 | Titletitle | |
| Company Name | Company Namecompany_name | |
| Detailsdetails Three slots compose into Copper's Details 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 Copper.
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 Copper.
- 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 Copper'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
Copper People have no native LinkedIn field on the standard layout.
If you need it. Add a custom URL field on the Copper Person called LinkedIn, then map Profile URL to it by hand.
- Location, Country
Sales Navigator's Location is a free-text string and the standard export has no parsed person city or state. Copper's address fields expect parsed components, so there is no clean way to fill them from this export.
If you need it. Map Country by hand to the Copper Person's Country field if you only need the country, or map Location to a custom field for the verbatim string.
- Company Industry, Company Size, Company Headcount, Company URL, Company Website, Company Founded, Company Description, Company Specialties
These are company-level data points. Copper stores firmographics on the Company record in its data model, not People.
If you need it. Enrich the matched Copper Company after import using Sales Navigator's company data, or add custom Company fields and update by company name.
- Company Location, Company Country, Company City
These describe where the company is, not where the contact is. They belong on the Copper Company record.
If you need it. Land the company location on the matched Copper Company record in a separate pass if you need it.
- Years in Role, Years in Company
Copper People have no native fields for role or company tenure. The data is a useful 'just changed jobs' filter, Copper just has no standard place for it.
If you need it. Add custom number fields on the Copper Person for tenure, then map them by hand.
- Description, Education Top
Copper People have no native field for a LinkedIn About summary or a top education entry. The data is real, Copper just has no standard place for it.
If you need it. Add custom fields on the Copper Person, then map them by hand.
- Skills, Languages
Copper People 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 fields on the Copper Person if you want them, then map them by hand.
- Connection Degree, Shared Connections
Copper People have no native fields for the connection-degree integer or the shared-connections count. Mutual Connections (the named-list column) is composed into the Details field; these two are the numeric signals beside it.
If you need it. Add custom fields on the Copper Person if you run warm-intro plays from connection data.
- List Name, Scraped At
Copper People 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 fields on the Copper Person if you want to record which Sales Navigator search a contact came from.
Formatting and cleanup
LinkedIn Sales Navigator exports rarely match the format Copper expects. Fix these before you import.
- 1.Maps the work Email column to Copper's email field when the export includes it
- 2.Combines First Name and Last Name into Copper's single Name field
- 3.Title-cases name fields
- 4.Composes Mutual Connections and the two previous-role slots into the Details 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 Copper.
LinkedIn Sales Navigator to Copper 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 Copper'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 Copper Person 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 this template combine First Name and Last Name?
Copper People records use a single Name field, not separate first and last name fields. The template combines the two columns with a space so each Person record displays correctly.
Where do company-level fields like industry and headcount go?
Copper stores firmographics on the Company record in its data model, not People. This template creates People records, so the company industry, headcount, and the rest of the company data are not mapped. Enrich the matched Copper Company after import using Sales Navigator's company data.
Will this create duplicate People in Copper?
Copper deduplicates People on email by default. This template maps the work Email column, so when your export includes email, Copper matches on it. On baseline-tier exports the Email column is empty, so review your import settings in Copper to control how those rows match existing People.
Where do I import the CSV into Copper?
In Copper, go to Settings, then Data, then Import Records, and upload the file Operelio produces. The import wizard matches the column headers to People fields.
