← Back to guides

HubSpot import guide

HubSpot import unmapped / unrecognized columns

HubSpot imports depend on mapping CSV headers to properties. Unrecognized columns are not always fatal, but they should be reviewed before you commit the import.

What the error means

An unmapped or unrecognized column means the CSV header did not clearly match a HubSpot contact property in the destination account or import profile. HubSpot may ask you to map it manually, create a custom property, or skip the column.

ReadyCSV can review headers locally against its HubSpot Contacts preset, but it does not connect to HubSpot or create account-specific properties for you.

Why column mapping fails

Mapping problems usually come from source-system labels, account-specific custom fields, or columns that are useful internally but do not have a direct HubSpot property. A friendly spreadsheet header can still require a decision in HubSpot's import mapping screen.

  • Unknown headers may not map to any built-in HubSpot contact property.
  • Recognized aliases may still need review when multiple source columns point at the same destination field.
  • Full Name often needs human splitting into First Name and Last Name.
  • Custom account properties cannot be confirmed locally without a HubSpot connection.

How to fix it manually

  1. Decide which columns must import and which columns can be skipped.
  2. Rename obvious aliases to the HubSpot property names you want before export.
  3. Split Full Name into First Name and Last Name when the destination import expects separate fields.
  4. Create or confirm custom HubSpot properties before mapping account-specific columns.
  5. Review HubSpot's import mapping screen carefully before committing the import.

How ReadyCSV flags mapping risks locally

ReadyCSV flags unknown headers as unmapped_column info findings. Those columns are kept in the export, but the finding tells you they may not import correctly unless you map or review them in HubSpot.

ReadyCSV also emits hubspot_manual_mapping_review warnings for columns that may require manual mapping or property creation. For Full Name, ReadyCSV can emit a mapping_suggestion info finding that says the column can be split into First Name and Last Name.

The import profile can list recognized header aliases and local rename actions, but ReadyCSV does not map the columns into HubSpot itself. Use the HubSpot CSV formatting checklist with the CSV column format guide before upload.

Related HubSpot import guides

How to format a CSV for HubSpot import

Use an end-to-end HubSpot contact CSV checklist before uploading: identity, headers, emails, dates, phones, owners, encoding, and enums.

HubSpot import date format errors

Fix HubSpot date columns that use Excel serials, written-out dates, dots, or unsupported formats.

HubSpot invalid email import error

Understand INVALID_EMAIL, INVALID_DOMAIN, duplicate emails, and additional email address imports.

HubSpot lifecycle stage import error

Check lifecycle stage and lead status values before HubSpot rejects an import row.

HubSpot import missing required fields

Fix contact rows missing First name, Last name, and Email before a HubSpot import.

HubSpot contact owner import error

Review Contact owner values that need an active HubSpot user email or internal owner value.

HubSpot CSV column format errors

Fix duplicate headers, blank headers, and rows with extra cells before importing a CSV.

HubSpot phone number format import

Review HubSpot phone number format import risks and use E.164-style values before uploading contacts.

HubSpot import special characters broken / UTF-8 encoding CSV

Fix CSV encoding workflows when HubSpot import special characters look broken, such as José instead of José.

HubSpot import duplicate contacts / duplicate email

Review duplicate emails, duplicate rows, and blank-email dedupe risk before importing HubSpot contacts.

HubSpot website URL import format

Clean Website URL values, whitespace, and clearly invalid website text before importing contacts.

View all guides

Check your CSV before importing

ReadyCSV preflights HubSpot contact CSVs locally in your browser. Your CSV contents stay on your device: no upload, no account, no AI calls, and no license server call for local checks.

It is still your responsibility to review every finding, cleaned export, Issue Report, and HubSpot import setting before importing. ReadyCSV cannot guarantee that HubSpot will accept every row.

Open ReadyCSV local preflight