How to import ZoomInfo data into Copper
ZoomInfo exports contact lists as CSV files from Contact Search. This template maps the export to Copper People fields: First Name and Last Name are combined into Copper's single name field, then email, the phone, title, company, and the person's office address map directly. ZoomInfo's Contact Search export ships one person phone column, Direct Phone, plus a Company HQ Phone; Copper People have one Phone Number field, so the two are combined and the first available number wins. Phones are standardized, emails are lowercased, and country names are normalized. Mobile phone, intent, and scoop columns are tier-gated and not part of this template's expected column set. Company-level data like Industry and Company Revenue belongs on the Copper Company record and is listed in the Columns we don't use section.
Field-by-field mapping
This is the complete column mapping from ZoomInfo to Copper. The left column is the header in your CSV export. The right column is the Copper field it should map to.
| 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 | |
| Email Address | Email*email TransformLowercased and trimmed | |
| Direct Phone → Company HQ Phone | Phone Numberphone_number Copper People have one Phone Number field. Direct Phone and Company HQ Phone are combined into it, taking the first available number in that order. TransformStandardized to international format (+1, +44, etc.) | |
| Job Title | Titletitle | |
| Company Name | Company Namecompany_name | |
| Person Street | Streetaddress_street ZoomInfo ships the person's office address. That address block maps to the Person's address fields. The company HQ address block is a separate set of columns and is not mapped. | |
| Person City | Cityaddress_city | |
| Person State | Stateaddress_state | |
| Person Zip Code | Postal Codeaddress_postal_code | |
| Person Country | Countryaddress_country |
Required by Copper.
Columns we don't use
Your ZoomInfo export includes 26 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Copper.
- Salutation
Copper People have no native salutation field.
If you need it. Add a custom field on the Copper Person called Salutation, then map it by hand.
- Job Function, Management Level, Department
Copper People have no native fields for job function, seniority, or department.
If you need it. Add custom fields on the Copper Person for Job Function, Management Level, and Department, then map them by hand.
- Email Domain
Copper People have no native field for the email domain on its own. The domain is already part of the email address.
If you need it. None needed. The domain is already part of the Email Address this template maps.
- Company HQ Phone
Copper People have one Phone Number field, which this template fills from Direct Phone, then Company HQ Phone. The HQ number is a company switchboard number anyway.
If you need it. Add a custom phone field on the Copper Person for the company phone, then map it by hand.
- LinkedIn Contact Profile URL, LinkedIn Company Profile 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 the contact profile column to it by hand.
- Website, Industry, SIC Code, NAICS Code, Company Employees, Company Revenue, Company Founded Year, Company Type, Stock Ticker, Company Description
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 ZoomInfo's company data, or add custom Company fields and update by company name.
- Company HQ Address, Company HQ City, Company HQ State, Company HQ Zip, Company HQ Country
Copper People have one address block, which this template fills from ZoomInfo's Person address. The HQ address belongs on the Copper Company record.
If you need it. Land the company HQ address on the matched Copper Company record in a separate pass if you need it.
- Company Fax
Copper People have no native fax field, and ZoomInfo's Company Fax column is aging and mostly empty.
If you need it. None needed. This column is safe to ignore.
- Last Updated, Source
Copper People have no native fields for when ZoomInfo last refreshed the record or the constant Source value. Source is the literal 'ZoomInfo' on every row.
If you need it. Filter your ZoomInfo export on Last Updated before uploading, or add custom Person fields and map them by hand.
Formatting and cleanup
ZoomInfo 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 Direct Phone, then Company HQ Phone
- 5.Maps ZoomInfo's Person address block to Copper's address_street, address_city, address_state, address_postal_code, and address_country 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 ZoomInfo export and download a clean, import-ready file for Copper.
ZoomInfo to Copper FAQ
How do I export from ZoomInfo?
In ZoomInfo Sales, open Contact Search, apply your filters, select the records you want, and click Export to download a CSV. Upload that CSV to Operelio.
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 ZoomInfo columns with a space so each Person record displays correctly.
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.
How does the template handle ZoomInfo's phone columns?
ZoomInfo's Contact Search export ships a Direct Phone column for the person and a Company HQ Phone for the company switchboard. Copper People have one Phone Number field, so the template fills it with the first available number, checking Direct Phone first, then Company HQ Phone. Mobile Phone is tier-gated and is not part of this template's expected column set.
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.
Where do company-level fields like Industry and Company Revenue go?
They belong on the Copper Company record in Copper's data model, not the Person. After import, enrich the matched Company using ZoomInfo's company data, or run a separate ZoomInfo to Copper Companies pass.