Lusha User Data
Close Contacts5 fieldsHow to import Lusha User Data into Close
Lusha ships at least two CSV export shapes. This template handles the User Data export, the one with a single Contact name column, three email slots, and six type-named phone slots. Lusha's single Contact name column is exactly what Close's single name field expects, so it maps across verbatim. The template also maps work email, job title, and company. Lusha runs on a credit-per-reveal model, so any email or phone column can be blank for contacts you have not revealed yet. Mobile, Direct phone, and Phone are combined into Close's single phone field, mobile-first. 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 Close. The left column is the header in your CSV export. The right column is the Close field it should map to.
| Lusha User Data column | Close field | |
|---|---|---|
| Contact name | Name*name Lusha's User Data export ships the full name in a single Contact name column, which is exactly what Close's single name field expects, so it maps across verbatim. | |
| Job title | Titletitle | |
| Work email | Emailemail TransformLowercased and trimmed | |
| Company name | Companycompany | |
| Mobile → Direct phone → Phone | Phonephone This template's Close schema has one phone field. Mobile, Direct phone, and Phone are combined into Phone, taking the first available number in that order. Mobile wins when present. TransformStandardized to international format (+1, +44, etc.) |
Required by Close.
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 Close.
- Work email 2, Private email
This template's Close schema has one email field, which this template fills from Work email. A secondary work email and a personal email have no native place on the contact here.
If you need it. Close supports multiple emails via its API. Add the extra emails to the Close contact after import, or use Close's API for bulk multi-email imports.
- Mobile 2, Phone 2, Direct phone 2
This template's Close schema has one phone field, which this template fills from the first available of Mobile, Direct phone, and Phone. The second numbers in each pair have no native place on the contact here.
If you need it. Close supports multiple phones via its API. Add the extra numbers to the Close contact after import, or use Close's API for bulk multi-phone imports.
- LinkedIn profile
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.
- Industry, Sub industry
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.
Formatting and cleanup
Lusha User Data exports rarely match the format Close expects. Fix these before you import.
- 1.Maps Lusha's single Contact name column to 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 Mobile, then 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 Close.
Lusha User Data to Close 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 Close 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.
Why doesn't this template split the name?
Close uses a single name field on the contact record, which is exactly the shape Lusha's User Data export already ships in its Contact name column. So the column maps across verbatim, no split needed.
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.
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.
