Lusha User Data
Freshsales Contacts7 fieldsHow to import Lusha User Data into Freshsales
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 Freshsales' standard contact fields: name, job title, work email, and company. Contact name splits into First Name and Last Name on the first space; a single-word name leaves Last Name empty, and Freshsales requires Last Name, so add one before import. Mobile goes to the dedicated Mobile Number field, and the Work Number field takes the first available work number from Direct phone or Phone. 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 Freshsales. The left column is the header in your CSV export. The right column is the Freshsales field it should map to.
| Lusha User Data column | Freshsales field | |
|---|---|---|
| Contact name | First Namefirst_name 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*last_name Freshsales 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 | Job Titlejob_title | |
| Work email | Email*email TransformLowercased and trimmed | |
| Mobile | Mobile Numbermobile_number Freshsales contacts have two phone fields. Lusha's Mobile lands on the dedicated Mobile Number field. TransformStandardized to international format (+1, +44, etc.) | |
| Direct phone → Phone | Work Numberwork_number Freshsales' Work Number field takes the first available work number: Direct phone first, then Phone. TransformStandardized to international format (+1, +44, etc.) | |
| Company name | Company Namecompany_name |
Required by Freshsales.
Columns we don't use
Your Lusha User Data export includes 8 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Freshsales.
- Work email 2, Private email
Freshsales 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. Create custom contact fields in Freshsales for the extra emails, then map them by hand.
- Mobile 2, Phone 2, Direct phone 2
Freshsales contacts have two phone fields. Mobile fills the Mobile Number field and the Work Number 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. Create custom contact fields in Freshsales if you want every number kept separately.
- LinkedIn profile
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.
- Industry, Sub industry
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.
Formatting and cleanup
Lusha User Data exports rarely match the format Freshsales 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.Sends Mobile to Freshsales' Mobile Number field and fills the Work Number field with the first available work number (Direct phone, then Phone)
- 5.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 Freshsales.
Lusha User Data to Freshsales 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 Freshsales Contacts 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.
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. Freshsales 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 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 Industry 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.
