Lusha User Data
Salesforce Contacts8 fieldsHow to import Lusha User Data into Salesforce Contacts
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 contact fields: name, job title, work email, and mobile phone. 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. Salesforce Contacts associate to an Account rather than carrying a company name, so Company name is left for you to link after import. 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 Contacts. The left column is the header in your CSV export. The right column is the Salesforce Contacts field it should map to.
| Lusha User Data column | Salesforce Contacts 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. The company column is mapped to Account Name, so each Contact is linked to its Account as it lands. 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 Contact field that's often hidden in the default layout. If you don't see it, add MobilePhone to your Contact page layout in Salesforce setup before importing. TransformStandardized to international format (+1, +44, etc.) | |
| Direct phone → Phone | Phone Salesforce Contacts 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.) | |
| LinkedIn profile | LinkedIn URLLinkedIn_URL__c Maps to a custom Salesforce field called LinkedIn_URL__c. Create that field on the Contact object in Salesforce before importing, or open the mapping in Operelio and point the column at a different field instead. | |
| Company name | Account NameAccountName Matched to an existing Salesforce Account by name, or a new one is created and the Contact is linked to it. A Salesforce Contact has no company field of its own, so this is what puts the person against the right company. |
Required by Salesforce Contacts.
Columns we don't use
Your Lusha User Data export includes 7 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Salesforce Contacts.
- Industry, Sub industry
Salesforce Contacts have no native Industry field. Industry is company-level data and belongs on the Account record.
If you need it. Run a Lusha to Salesforce Accounts pass to land industry on the Account, or map it by hand to a custom Contact field.
- Work email 2, Private email
Salesforce 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. Map them by hand to custom Contact 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 Contact.
If you need it. Map them by hand to custom Contact fields if you want every number kept separately.
Formatting and cleanup
Lusha User Data exports rarely match the format Salesforce Contacts expects. Fix these first.
- 1.Matches Company name to an existing Salesforce Account, or creates one, and links the Contact to it
- 2.Splits Contact name into First Name and Last Name on the first space
- 3.Lowercases and trims email addresses
- 4.Standardizes phone numbers to international format (+1, +44, etc.)
- 5.Maps Mobile directly to MobilePhone; fills Phone with the first available of Direct phone, Phone
- 6.Maps LinkedIn profile to the custom LinkedIn_URL__c Contact field
- 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 file for Salesforce Contacts, or connect Salesforce and push the records straight in. You see what will be created and updated before anything is written.
Lusha User Data to Salesforce Contacts 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 Contacts template for that shape.
Why Salesforce Contacts instead of Leads?
Contacts are the right destination when the person already belongs to an account you work, or when your team skips the Lead object. If you're importing cold prospects, the Lusha User Data to Salesforce Leads template is the better fit for that. Both ship so you can pick at the destination picker.
How do Contacts link to Accounts?
The company column is mapped to Account Name. On a push, Operelio looks for a Salesforce Account with that name, creates one if there isn't a match, and sets the Contact's Account to it. A Salesforce Contact has no company field of its own, so this is what stops people landing with nothing against them. The report before the push says how many Accounts it will need to create.
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 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.
Will this create duplicate contacts?
Not if you push from Operelio. A push matches on email before anything is written: a match updates the existing record, anything else is created, and the report shows you the split first. If you import the file through Salesforce instead, its own rules decide. Salesforce checks for duplicates based on your org's matching rules. Review your duplicate settings in Salesforce Setup before importing, especially if you already have contacts from the same Lusha lists.
