Lusha Prospecting
Salesforce Contacts11 fieldsHow to import Lusha Prospecting data into Salesforce Contacts
This template handles Lusha's Prospecting export, which ships separate First name and Last name columns, Seniority and Departments, and a Phone 1 / Phone 2 structure. It maps to Salesforce's standard contact fields: names, job title, work email, department, and the mailing address. Phone 1 and Phone 2 are combined into the single Phone field. Lusha's Departments column is comma-separated, so the template takes the first listed department. 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 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 Contacts. The left column is the header in your CSV export. The right column is the Salesforce Contacts field it should map to.
| Lusha Prospecting column | Salesforce Contacts field | |
|---|---|---|
| First name | First NameFirstName | |
| Last name | Last Name*LastName Salesforce requires a Last Name on every Contact. The company column is mapped to Account Name, so each Contact is linked to its Account as it lands. | |
| Job title | Title | |
| Work email | Email TransformLowercased and trimmed | |
| Phone 1 → Phone 2 | Phone Salesforce 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.) | |
| Departments → first | Department Lusha ships several departments per row, comma-separated. Salesforce's Department field holds one value, so the template takes the first listed department. Lusha does not order departments primary-first, so this is the first listed one, not necessarily the main one. To keep the full list, remove the split in the column mapper. | |
| City | Mailing CityMailingCity Lusha's Prospecting export ships the person's city, state, and country. They map to the Contact's Mailing City, State, and Country. Salesforce Contacts in this template's schema have no Mailing Street or Postal Code field. | |
| State | Mailing StateMailingState | |
| Country | Mailing CountryMailingCountry | |
| LinkedIn URL | 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 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 Contacts.
- Seniority
Salesforce Contacts 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 Contact field if you want seniority in Salesforce.
- Phone 2, Phone 1 type, Phone 2 type
Salesforce 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. Map them by hand to custom Contact fields if you want the second number or the type labels kept.
- Company domain, Company number of employees
These are company-level data points. Salesforce Contacts have no native fields for them, they belong on the Salesforce Account record.
If you need it. Run a separate Lusha to Salesforce Accounts pass to land these on the Account record.
Formatting and cleanup
Lusha Prospecting 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.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.Takes the first department from Lusha's comma-separated Departments list, so a single value lands in Salesforce's Department field
- 6.Maps LinkedIn URL to the custom LinkedIn_URL__c Contact field
- 7.Normalizes country names to a standard form
- 8.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 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 Prospecting to Salesforce Contacts 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 and three email slots instead, that's the User Data export. Use the Lusha User Data 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 Prospecting 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.
Where does the Departments column go?
Lusha ships several departments per row, comma-separated. Salesforce's Department field holds one value, so the template takes the first listed department. Lusha does not order departments primary-first, so this is the first listed one, not necessarily the main one. To keep the full list, remove the split on the Department row in the column mapper.
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 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.
