Lusha User Data
Zoho Leads8 fieldsHow to import Lusha User Data into Zoho Leads
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 lead 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 both Last Name and Company on every Lead, so add a last name before import. Mobile, Direct phone, and Phone are combined into the single Phone field, mobile-first. Lead Source is set to Lusha and Lead Status to Not Contacted on every row. 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 Leads. The left column is the header in your CSV export. The right column is the Zoho Leads field it should map to.
| Lusha User Data column | Zoho Leads 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 → Direct phone → Phone | Phone Zoho Leads have 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.) | |
| Company name | Company* | |
| "Lusha" | Lead SourceLead_Source Set on every row. Change the value, or remove it, in the column mapper if your process records lead source differently. | |
| "Not Contacted" | Lead StatusLead_Status Set on every row. This is Zoho's standard new-lead status. If your org renamed its Lead Status picklist, change the value in the column mapper to match before you run the job. |
Required by Zoho Leads.
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 Leads.
- Work email 2, Private email
Zoho Leads 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 Lead.
If you need it. Create custom fields on the Zoho Lead for the extra emails, then map them by hand.
- Mobile 2, Phone 2, Direct phone 2
Zoho Leads have 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 Lead.
If you need it. Create custom phone fields on the Zoho Lead if you want every number kept separately.
- LinkedIn profile
Zoho Leads have no native LinkedIn field on the standard layout.
If you need it. Create a custom URL field on the Zoho Lead called LinkedIn, then map this column to it by hand.
- Industry, Sub industry
Zoho Leads have an Industry field at the API level, but Operelio's exposed Zoho Leads schema is the core lead field set. Industry is company-level data anyway.
If you need it. Enrich the lead in Zoho after import, or convert the lead to a Contact and Account and put industry on the Account record.
Formatting and cleanup
Lusha User Data exports rarely match the format Zoho Leads 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.Fills the single Phone field with the first available number, checking Mobile, then Direct phone, then Phone
- 5.Sets Lead Source to Lusha and Lead Status to Not Contacted on every row
- 6.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 Leads.
Lusha User Data to Zoho Leads 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 Leads 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 are these going to Zoho Leads instead of Contacts?
This template is for users treating Lusha contacts as net-new leads in Zoho. Leads are the right destination for prospects you haven't qualified yet. If you want to import them as Zoho Contacts with an Account link instead, use the Lusha User Data to Zoho Contacts template.
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 does the template set Lead Source and Lead Status?
A freshly revealed Lusha list is a new lead from Lusha, so the template sets Lead Source to Lusha and Lead Status to Not Contacted on every row. Not Contacted is Zoho's standard new-lead status. If your org renamed its picklist, change the value in the column mapper before you run the job.
Will this create duplicate leads in Zoho?
Zoho uses Email as the unique-value field on leads by default, so rows with matching emails update the existing record rather than creating a duplicate. You can change the match field in Setup, Data Administration, Deduplication if your team uses a different convention.
