Cognism
HubSpot Contacts15 fieldsHow to import Cognism data into HubSpot
Cognism exports prospect lists as CSV files from Prospector. This template maps the export to HubSpot's standard contact fields: names, email, job title, company, website, LinkedIn profile, industry, and the person's location. Cognism ships four phone columns; Mobile goes to Mobile Phone Number and the main Phone field takes the first available work number from Direct, Office, or HQ. Cognism's Industries column is comma-separated, so the template takes the first industry. Lifecycle Stage and Lead Status are set to Lead and New on every row. Phones, emails, and country names are standardized. The company's registered office address and HQ address are company-level data and belong on the HubSpot Company record, so they are listed in the Columns we don't use section. Data HubSpot has no standard field for is listed in the Columns we don't use section.
Field-by-field mapping
This is the complete column mapping from Cognism to HubSpot. The left column is the header in your CSV export. The right column is the HubSpot field it should map to.
| Cognism column | HubSpot field | |
|---|---|---|
| First Name | First Namefirstname | |
| Last Name | Last Namelastname | |
| Job Title | Job Titlejobtitle | |
| Emailemail TransformLowercased and trimmed | ||
| Mobile | Mobile Phone Numbermobilephone Cognism's Mobile column, including Diamond-verified mobile numbers, lands on HubSpot's dedicated Mobile Phone Number field. TransformStandardized to international format (+1, +44, etc.) | |
| Direct → Office → HQ | Phone Numberphone The main Phone field takes the first available work number: Direct first, then Office, then HQ. Whichever is present wins; the rest are skipped. TransformStandardized to international format (+1, +44, etc.) | |
| "Lead" | Lifecycle Stagelifecyclestage Set on every row. Cognism doesn't ship a lifecycle stage, and a freshly sourced Prospector list is a Lead. Change the value, or remove it, in the column mapper if your process is different. | |
| "New" | Lead Statushs_lead_status Set on every row. Cognism doesn't ship a lead status, and a newly imported prospect starts as New. Change the value, or remove it, in the column mapper if your process is different. | |
| Company Name | Company Namecompany | |
| Website | Website URLwebsite | |
| Personal Linkedin URL | LinkedIn Biohs_linkedinbio Maps to HubSpot's LinkedIn Bio property, the home for a contact's LinkedIn profile. Cognism's separate Company Linkedin URL column is not mapped here. | |
| Industries → first | Industryindustry Cognism ships several industries per row, comma-separated and ordered primary first. HubSpot's Industry field holds one value, so the template takes the first industry. It lands as a single value HubSpot can match to its Industry picklist, instead of a comma-joined blob it can't. To keep the full list, remove the split in the column mapper. | |
| City | Citycity Cognism's person-level City column maps to HubSpot's City field. The company's City and HQ City columns are not mapped here; they belong on the HubSpot Company record. | |
| State | State/Regionstate Cognism's person-level State column maps to HubSpot's State/Region field. The company's State columns are not mapped here. | |
| Country | Country/Regioncountry Cognism's person-level Country column maps to HubSpot's Country/Region field. The company's Country columns are not mapped here. |
Columns we don't use
Your Cognism export includes 44 columns this template doesn't map. Each one below explains why, plus the workaround if you want the data in HubSpot.
- Seniority
HubSpot Contacts has no native seniority field. The data is real and useful, HubSpot just has no standard place for it.
If you need it. Map it by hand to a custom contact property if you want seniority in HubSpot.
- Department
HubSpot Contacts has no native department field. The data is real and useful, HubSpot just has no standard place for it.
If you need it. Map it by hand to a custom contact property if you want department in HubSpot.
- Technologies
HubSpot Contacts has no native field for a company's tech stack. The data is useful for targeting, HubSpot just has no standard place for it.
If you need it. Map it by hand to a custom contact property, or land it on the Company record in a separate pass.
- Email Quality
HubSpot Contacts has no native field for an email confidence flag. The Verified Email or Likely Email signal is useful for filtering, HubSpot just has no standard place for it.
If you need it. Map it by hand to a custom contact property if you want to filter on email quality in HubSpot.
- Education
HubSpot Contacts has no native education field.
If you need it. Map it by hand to a custom contact property if you want it.
- List Name
HubSpot Contacts has no native field for the source list a row came from. HubSpot lists are managed inside HubSpot.
If you need it. Map it by hand to a custom contact property if you want to record which Cognism list a contact came from.
- Diamond Record
HubSpot Contacts has no native field for Cognism's Diamond-verified flag.
If you need it. Map it by hand to a custom contact property if you want to keep the flag.
- Profile ID
HubSpot Contacts has no native field for an external ID. HubSpot matches contacts on email.
If you need it. Map it by hand to a custom contact property 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
HubSpot Contacts has no native field for an alternate company trading name. It is often the same as Company Name anyway.
If you need it. Map it by hand to a custom contact property if you want it.
- Lead Source
Every Cognism row carries the literal value 'Cognism', so there is nothing to map per-row.
If you need it. Set a default Lead Source of 'Cognism' on the HubSpot import itself if you want it recorded.
- Headcount, Financials, Company Type, Company Description, Company Founded Year, Company Linkedin URL
These are company-level data points. HubSpot Contacts has no native fields for them, they belong on the HubSpot Company record.
If you need it. Run a separate Cognism to HubSpot Companies pass to land these on the Company record.
- Company Address Line, Company City, Company Post Code/ZIP, Company County/State, Company Country
These are the company's registered office address. HubSpot's contact address fields are filled from the person-level Country, City, and State columns instead, since those describe where the contact actually is. The company's registered office belongs on the HubSpot Company record.
If you need it. Land the registered office address on the HubSpot Company record in a separate pass. If you would rather use the company's office address on the contact, 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. HubSpot's contact address fields are filled from the person-level columns. The HQ address belongs on the HubSpot Company record.
If you need it. Land the HQ address on the HubSpot Company record in a separate pass if you need it.
- SIC, ISIC, NAICS
HubSpot Contacts has no native fields for industry classification codes. They are company-level data.
If you need it. Run a Cognism to HubSpot Companies pass, or map them by hand to custom properties.
- Hiring Title, URL, Location, and Date columns (1 through 5)
HubSpot Contacts has no native fields for hiring-signal data. These columns capture roles the contact's company is hiring for, a real buying signal, but HubSpot has no standard place for them.
If you need it. Map them by hand to custom contact properties if you track hiring activity as a buying signal.
- Job Change - Previous Company, Previous Title, New Company, New Title, Date
HubSpot Contacts has no native fields for job-change data. A recent job change is a useful champion signal, HubSpot just has no standard place for it.
If you need it. Map them by hand to custom contact properties if you track job changes.
- Location Move - From Country, From State, To Country, To State, Date
HubSpot Contacts has no native fields for location-move data. The signal is useful for territory planning, HubSpot just has no standard place for it.
If you need it. Map them by hand to custom contact properties if you use them for territory planning.
Formatting and cleanup
Cognism exports rarely match the format HubSpot expects. Fix these before you import.
- 1.Lowercases and trims email addresses
- 2.Standardizes phone numbers to international format (+1, +44, etc.)
- 3.Sends Mobile to the Mobile Phone Number field and fills the main Phone field with the first available work number (Direct, then Office, then HQ)
- 4.Takes the first industry from Cognism's comma-separated Industries list, so a single value lands in HubSpot's Industry field
- 5.Maps the person-level City, State, and Country to HubSpot's contact address fields
- 6.Sets Lifecycle Stage to Lead and Lead Status to New on every row, since Cognism's export carries neither
- 7.Title-cases name fields, including Cognism's ALL-CAPS job titles
- 8.Normalizes country names to a standard form
- 9.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 HubSpot.
Cognism to HubSpot 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. Upload that file to Operelio.
How does the template handle Cognism's four phone columns?
Cognism ships Mobile, Direct, Office, and HQ. Mobile goes to HubSpot's dedicated Mobile Phone Number field. The main Phone field takes the first available work number, checking Direct first, then Office, then HQ. Whichever is present wins. All numbers are standardized to international format before import.
Does this template handle Cognism's Diamond Data mobile numbers?
Yes. Diamond-verified mobile numbers come through in the Mobile column and land on HubSpot's Mobile Phone Number field, so the verified mobile sits where your reps expect to find it.
Why aren't Seniority, Department, and the other Cognism signals mapped?
HubSpot Contacts has no standard fields for Seniority, Department, Technologies, Email Quality, and similar Cognism signals. The data is real and useful, HubSpot just has no native place for it. Those columns are listed in the Columns we don't use section. If you want them in HubSpot, create a custom property and map the column to it by hand in the column mapper.
Where does the Industries column go?
Cognism ships several industries per row, comma-separated and ordered primary first. HubSpot's Industry field holds one value, so the template takes the first industry. That lands a single value HubSpot can match to its Industry picklist, instead of a comma-joined string it can't. If you want the full list instead, remove the split on the Industry row in the column mapper.
Why does the template set Lifecycle Stage and Lead Status?
Cognism's export doesn't carry a lifecycle stage or a lead status, but HubSpot has both fields and reps expect them filled. A freshly sourced prospect list is a Lead in the New status, so the template sets Lifecycle Stage to Lead and Lead Status to New on every row. If your process uses different values, change them, or remove them, on those rows in the column mapper before you run the job.
Which address does the template use?
HubSpot Contacts has one address block, and this template fills it 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 HubSpot Company record, not the contact.
Will this create duplicates if a contact already exists in HubSpot?
No. HubSpot uses email as the unique identifier for contacts. Rows whose email matches an existing contact update that record; rows with a new email create a new contact.
Where does the LinkedIn URL go?
Cognism's Personal Linkedin URL maps to HubSpot's LinkedIn Bio property. The separate Company Linkedin URL column is not mapped here, because the company's page belongs on the HubSpot Company record.
