Lusha Prospecting
Zoho Contacts9 fieldsHow to import Lusha Prospecting data into Zoho Contacts
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 Zoho's standard contact fields: names, job title, work email, company, and the person's mailing address. 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 Zoho's Phone 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 Zoho Contacts. The left column is the header in your CSV export. The right column is the Zoho Contacts field it should map to.
| Lusha Prospecting column | Zoho Contacts field | |
|---|---|---|
| First name | First NameFirst_Name | |
| Last name | Last Name*Last_Name | |
| Job title | Title | |
| Work email | Email* TransformLowercased and trimmed | |
| Phone 1 → Phone 2 | Phone Zoho's Phone 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 | Account NameAccount_Name | |
| City | Mailing CityMailing_City Lusha's Prospecting export ships the person's city, state, and country. They map to the Contact's Mailing address fields. | |
| State | Mailing StateMailing_State | |
| Country | Mailing CountryMailing_Country |
Required by Zoho Contacts.
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 Zoho Contacts.
- Seniority
Zoho Contacts have no native seniority field. The data is real and useful, Zoho just has no standard place for it.
If you need it. Create a custom picklist field on the Zoho Contact called Seniority, then map it by hand.
- Departments
Zoho Contacts have no native department field. Lusha ships several departments per row, comma-separated.
If you need it. Create a custom field on the Zoho Contact called Departments, then map it by hand.
- Phone 2, Phone 1 type, Phone 2 type
Zoho Contacts have a Phone and a Mobile field. This template fills Phone 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 Zoho's Mobile field by hand, or create custom fields for the type labels.
- Company domain, Company number of employees
These are company-level data points. Zoho Contacts have no native fields for them, they belong on the Zoho Account record.
If you need it. Run a separate Lusha to Zoho Accounts pass to land these on the Account record.
- LinkedIn URL
Zoho Contacts have no native LinkedIn field on the standard layout.
If you need it. Create a custom URL field on the Zoho Contact called LinkedIn, then map this column to it by hand.
Formatting and cleanup
Lusha Prospecting exports rarely match the format Zoho Contacts expects. Fix these before you import.
- 1.Lowercases and trims email addresses
- 2.Standardizes phone numbers to international format (+1, +44, etc.)
- 3.Fills Zoho's Phone field with the first available number, checking Phone 1, then Phone 2
- 4.Maps Lusha's City, State, and Country columns to Zoho's Mailing 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 Zoho Contacts.
Lusha Prospecting to Zoho Contacts 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 Zoho 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. The template fills Zoho's Phone field 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 if a contact already exists in Zoho?
Zoho deduplicates Contacts on Email by default. Rows whose email matches an existing contact update that record. 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. You can adjust the match field in Setup, Data Administration, Deduplication if your team uses a different convention.
Why isn't the LinkedIn URL mapped?
Zoho Contacts have no native LinkedIn field on the standard layout. The Columns we don't use section explains the custom-field workaround: add a URL field called LinkedIn to the Contact and map the column to it by hand.
