Lusha User Data
Zoho Contacts7 fieldsHow to import Lusha User Data into Zoho Contacts
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 Zoho's 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 Zoho requires Last Name, so add one before import. Mobile goes to Zoho's dedicated Mobile field, and the Phone 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 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 User Data column | Zoho Contacts 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 Zoho 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 | Title | |
| Work email | Email* TransformLowercased and trimmed | |
| Mobile | Mobile Zoho Contacts have two phone fields. Lusha's Mobile lands on the dedicated Mobile field. TransformStandardized to international format (+1, +44, etc.) | |
| Direct phone → Phone | Phone Zoho's Phone field takes the first available work number: Direct phone first, then Phone. TransformStandardized to international format (+1, +44, etc.) | |
| Company name | Account NameAccount_Name |
Required by Zoho Contacts.
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 Zoho Contacts.
- Work email 2, Private email
Zoho 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 fields on the Zoho Contact for the extra emails, then map them by hand.
- Mobile 2, Phone 2, Direct phone 2
Zoho Contacts have two phone fields. Mobile fills the Mobile field and the Phone 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 phone fields on the Zoho Contact if you want every number kept separately.
- LinkedIn profile
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.
- Industry, Sub industry
Zoho Contacts have no native Industry field. Industry is company-level data and belongs on the Zoho Account record.
If you need it. Run a Lusha to Zoho Accounts pass to land industry on the Account, or map it by hand to a custom Contact field.
Formatting and cleanup
Lusha User Data exports rarely match the format Zoho Contacts 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 Zoho's dedicated Mobile field and fills the Phone 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 Zoho Contacts.
Lusha User Data to Zoho Contacts 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 Zoho 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. Zoho 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 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 profile 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.
