Cognism
Copper People8 fieldsHow to import Cognism data into Copper
Cognism exports prospect lists as CSV files from Prospector. This template maps the export to Copper's People fields: it combines First Name and Last Name into Copper's single name field, and maps email, job title, company, and the person's location. Cognism ships four phone columns; Copper People have one Phone Number field, so Mobile, Direct, Office, and HQ are combined and the first available number wins, with Mobile, including Cognism's Diamond-verified mobiles, taking priority. Copper calls contacts People. Phones are standardized, emails are lowercased, and country names are normalized. The company's registered office and HQ addresses are company-level data and belong on the Copper Company record. Data Copper has no standard People field for, like Seniority and the company firmographics, is listed in the Columns we don't use section.
Field-by-field mapping
This is the complete column mapping from Cognism to Copper. The left column is the header in your CSV export. The right column is the Copper field it should map to.
| Cognism column | Copper field | |
|---|---|---|
| First Name + Last Name | Name*name Copper uses a single name field on the People record, so the template combines the two columns with a space between them. TransformFirst Name and Last Name combined with a space | |
| Email*email TransformLowercased and trimmed | ||
| Mobile → Direct → Office → HQ | Phone Numberphone_number Copper People have one Phone Number field. It takes the first available number: Mobile first, including Cognism's Diamond-verified mobiles, then Direct, then Office, then HQ. Whichever is present wins; the rest are skipped. TransformStandardized to international format (+1, +44, etc.) | |
| Job Title | Titletitle | |
| Company Name | Company Namecompany_name | |
| City | Cityaddress_city Cognism's person-level City column maps to the Copper Person's City field. The company's City and HQ City columns are not mapped here; they belong on the Copper Company record. | |
| State | Stateaddress_state Cognism's person-level State column maps to the Copper Person's State field. The company's State columns are not mapped here. | |
| Country | Countryaddress_country Cognism's person-level Country column maps to the Copper Person's Country field. The company's Country columns are not mapped here. |
Required by Copper.
Columns we don't use
Your Cognism export includes 47 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.
- Department
Copper People have no native department field.
If you need it. Add a custom field on the Copper Person for Department, then map it by hand.
- Industries
Industry sits on the Company record in Copper's data model, not People.
If you need it. After import, update the matching Copper Company record's Industry field, or map it by hand to a custom Person field.
- Technologies
Copper People have no native field for a company's tech stack.
If you need it. Add a custom field on the Copper Person, or land it on the matched Copper Company record.
- Email Quality
Copper People have no native field for an email confidence flag. The Verified Email or Likely Email signal is useful for filtering, Copper just has no standard place for it.
If you need it. Add a custom field on the Copper Person if you want to filter on email quality.
- Education
Copper People have no native education field.
If you need it. Add a custom field on the Copper Person if you want it.
- List Name
Copper People have no native field for the source list a row came from.
If you need it. Add a custom field on the Copper Person if you want to record which Cognism list a contact came from.
- Diamond Record
Copper People have no native field for Cognism's Diamond-verified flag.
If you need it. Add a custom field on the Copper Person if you want to keep the flag.
- Profile ID
Copper People have no native field for an external ID. Copper matches People on email.
If you need it. Add a custom field on the Copper Person if you want Cognism's ID for re-import matching.
- sId
Cognism's internal composite ID has no downstream use in a CRM.
If you need it. None needed. This column is safe to ignore.
- Company Alias
Copper People have no native field for an alternate company trading name. It belongs on the Company record anyway, and is often the same as Company Name.
If you need it. Add a custom field on the Copper Company record if you want it.
- Lead Source
Every Cognism row carries the literal value 'Cognism'. Copper People have no native lead source field on the standard layout.
If you need it. Add a custom field on the Copper Person and set it by hand if you want the source recorded.
- Personal 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.
- Website, Headcount, Financials, Company Type, Company Description, Company Founded Year, Company Linkedin URL
These are company-level data points. Copper Website, Employee Count, and Annual Revenue belong on the Company record, not People.
If you need it. Enrich the matched Copper Company after import using Cognism's company data, or add custom Company fields and update by company name.
- Company Address Line, Company City, Company Post Code/ZIP, Company County/State, Company Country
These are the company's registered office address. The Copper Person's address fields are filled from the person-level City, State, and Country columns instead, since those describe where the contact actually is. The company's registered office belongs on the Copper Company record.
If you need it. Land the registered office address on the Copper Company record in a separate pass. If you would rather use the company's office address on the Person, swap the mappings by hand in the column mapper.
- Company HQ Address Line, Company HQ City, Company HQ Post Code/ZIP, Company HQ County/State, Company HQ Country
These are the company's HQ address, a second company-level address. The Copper Person's address fields are filled from the person-level columns. The HQ address belongs on the Copper Company record.
If you need it. Land the HQ address on the Copper Company record in a separate pass if you need it.
- SIC, ISIC, NAICS
Copper People have no native fields for industry classification codes. They are company-level data.
If you need it. Land the codes on the matched Copper Company record, or add custom Person fields.
- Hiring Title, URL, Location, and Date columns (1 through 5)
Copper People have no native fields for hiring-signal data. These columns capture roles the contact's company is hiring for, a real buying signal, but Copper has no standard place for them.
If you need it. Add custom Person fields if you track hiring activity as a buying signal.
- Job Change - Previous Company, Previous Title, New Company, New Title, Date
Copper People have no native fields for job-change data. A recent job change is a useful champion signal, Copper just has no standard place for it.
If you need it. Add custom Person fields if you track job changes.
- Location Move - From Country, From State, To Country, To State, Date
Copper People have no native fields for location-move data. The signal is useful for territory planning, Copper just has no standard place for it.
If you need it. Add custom Person fields if you use them for territory planning.
Formatting and cleanup
Cognism 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 Mobile, then Direct, then Office, then HQ
- 5.Maps the person-level City, State, and Country to the Copper Person's address fields
- 6.Title-cases name fields, including Cognism's ALL-CAPS job titles
- 7.Normalizes country names to a standard form
Or skip the manual work
Operelio runs this cleanup and mapping for you. Upload your Cognism export and download a clean, import-ready file for Copper.
Cognism to Copper FAQ
How do I export from Cognism?
In Cognism Prospector, build your search, save the contacts to a list, then click Download CSV from the list view. For larger lists Cognism emails you the file when it's ready. 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 Cognism columns with a space so each Person record displays correctly.
How does the template handle Cognism's four phone columns?
Cognism ships Mobile, Direct, Office, and HQ. Copper People have one Phone Number field, so the template fills it with the first available number, checking Mobile first, then Direct, then Office, then HQ. Cognism's Diamond-verified mobiles come through in the Mobile column, so they win when present. All numbers are standardized to international format before import.
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 aren't Seniority and the other Cognism signals mapped?
Copper People have no standard fields for Seniority, Department, Technologies, Email Quality, and similar Cognism signals. The data is real and useful, Copper just has no native place for it. Those columns are listed in the Columns we don't use section. If you want them in Copper, add a custom Person field and map the column to it by hand.
Where do company-level fields like Industry and Revenue go?
They belong on the Copper Company record in Copper's data model, not the Person. After import, enrich the matched Company using Cognism's company data, or run a separate Cognism to Copper Companies pass.
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.
Which address does the template use?
Copper People have address fields, and this template fills them from Cognism's person-level Country, City, and State columns. Those describe where the contact actually is. Cognism also ships two company-level addresses (the registered office and the HQ); both are listed in the Columns we don't use section because they belong on the Copper Company record, not the Person.
