Lusha Prospecting
Copper People8 fieldsHow to import Lusha Prospecting data into Copper
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 Copper's single name field, then work email, job title, company, and the person's location 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 Copper's single Phone Number 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 Copper. The left column is the header in your CSV export. The right column is the Copper field it should map to.
| Lusha Prospecting column | Copper field | |
|---|---|---|
| First name → Last name | Name*name Copper uses a single name field on the People 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 | Company Namecompany_name | |
| Phone 1 → Phone 2 | Phone Numberphone_number Copper People have one Phone Number field. Phone 1 and Phone 2 are combined into it, taking the first available number in that order. TransformStandardized to international format (+1, +44, etc.) | |
| City | Cityaddress_city Lusha's Prospecting export ships the person's city, state, and country. They map to the Person's address fields. | |
| State | Stateaddress_state | |
| Country | Countryaddress_country |
Required by Copper.
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 Copper.
- Seniority
Copper People have no native seniority field. The data is real and useful, Copper just has no standard place for it.
If you need it. Add a custom field on the Copper Person for Seniority, then map it by hand.
- Departments
Copper People have no native department field. Lusha ships several departments per row, comma-separated.
If you need it. Add a custom field on the Copper Person for Departments, then map it by hand.
- Phone 2, Phone 1 type, Phone 2 type
Copper People have one Phone Number 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 Person.
If you need it. Add custom phone fields on the Copper Person if you want the second number or the type labels kept.
- Company domain, Company number of employees
These are company-level data points. Copper stores firmographics on the Company record in its data model, not People.
If you need it. Enrich the matched Copper Company after import using Lusha's company data, or add custom Company fields and update by company name.
- LinkedIn URL
Copper People have no native LinkedIn field on the standard layout.
If you need it. Add a custom URL field on the Copper Person called LinkedIn, then map this column to it by hand.
Formatting and cleanup
Lusha Prospecting exports rarely match the format Copper expects. Fix these before you import.
- 1.Combines First name and Last name into Copper'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 Number field with the first available number, checking Phone 1, then Phone 2
- 5.Maps Lusha's City, State, and Country columns to Copper's address fields
- 6.Normalizes country names to a standard form
- 7.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 Copper.
Lusha Prospecting to Copper 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 Copper 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.
What's a 'Person' in Copper?
Copper calls contacts People. The data model has People (individuals), Companies, Leads, and Opportunities. This template creates People records and links each one to the matched Company by name.
Why do you combine First name and Last name?
Copper People records use a single name field, not separate first and last name fields. The template combines the two columns with a space so each Person record displays correctly.
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. Copper People have one Phone Number field, so the template fills it with the first available of Phone 1 and Phone 2. The type columns are listed in the Columns we don't use section.
Will this create duplicate People in Copper?
Copper deduplicates People on email by default. People with matching emails update the existing record. New emails create new People. Lusha's credit-per-reveal model leaves some rows with a blank Work email; those rows will be created as new People every run, so filter them out or dedupe the CSV before import if you don't want repeats.
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.
