Lusha Prospecting
HubSpot Contacts13 fieldsHow to import Lusha Prospecting data into HubSpot
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 HubSpot's standard contact fields: names, job title, work email, company, website, LinkedIn profile, and the person's location. Phone 1 and Phone 2 are combined into the main Phone field, taking the first available. Lifecycle Stage and Lead Status are set to Lead and New on every row. 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 HubSpot. The left column is the header in your CSV export. The right column is the HubSpot field it should map to.
| Lusha Prospecting column | HubSpot field | |
|---|---|---|
| First name | First Namefirstname | |
| Last name | Last Namelastname | |
| Job title | Job Titlejobtitle | |
| Work email | Emailemail TransformLowercased and trimmed | |
| Phone 1 → Phone 2 | Phone Numberphone Lusha's Prospecting export ships up to two phones, Phone 1 and Phone 2, each with a sibling type column. HubSpot's main Phone field takes the first available of Phone 1 and Phone 2. Check the type columns in the source for what Lusha returned. TransformStandardized to international format (+1, +44, etc.) | |
| "Lead" | Lifecycle Stagelifecyclestage Set on every row. Lusha doesn't ship a lifecycle stage, and a freshly built prospect list is a Lead. Change the value, or remove it, in the column mapper if your process is different. | |
| "New" | Lead Statushs_lead_status Set on every row. Lusha doesn't ship a lead status, and a newly imported prospect starts as New. Change the value, or remove it, in the column mapper if your process is different. | |
| Company name | Company Namecompany | |
| Company domain | Website URLwebsite Lusha's Company domain is the company's website root (e.g. example.com). Maps to HubSpot's Website property. | |
| LinkedIn URL | LinkedIn Biohs_linkedinbio Maps to HubSpot's LinkedIn Bio property, the home for a contact's LinkedIn profile. | |
| City | Citycity | |
| State | State/Regionstate | |
| Country | Country/Regioncountry |
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 HubSpot.
- Seniority
HubSpot Contacts has no native seniority field. The data is real and useful, HubSpot just has no standard place for it.
If you need it. Map it by hand to a custom contact property if you want seniority in HubSpot.
- Departments
HubSpot Contacts has no native department field. Lusha ships several departments per row, comma-separated.
If you need it. Map it by hand to a custom contact property if you want department in HubSpot.
- Phone 2, Phone 1 type, Phone 2 type
HubSpot Contacts has one main 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 properties if you want the second number or the type labels kept.
- Company number of employees
HubSpot Contacts has no native employee-count field. Company number of employees is company-level data that belongs on the HubSpot Company record.
If you need it. Run a separate Lusha to HubSpot Companies pass to land headcount on the Company record.
Formatting and cleanup
Lusha Prospecting exports rarely match the format HubSpot 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 main Phone field with the first available number, checking Phone 1, then Phone 2
- 4.Sets Lifecycle Stage to Lead and Lead Status to New on every row, since Lusha's export carries neither
- 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 HubSpot.
Lusha Prospecting to HubSpot 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 with sibling type columns. 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 HubSpot 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 indicating whether the number is direct, mobile, or HQ. HubSpot's main Phone field takes the first available of Phone 1 and Phone 2. The type columns are listed in the Columns we don't use section; check them in the source if you need to know what Lusha returned.
Why does the template set Lifecycle Stage and Lead Status?
Lusha's export doesn't carry a lifecycle stage or a lead status, but HubSpot has both fields and reps expect them filled. A freshly built prospect list is a Lead in the New status, so the template sets Lifecycle Stage to Lead and Lead Status to New on every row. Change them, or remove them, in the column mapper if your process is different.
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 if a contact already exists in HubSpot?
No. HubSpot uses email as the unique identifier for contacts. Rows whose email matches an existing contact update that record; rows with a new email create a new contact. 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.
