If an export to HubSpot fails, Cognism displays the error returned by HubSpot.

This article explains common HubSpot export errors, what they mean, and how to resolve them.

Before You Begin

Before troubleshooting, check that:

The HubSpot integration is connected.
You are logged in to the correct HubSpot account.
Your HubSpot user has the required permissions.
Field mappings have been configured correctly.
The record still exists in HubSpot if you are exporting from a saved list.

Connection and Authentication Errors

Authorization failed because you don’t have permission to authorize the required scopes

What it means

HubSpot has blocked the connection because the user does not have permission to authorise the Cognism app.

Resolution

Ask your HubSpot administrator to temporarily grant the user Super Admin permissions.

After the integration has been connected successfully, Super Admin permissions can usually be removed.

Error 400 referencing integration or token

What it means

The HubSpot connection may have dropped or the authentication token is no longer valid.

Resolution

Go to Settings > Integrations > HubSpot.
Click Log Out.
Click Log In and reconnect your HubSpot account.
Retry the export.
Important: Do not click Remove if you are an admin user unless you want to remove the integration configuration. Removing the integration may delete field mappings and settings.

BAD_HUB: missing or unknown hub id

What it means

The HubSpot account you are trying to connect does not match the expected HubSpot account.

Resolution

Log out of all HubSpot accounts in your browser.
Log back into the correct HubSpot account.
Return to Cognism.
Reconnect the HubSpot integration.

Field Mapping and Property Errors

Property does not exist

What it means

A mapped HubSpot property no longer exists or cannot be accessed.

This usually happens when a property that was previously mapped in Cognism has been deleted in HubSpot.

Resolution

Read the full error message to identify the affected property.
Go to Settings > Integrations > HubSpot in Cognism.
Open the field mappings.
Check both Contact and Company mappings.
Remove or update the affected field mapping.
Save the changes and retry the export.

INVALID_OPTION - Property values were not valid

What it means

The value Cognism is exporting is not accepted by the mapped HubSpot property.

This commonly happens when a Cognism field, such as Country, is mapped to a HubSpot dropdown or picklist field but the values do not match the allowed HubSpot options.

Resolution

Review the mapped HubSpot property and ensure the exported values match the allowed options.

If advanced value mapping is available, align the Cognism values with the HubSpot property values.

INVALID_DOMAIN - Property values were not valid

What it means

HubSpot has rejected the company domain because the value is not valid.

Example

A value such as mcdonald’http://s.co.uk may be rejected as an invalid domain.

Resolution

Review the company domain value in the export and correct the invalid domain before exporting again.

INVALID_EMAIL - Property values were not valid

What it means

HubSpot has rejected the email address because it is not valid.

Resolution

Check the contact’s email address. If the email address is invalid, the record cannot be exported until the value is corrected or removed.

Duplicate and Existing Record Errors

CONFLICT - Contact already exists

What it means

HubSpot has identified that the contact already exists.

This may happen when the existing contact was not matched before Cognism attempted to create a new record.

Resolution

Search for the contact in HubSpot and verify whether the record already exists.

If the contact exists, review your HubSpot update rules and matching behaviour before retrying the export.

Record and Association Errors

Resource not found

What it means

The HubSpot object Cognism is trying to update or associate no longer exists, or the user does not have permission to access it.

This can happen when exporting from a saved list if the related HubSpot record has been deleted or moved.

Resolution

If exporting from a list:

Find the contact again in Search.
Save the record to a new list.
Export the record again from the new list.

If the issue continues, check HubSpot permissions and confirm the record still exists.

INVALID_OBJECT_IDS - One or more associations are invalid

What it means

HubSpot has rejected an association because one of the related object IDs is invalid.

This can happen when Cognism attempts to associate a contact with a company or another HubSpot object that no longer exists or cannot be accessed.

Resolution

Check whether the related contact or company still exists in HubSpot.

If exporting from a saved list, save the record to a new list and export again.

LEAD with ID was not found

What it means

A record referenced during export can no longer be found.

This usually happens when exporting from a list and the underlying HubSpot record has been deleted or moved.

Resolution

Find the same record again from Search.
Save it to a new list.
Export it to HubSpot again.

The customer may need to recreate or resave the list before retrying the export.

Ownership Errors and Questions

Changing owner of contact or company

What it means

Ownership cannot be mapped or controlled directly from Cognism.

How ownership works

For new contacts or companies, HubSpot sets the owner as the user who exported the record from Cognism.

For existing contacts or companies, exporting or enriching from Cognism does not change the existing HubSpot owner.

The original HubSpot owner remains assigned.

I want Contacts to have the same owner as Companies in HubSpot

Resolution

This behaviour must be configured in HubSpot.

Review the Contact object setup and ownership automation in HubSpot.

Cognism does not control this ownership rule during export.

Company Export Issues

Company data is not exported or company fields are blank

What it means

Cognism may be configured not to create or export associated companies.

Resolution

Ask a Cognism Admin to check the HubSpot export setup.

If the export rule is set to Export contacts without associated companies, company records will not be created or updated in HubSpot when exporting from Cognism.

To export company data, update the HubSpot export settings so associated companies are included.

HubSpot System Errors

502 Bad Gateway or Bad Gateway from Cloudflare

What it means

HubSpot or Cloudflare returned a temporary error.

This is usually outside Cognism’s control.

Resolution

Retry the export later.

If the issue persists, contact Cognism Support with the full error message and affected record details.

INTERNAL_ERROR - There was an error processing the request

What it means

HubSpot returned an internal processing error.

This is usually outside Cognism’s control.

Resolution

Retry the export.

If the issue continues, contact Cognism Support and provide the full error message, contact email, company name, and export location.

Required Email Property Behaviour

Email is required in HubSpot but Cognism still sends records without email

What it means

HubSpot required properties set in the HubSpot UI are not always enforced through the HubSpot API.

This means a property may be required when manually creating a contact in HubSpot or importing via CSV, but not enforced when records are created through an integration.

Resolution

Use HubSpot workflows to introduce validation for the email property if your organisation requires every contact to have an email address.

Still Having Problems?

If the issue cannot be resolved, contact Cognism Support and provide:

The full HubSpot error message.
The contact email address.
The company name.
Whether the export was from Search, a List, a Contact Profile, or the Chrome Extension.
Whether the issue affects one record or multiple records.
A screenshot of the error, if available.