Cognism
Pipedrive Contacts5 fieldsHow to import Cognism data into Pipedrive
Cognism exports prospect lists as CSV files from Prospector. This template maps the export to Pipedrive's contact fields: it combines First Name and Last Name into Pipedrive's single Name field, matches the company to an organization, and maps email and job title. Cognism ships four phone columns; Pipedrive contacts have one Phone 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. Pipedrive's contact model is leaner than HubSpot or Salesforce, so most Cognism columns, including all the company firmographics and the address, belong on the Pipedrive organization rather than the contact. The Columns we don't use section covers each one.
Field-by-field mapping
This is the complete column mapping from Cognism to Pipedrive. The left column is the header in your CSV export. The right column is the Pipedrive field it should map to.
| Cognism column | Pipedrive field | |
|---|---|---|
| First Name + Last Name | Name*name Pipedrive uses a single Name field, so the template combines the two columns with a space between them. TransformFirst Name and Last Name combined with a space | |
| Emailemail TransformLowercased and trimmed | ||
| Job Title | Job Titlejob_title | |
| Company Name | Organizationorg_name Matched to an existing Pipedrive organization, or a new one is created. | |
| Mobile → Direct → Office → HQ | Phonephone Pipedrive contacts have one Phone 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.) |
Required by Pipedrive.
Columns we don't use
Your Cognism export includes 50 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in Pipedrive.
- Seniority
Pipedrive contacts have no native seniority field. The data is real and useful, Pipedrive just has no standard place for it.
If you need it. Add a custom contact field in Pipedrive for Seniority, then map it by hand in the column mapper.
- Department
Pipedrive contacts have no native department field. The data is real and useful, Pipedrive just has no standard place for it.
If you need it. Add a custom contact field in Pipedrive for Department, then map it by hand.
- Technologies
Pipedrive contacts have no native field for a company's tech stack. The data is useful for targeting, Pipedrive just has no standard place for it.
If you need it. Add a custom field on the Pipedrive organization, then update by organization name after import.
- Email Quality
Pipedrive contacts have no native field for an email confidence flag. The Verified Email or Likely Email signal is useful for filtering, Pipedrive just has no standard place for it.
If you need it. Map it by hand to a custom contact field if you want to filter on email quality in Pipedrive.
- Education
Pipedrive contacts have no native education field.
If you need it. Map it by hand to a custom contact field if you want it.
- List Name
Pipedrive contacts have no native field for the source list a row came from.
If you need it. Map it by hand to a custom contact field if you want to record which Cognism list a contact came from.
- Diamond Record
Pipedrive contacts have no native field for Cognism's Diamond-verified flag.
If you need it. Map it by hand to a custom contact field if you want to keep the flag.
- Profile ID
Pipedrive contacts have no native field for an external ID. Pipedrive matches contacts on email.
If you need it. Map it by hand to a custom contact field 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
Pipedrive contacts have no native field for an alternate company trading name. It belongs on the organization anyway, and is often the same as Company Name.
If you need it. Add a custom field on the Pipedrive organization if you want it.
- Lead Source
Every Cognism row carries the literal value 'Cognism'. Pipedrive contacts have no native lead source field.
If you need it. Add a custom contact field in Pipedrive and set it by hand if you want the source recorded, or use Pipedrive's labels.
- Personal Linkedin URL
Pipedrive contacts have no native LinkedIn field.
If you need it. Add a custom Link field on the Pipedrive contact called LinkedIn, then map this column to it by hand.
- Country, City, State (person location)
Pipedrive contacts have no native address fields. Addresses live on the Pipedrive organization in Pipedrive's data model.
If you need it. Add custom contact fields if you need the address on the contact, or move the data to the matched organization's address after import.
- Website, Headcount, Industries, Financials, Company Type, Company Description, Company Founded Year, Company Linkedin URL
These are company-level data points. Pipedrive contacts have no native fields for them, they belong on the Pipedrive organization.
If you need it. Enrich the matched Pipedrive organization after import using Cognism's company data, or add custom organization fields and update by organization name.
- Company Address Line, Company City, Company Post Code/ZIP, Company County/State, Company Country
The company registered office address belongs on the Pipedrive organization, not the contact. Pipedrive contacts have no address fields.
If you need it. Land the company address on the matched Pipedrive organization's Address field after import.
- Company HQ Address Line, Company HQ City, Company HQ Post Code/ZIP, Company HQ County/State, Company HQ Country
The company HQ address also belongs on the Pipedrive organization, not the contact.
If you need it. Land the HQ address on the Pipedrive organization in a separate pass if you need it.
- SIC, ISIC, NAICS
Pipedrive contacts have no native fields for industry classification codes. They are company-level data.
If you need it. Add custom fields on the Pipedrive organization, or map them by hand.
- Hiring Title, URL, Location, and Date columns (1 through 5)
Pipedrive contacts have no native fields for hiring-signal data. These columns capture roles the contact's company is hiring for, a real buying signal, but Pipedrive has no standard place for them.
If you need it. Map them by hand to custom contact fields if you track hiring activity as a buying signal.
- Job Change - Previous Company, Previous Title, New Company, New Title, Date
Pipedrive contacts have no native fields for job-change data. A recent job change is a useful champion signal, Pipedrive just has no standard place for it.
If you need it. Map them by hand to custom contact fields if you track job changes.
- Location Move - From Country, From State, To Country, To State, Date
Pipedrive contacts have no native fields for location-move data. The signal is useful for territory planning, Pipedrive just has no standard place for it.
If you need it. Map them by hand to custom contact fields if you use them for territory planning.
Formatting and cleanup
Cognism exports rarely match the format Pipedrive expects. Fix these before you import.
- 1.Combines First Name and Last Name into Pipedrive'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 field with the first available number, checking Mobile, then Direct, then Office, then HQ
- 5.Matches Company Name to an existing Pipedrive organization, or creates a new one
- 6.Title-cases name fields, including Cognism's ALL-CAPS job titles
- 7.Trims whitespace and removes blank rows
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 Pipedrive.
Cognism to Pipedrive FAQ
How do I export contacts from Cognism?
In Cognism Prospector, build your search, save the contacts to a list, then open the list and click Download CSV. Upload that CSV to Operelio.
Why does this template combine First Name and Last Name?
Pipedrive contacts use a single Name field, not separate first and last name fields. The template combines the two columns with a space so the contact records look right in Pipedrive.
How does the template handle Cognism's four phone columns?
Cognism ships Mobile, Direct, Office, and HQ. Pipedrive contacts have one Phone 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 if the contact's company doesn't exist in Pipedrive?
The template creates a new organization in Pipedrive and links the contact to it. If the company already exists, the contact links to the existing organization.
Why are most Cognism columns not mapped?
Pipedrive contacts use a leaner field set than HubSpot or Salesforce. Seniority, Department, LinkedIn, the address, industry, and the company firmographics have no native Pipedrive contact field, and most of that data belongs on the Pipedrive organization rather than the contact. The Columns we don't use section above explains the workaround for each one.
Will this create duplicate contacts?
Pipedrive's import dedupes on Name plus one of email, phone, or organization. A Cognism row matches an existing Pipedrive contact when the name and one of email, phone, or organization align. Rows missing an email after reveal can still match on Name plus phone or organization.
Which address does the template use?
Pipedrive contacts have one address block on the organization, not the contact, and this template doesn't fill it. Cognism's person-level Country, City, and State columns describe where the contact actually is and would land on the contact if Pipedrive had address fields there. Both company-level addresses (the registered office and the HQ) are listed in the Columns we don't use section because they belong on the matched Pipedrive organization, not the contact.
