Lusha Prospecting
Pipedrive Contacts5 fieldsHow to import Lusha Prospecting data into Pipedrive
Lusha ships at least two CSV export shapes. This template handles the Prospecting export, the one with separate First name and Last name columns, Seniority and Departments, and a Phone 1 / Phone 2 structure. First name and Last name are combined into Pipedrive's single Name field, the company is matched to an organization, and work email and job title map directly. Lusha runs on a credit-per-reveal model, so any Work email or Phone column can be blank for contacts you have not revealed yet. Phone 1 and Phone 2 are combined into Pipedrive's single phone field. If your export has a single Contact name column instead, use the Lusha User Data template.
Field-by-field mapping
This is the complete column mapping from Lusha Prospecting to Pipedrive. The left column is the header in your CSV export. The right column is the Pipedrive field it should map to.
| Lusha Prospecting column | Pipedrive field | |
|---|---|---|
| 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 | |
| Work email | Emailemail TransformLowercased and trimmed | |
| Job title | Job Titlejob_title | |
| Company name | Organizationorg_name Matched to an existing Pipedrive organization, or a new one is created. | |
| Phone 1 → Phone 2 | Phonephone Pipedrive contacts have one phone field. Phone 1 and Phone 2 are combined into Phone, taking the first available number in that order. TransformStandardized to international format (+1, +44, etc.) |
Required by Pipedrive.
Columns we don't use
Your Lusha Prospecting export includes 11 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Pipedrive.
- Seniority
Pipedrive contacts have no native seniority field. The data is real and useful, Pipedrive just has no standard place for it.
If you need it. Add a custom contact field in Pipedrive for Seniority, then map it by hand.
- Departments
Pipedrive contacts have no native department field. Lusha ships several departments per row, comma-separated.
If you need it. Add a custom contact field in Pipedrive for Departments, then map it by hand.
- Phone 2, Phone 1 type, Phone 2 type
Pipedrive contacts have one phone field, which this template fills from the first available of Phone 1 and Phone 2. The second number and Lusha's phone-type labels have no native place on the contact.
If you need it. Add custom contact fields in Pipedrive if you want the second number or the type labels kept.
- City, State, 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 address on the contact, or move the data to the matched organization's address after import.
- Company domain, Company number of employees
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 Lusha's company data, or add custom organization fields and update by organization name.
- LinkedIn 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 this column to it by hand.
Formatting and cleanup
Lusha Prospecting exports rarely match the format Pipedrive expects. Fix these before you import.
- 1.Combines First name and Last name into 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 Phone 1, then Phone 2
- 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 Prospecting export and download a clean, import-ready file for Pipedrive.
Lusha Prospecting to Pipedrive FAQ
Which Lusha export does this template expect?
The Prospecting export, which ships separate First name and Last name columns, Seniority and Departments, and a Phone 1 / Phone 2 structure. If your export has a single Contact name column instead, that's the User Data export. Use the Lusha User Data to Pipedrive Contacts template for that shape.
How do I export from Lusha?
In Lusha Prospecting, build your search, save the contacts to a list, then open the list menu and click Export to CSV. Lusha emails you a download link when the file is ready. Upload that CSV 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.
How does the template handle Lusha's two phone columns?
Lusha's Prospecting export ships Phone 1 and Phone 2, each with a sibling type column. Pipedrive contacts have one phone field, so the template fills it with the first available of Phone 1 and Phone 2. The type columns are listed in the Columns we don't use section.
Why are some Work 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.
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 Prospecting 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.
