Lusha User Data
Pipedrive Contacts5 fieldsHow to import Lusha User Data into Pipedrive
Lusha ships at least two CSV export shapes. This template handles the User Data export, the one with a single Contact name column, three email slots, and six type-named phone slots. Lusha's single Contact name column is exactly what Pipedrive's single Name field expects, so it maps across verbatim. The template also maps work email, job title, and company. Lusha runs on a credit-per-reveal model, so any email or phone column can be blank for contacts you have not revealed yet. Mobile, Direct phone, and Phone are combined into Pipedrive's single phone field, mobile-first. If your export has separate First name and Last name columns, use the Lusha Prospecting template instead.
Field-by-field mapping
This is the complete column mapping from Lusha User Data to Pipedrive. The left column is the header in your CSV export. The right column is the Pipedrive field it should map to.
| Lusha User Data column | Pipedrive field | |
|---|---|---|
| Contact name | Name*name Lusha's User Data export ships the full name in a single Contact name column, which is exactly what Pipedrive's single Name field expects, so it maps across verbatim. | |
| Job title | Job Titlejob_title | |
| Work email | Emailemail TransformLowercased and trimmed | |
| Company name | Organizationorg_name Matched to an existing Pipedrive organization, or a new one is created. | |
| Mobile → Direct phone → Phone | Phonephone Pipedrive contacts have one phone field. Mobile, Direct phone, and Phone are combined into Phone, taking the first available number in that order. Mobile wins when present. TransformStandardized to international format (+1, +44, etc.) |
Required by Pipedrive.
Columns we don't use
Your Lusha User Data export includes 8 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Pipedrive.
- Work email 2, Private email
Pipedrive contacts have one native email field, which this template fills from Work email. A secondary work email and a personal email have no native place on the contact.
If you need it. Add custom contact fields in Pipedrive for the extra emails, then map them by hand.
- Mobile 2, Phone 2, Direct phone 2
Pipedrive contacts have one phone field, which this template fills from the first available of Mobile, Direct phone, and Phone. The second numbers in each pair have no native place on the contact.
If you need it. Add custom phone fields in Pipedrive if you want every number kept separately.
- LinkedIn profile
Pipedrive contacts have no native LinkedIn field.
If you need it. Add a custom Link field on the Pipedrive contact called LinkedIn, then map this column to it by hand.
- Industry, Sub industry
These are company-level data points. Pipedrive contacts have no native industry field, it belongs on the Pipedrive organization.
If you need it. Add a custom field on the Pipedrive organization for Industry, then update by organization name after import.
Formatting and cleanup
Lusha User Data exports rarely match the format Pipedrive expects. Fix these before you import.
- 1.Maps Lusha's single Contact name column to Pipedrive's single Name field
- 2.Lowercases and trims email addresses
- 3.Standardizes phone numbers to international format (+1, +44, etc.)
- 4.Fills the single phone field with the first available number, checking Mobile, then Direct phone, then Phone
- 5.Matches Company name to an existing Pipedrive organization, or creates a new one
- 6.Trims whitespace and removes blank rows
Or skip the manual work
Operelio runs this cleanup and mapping for you. Upload your Lusha User Data export and download a clean, import-ready file for Pipedrive.
Lusha User Data to Pipedrive FAQ
Which Lusha export does this template expect?
The User Data export, which ships a single Contact name column, three email slots, and six type-named phone slots. If your export has separate First name and Last name columns plus Seniority and Departments, that's the Prospecting export. Use the Lusha Prospecting to Pipedrive Contacts template for that shape.
How do I export from Lusha?
In Lusha, open the list you want, then use the list's export option to download a CSV. Lusha emails you a download link when the file is ready. Upload that CSV to Operelio.
Why doesn't this template split the name?
Pipedrive contacts use a single Name field, which is exactly the shape Lusha's User Data export already ships in its Contact name column. So the column maps across verbatim, no split needed.
Why are some email and phone columns blank?
Lusha uses a credit-per-reveal model, so contacts you haven't spent credits to reveal ship with blank email or phone columns. Operelio preserves those blanks rather than guessing values.
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 org.
Will this create duplicates if the contact already exists in Pipedrive?
Pipedrive's import dedupes on Name plus one of email, phone, or organization. A Lusha User Data row matches an existing Pipedrive contact when the name and at least one of email, phone, or organization align. Lusha's credit-per-reveal model leaves some rows with a blank Work email; those rows can still match on Name plus phone or organization if you've revealed at least one of those, otherwise they'll create new contacts every run, so filter or dedupe the CSV before import if you don't want repeats.
