Lusha Prospecting
Close Contacts5 fieldsHow to import Lusha Prospecting data into Close
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. First name and Last name are combined into Close's single name field, then work email, job title, and company map directly. 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 Close's single phone field. 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 Close. The left column is the header in your CSV export. The right column is the Close field it should map to.
| Lusha Prospecting column | Close field | |
|---|---|---|
| First name → Last name | Name*name Close uses a single name field on the contact record, so First name and Last name are combined into one with a space between them. TransformFirst name and Last name combined with a space | |
| Work email | Emailemail TransformLowercased and trimmed | |
| Job title | Titletitle | |
| Company name | Companycompany | |
| Phone 1 → Phone 2 | Phonephone This template's Close schema has 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.) |
Required by Close.
Columns we don't use
Your Lusha Prospecting export includes 11 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Close.
- Seniority
This template's Close schema has no seniority field. The data is real and useful, Close just has no standard place for it here.
If you need it. Add a custom contact field on the Close contact for Seniority, then map it by hand.
- Departments
This template's Close schema has no department field. Lusha ships several departments per row, comma-separated.
If you need it. Add a custom contact field on the Close contact for Departments, then map it by hand.
- Phone 2, Phone 1 type, Phone 2 type
This template's Close schema has 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. Close supports multiple phones via its API. Add the second number to the Close contact after import, or use Close's API for bulk multi-phone imports.
- City, State, Country
This template's Close schema has no address fields. Addresses live on the Lead, Close's company-equivalent record, not the contact.
If you need it. Update the matched Close Lead with the address after import, or add custom address fields on the Close contact.
- Company domain, Company number of employees
These are company-level data points. Close stores firmographics on the Lead in its data model, not on the contact.
If you need it. Enrich the matched Close Lead after import using Lusha's company data, or add custom Lead fields and update by company name.
- LinkedIn URL
This template's Close schema has no LinkedIn field.
If you need it. Add a custom URL field on the Close contact called LinkedIn, then map this column to it by hand.
Formatting and cleanup
Lusha Prospecting exports rarely match the format Close expects. Fix these before you import.
- 1.Combines First name and Last name into Close's single name field
- 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.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 Close.
Lusha Prospecting to Close 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 Close 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.
Why do you combine First name and Last name?
Close uses a single name field on the contact record, not separate first and last name fields. The template combines the two columns with a space so the contact records look right in Close.
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. This template's Close schema has one phone field, so the template fills it with the first available of Phone 1 and Phone 2. Close supports multiple phones via its API if you need the second number kept.
Where do I import the CSV into Close?
In Close, go to Leads, click the + button at the top, then choose Import, or use Close's CSV import flow under Settings, then Import Leads. Close's import wizard handles the Lead-to-Contact link based on the Company column.
Will this create duplicate contacts?
Close groups contacts under their Lead (company) record. If a Lead with the same Company name already exists, the new contacts are added to it. Close doesn't auto-dedupe contacts by email by default, so spot-check or use Close's bulk-merge tools if you re-import the same prospects.
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.
