Lusha Prospecting
Freshsales Contacts9 fieldsHow to import Lusha Prospecting data into Freshsales
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 Freshsales' standard contact fields: names, job title, work email, company, and the person's location. 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 Work Number field, taking the first available. 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 Freshsales. The left column is the header in your CSV export. The right column is the Freshsales field it should map to.
| Lusha Prospecting column | Freshsales field | |
|---|---|---|
| First name | First Namefirst_name | |
| Last name | Last Name*last_name | |
| Job title | Job Titlejob_title | |
| Work email | Email*email TransformLowercased and trimmed | |
| Phone 1 → Phone 2 | Work Numberwork_number Freshsales' Work Number field takes the first available number: Phone 1 first, then Phone 2. Check the type columns in the source for what Lusha returned. TransformStandardized to international format (+1, +44, etc.) | |
| Company name | Company Namecompany_name | |
| City | Citycity Lusha's Prospecting export ships the person's city, state, and country. They map to the contact's address fields. | |
| State | Statestate | |
| Country | Countrycountry |
Required by Freshsales.
Columns we don't use
Your Lusha Prospecting export includes 8 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Freshsales.
- Seniority
Freshsales contacts have no native seniority field. The data is real and useful, Freshsales just has no standard place for it.
If you need it. Create a custom contact field in Freshsales called Seniority, then map it by hand.
- Departments
Freshsales contacts have no native department field. Lusha ships several departments per row, comma-separated.
If you need it. Create a custom contact field in Freshsales called Departments, then map it by hand.
- Phone 2, Phone 1 type, Phone 2 type
Freshsales contacts have a Work Number and a Mobile Number field. This template fills Work Number 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 the second number to Freshsales' Mobile Number field by hand, or create custom fields for the type labels.
- Company domain, Company number of employees
These are company-level data points. Freshsales stores firmographics on the Sales Account record, not the Contact.
If you need it. Enrich the matched Freshsales Sales Account record after import using Lusha's company data, or add custom contact fields if you need the values on the contact itself.
- LinkedIn URL
Freshsales contacts have no native LinkedIn field.
If you need it. Create a custom URL field on the Freshsales contact called LinkedIn, then map this column to it by hand.
Formatting and cleanup
Lusha Prospecting exports rarely match the format Freshsales 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 Work Number field with the first available number, checking Phone 1, then Phone 2
- 4.Maps Lusha's City, State, and Country columns to Freshsales' address fields
- 5.Normalizes country names to a standard form
- 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 Freshsales.
Lusha Prospecting to Freshsales 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 Freshsales 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.
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. Freshsales contacts have a Work Number and a Mobile Number field; the template fills Work Number 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?
Freshsales deduplicates contacts on email by default. Rows with matching emails update the existing contact, and new emails create new contacts. Lusha's credit-per-reveal model leaves some rows with a blank Work email; those rows will be created as new contacts every run, so filter them out or dedupe the CSV before import if you don't want repeats.
Where do company-level fields like Company number of employees go?
They live on the Freshsales Sales Account record in Freshsales' data model, not on the Contact. After import, enrich the matched Sales Account using Lusha's company data, either manually or with a separate Operelio job that targets the Sales Account record.
