Lusha User Data
Salesforce Leads11 fieldsHow to import Lusha User Data into Salesforce Leads
This template handles Lusha's User Data export, which ships a single Contact name column, three email slots, and six type-named phone slots. It maps to Salesforce's standard lead fields: name, job title, work email, company, mobile phone, LinkedIn profile, and industry. Contact name splits into First Name and Last Name on the first space; a single-word name leaves Last Name empty, so add one before import. Mobile maps directly to MobilePhone; Direct phone and Phone coalesce into the Phone field. The LinkedIn profile 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 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 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 User Data export ships the full name in a single Contact name column, which the template splits on the last space. A single-word name leaves Last Name blank.
What to do. Scan your CSV for single-word names in the Contact name column before uploading and add a last name where possible.
- Company
Salesforce requires Company on every lead. Lusha's User Data 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 User Data column | Salesforce Leads field | |
|---|---|---|
| Contact name | First NameFirstName Lusha's User Data export ships the full name in a single Contact name column. The first space-separated word is taken as the first name. TransformSplit on first space | |
| Contact name | Last Name*LastName Salesforce requires Last Name. The rest of the Contact name after the first space is taken. A single-word name leaves Last Name empty, so the row will fail to import. Scan your CSV for single-word names before running and add a last name where possible. TransformSplit on first space | |
| Job title | Title | |
| Work email | Email* TransformLowercased and trimmed | |
| Mobile | Mobile PhoneMobilePhone Maps to Salesforce's MobilePhone field. MobilePhone is a standard Salesforce Lead field that's often hidden in the default layout. If you don't see it, add MobilePhone to your Lead page layout in Salesforce setup before importing. TransformStandardized to international format (+1, +44, etc.) | |
| Direct phone → Phone | Phone Salesforce Leads have one Phone field. Direct phone and Phone are combined into Phone, taking the first available number in that order. Mobile maps to MobilePhone separately. TransformStandardized to international format (+1, +44, etc.) | |
| Company name | Company* | |
| Industry | Industry Lusha ships a single industry value per row, so it maps straight to the Lead's Industry field. | |
| LinkedIn profile | 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 User Data 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.
- Work email 2, Private email
Salesforce Leads 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 Lead.
If you need it. Map them by hand to custom Lead fields if you want every email kept.
- Mobile 2, Phone 2, Direct phone 2
Mobile maps to MobilePhone, and the Phone field is filled from the first available of Direct phone and Phone. The second numbers in each pair have no native place on the Lead.
If you need it. Map them by hand to custom Lead fields if you want every number kept separately.
- Sub industry
Salesforce Leads have no native sub-industry field. The main Industry value maps; Lusha's finer-grained Sub industry has no standard place.
If you need it. Map it by hand to a custom Lead field if you want the sub-industry kept.
Formatting and cleanup
Lusha User Data exports rarely match the format Salesforce Leads expects. Fix these before you import.
- 1.Splits Contact name into First Name and Last Name on the first space
- 2.Lowercases and trims email addresses
- 3.Standardizes phone numbers to international format (+1, +44, etc.)
- 4.Maps Mobile directly to MobilePhone; fills Phone with the first available of Direct phone, Phone
- 5.Maps LinkedIn profile to the custom LinkedIn_URL__c Lead field
- 6.Sets Lead Source to Lusha and Status to Open - Not Contacted on every row
- 7.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 Salesforce Leads.
Lusha User Data to Salesforce Leads 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 Salesforce Leads 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 to map it to Salesforce lead fields.
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.
How does the Contact name column split?
Lusha's User Data export ships the full name in one Contact name column. The template splits it into First Name and Last Name on the first space. A single-word name goes to First Name and leaves Last Name empty. Salesforce requires Last Name, so rows with single-word names will fail to import. Scan your CSV for single-word names before running and add a last name where possible.
Why does the template set Lead Source and Status?
A freshly revealed Lusha 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.
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.
