Lusha Prospecting
Salesforce Leads13 fieldsHow to import Lusha Prospecting data into Salesforce Leads
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. It maps the export to Salesforce's standard lead fields: names, job title, work email, company, website, the person's location, and the LinkedIn profile URL. 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 the single Phone field, taking the first available. The LinkedIn URL column maps to the custom LinkedIn_URL__c Lead field, so create that field on the Lead object in Salesforce before importing, or repoint the mapping in the column mapper. Lead Source is set to Lusha and Status to Open - Not Contacted on every row. 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 Salesforce Leads. The left column is the header in your CSV export. The right column is the Salesforce Leads field it should map to.
Before you start
This template's destination has 3 required fields that need attention before upload. You can still use this template. The steps below tell you what to add and where.
- Email
Salesforce Leads require Email when org-level validation is on. Lusha's credit-per-reveal model leaves the Work email column blank for contacts you haven't spent credits to reveal.
What to do. Reveal the contacts in Lusha and re-export, or filter rows with blank Work email out of your CSV before uploading.
- Last NameLastName
Salesforce requires Last Name on every lead. Lusha's Prospecting export ships a Last name column on every row, so this is reliably populated.
What to do. Scan your CSV for blank Last name rows before uploading.
- Company
Salesforce requires Company on every lead. Lusha's Prospecting export ships a Company name column on every row, so this is reliably populated.
What to do. Scan your CSV for blank Company name rows before uploading. Fill any blanks with a placeholder ('Unknown').
| Lusha Prospecting column | Salesforce Leads field | |
|---|---|---|
| First name | First NameFirstName | |
| Last name | Last Name*LastName | |
| Job title | Title | |
| Work email | Email* TransformLowercased and trimmed | |
| Phone 1 → Phone 2 | Phone Salesforce Leads have one Phone field. Phone 1 and Phone 2 are combined into Phone, taking the first available number in that order. Check the type columns in the source for what Lusha returned. TransformStandardized to international format (+1, +44, etc.) | |
| Company name | Company* | |
| Company domain | Website Lusha's Company domain is the company's website root. Maps to the Lead's Website field. | |
| City | City | |
| State | State/ProvinceState | |
| Country | Country | |
| LinkedIn URL | LinkedIn URLLinkedIn_URL__c Maps to a custom Salesforce field called LinkedIn_URL__c. Create that field on the Lead object in Salesforce before importing, or open the mapping in Operelio and point the column at a different field instead. | |
| "Lusha" | Lead SourceLeadSource Set on every row. Change the value, or remove it, in the column mapper if your process records lead source differently. | |
| "Open - Not Contacted" | Lead StatusStatus Set on every row. This is Salesforce's standard new-lead status. If your org renamed its Lead Status picklist, change the value in the column mapper to match before you run the job. |
Required by Salesforce Leads.
Columns we don't use
Your Lusha Prospecting export includes 6 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Salesforce Leads.
- Seniority
Salesforce Leads have no native seniority field. The data is real and useful, Salesforce just has no standard place for it.
If you need it. Map it by hand to a custom Lead picklist field such as Seniority__c if you want seniority in Salesforce.
- Departments
Salesforce Leads have no native department field. Lusha ships several departments per row, comma-separated.
If you need it. Map it by hand to a custom Lead field called Departments__c if you want department in Salesforce.
- Phone 2, Phone 1 type, Phone 2 type
Salesforce Leads 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 Lead.
If you need it. Map them by hand to custom Lead fields if you want the second number or the type labels kept.
- Company number of employees
Salesforce Leads have no native employee-count field on the standard layout. Company number of employees is company-level data that belongs on the Salesforce Account record.
If you need it. Run a separate Lusha to Salesforce Accounts pass to land employee count on the Account record.
Formatting and cleanup
Lusha Prospecting exports rarely match the format Salesforce Leads expects. Fix these before you import.
- 1.Lowercases and trims email addresses
- 2.Standardizes phone numbers to international format (+1, +44, etc.)
- 3.Fills the single Phone field with the first available number, checking Phone 1, then Phone 2
- 4.Maps LinkedIn URL to the custom LinkedIn_URL__c Lead field
- 5.Sets Lead Source to Lusha and Status to Open - Not Contacted on every row
- 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 Lusha Prospecting export and download a clean, import-ready file for Salesforce Leads.
Lusha Prospecting to Salesforce Leads 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 with sibling type columns. If your export has a single Contact name column and three email slots instead, that's the User Data export. Use the Lusha User Data to Salesforce Leads 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 to map it to Salesforce lead fields.
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. Salesforce Leads 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 does the template set Lead Source and Status?
A freshly built Lusha prospect list is a new lead from Lusha, so the template sets Lead Source to Lusha and Status to Open - Not Contacted on every row. Open - Not Contacted is Salesforce's standard new-lead status. If your org renamed its Lead Status picklist, change the value in the column mapper to match before you run the job.
Does this template handle Lusha's LinkedIn URLs?
Yes. The LinkedIn URL column is mapped to a custom Salesforce field called LinkedIn_URL__c. Create that field on the Lead object in Salesforce before importing, or open the mapping in Operelio and point the column at a different field instead.
Will this create duplicate leads?
Salesforce checks for duplicates based on your org's matching rules. Review your duplicate settings in Salesforce Setup before importing to control how matches are handled.
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.
