← Back to guides

HubSpot import guide

HubSpot CSV column format errors

Some import failures are not bad field values. They are structural CSV problems: duplicate header names, empty header cells, or rows that have more cells than the header row.

What the error means

A CSV column format problem means the file structure is ambiguous before HubSpot even evaluates individual contact values. HubSpot and local tools need a stable header row to know which property each cell belongs to.

Common structural problems include duplicate header columns, blank header names, and data rows with more cells than the header row defines.

Why HubSpot rejects it

HubSpot maps CSV columns to properties by header name. If a header is blank or repeated, the mapping is ambiguous. If a row has more cells than the header row, some values have no column name and may be dropped, shifted, or misread by import tooling.

  • Duplicate headers make it unclear which column should map to the HubSpot property.
  • Blank headers create columns with no property name to map.
  • Rows wider than the header row contain extra values that are not represented in the cleaned working copy.

How to fix it manually

  1. Open the source CSV or spreadsheet that generated it.
  2. Rename duplicate headers so every intended column has a unique, meaningful name.
  3. Add real header names for blank header cells, or delete unused blank columns.
  4. Find rows with extra delimiters or accidental split cells and repair them in the source file.
  5. Export a fresh CSV and reload it before making per-cell cleanup edits.

How ReadyCSV catches it locally before import

ReadyCSV flags duplicate headers as structural_duplicate_header, blank headers as structural_blank_header, and rows with more cells than the header row as structural_extra_cells. These are critical structural blockers.

ReadyCSV treats these as source-file repairs, not per-cell edits. Extra values are not represented safely in the cleaned working copy, so the source CSV should be fixed and reloaded before export.

This guide is about CSV structure. It does not claim ReadyCSV can confirm every encoding or character-set problem before HubSpot import.

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 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é.

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