HubSpot Import CSV: Common Rejection Reasons and Fixes

A CSV can be perfectly valid and still fail in HubSpot.

That is the first thing to understand.

When HubSpot rejects an import, the problem is often not “CSV is broken.” It is usually one of these:

• the headers do not map to HubSpot properties
• required fields for the object are missing
• the import is trying to update records without a valid unique identifier
• the file contains values HubSpot cannot parse for the target property type
• the file violates HubSpot’s import file limits or sheet rules

That is why the fastest way to fix a HubSpot import is to separate:

• file structure
• property mapping
• object-specific validation rules

If you want to inspect the file before it reaches HubSpot, start with the CSV Validator, CSV Header Checker, and CSV Delimiter Checker. If you want the broader cluster, explore the CSV tools hub.

This guide walks through the most common HubSpot CSV import rejection reasons and the quickest way to fix each one.

Why this topic matters

Teams search for this topic when they need to:

• fix a HubSpot import that partially failed
• understand why some rows imported but some fields stayed blank
• repair property mapping or invalid header issues
• troubleshoot date, number, and enumeration parsing errors
• update or create records with the right identifiers
• avoid duplicate or ambiguous owner and company matches
• understand HubSpot file size and technical limits
• create import files that HubSpot accepts consistently

This matters because HubSpot import failures often look worse than they are.

A common pattern is:

• the file uploads successfully
• some records import
• some rows fail
• some properties are silently left blank on affected rows
• the team is unsure whether the issue was file format, field mapping, or record matching

HubSpot’s docs make it clear that many import errors do not reject the whole file. Some rows still import while specific properties fail to populate. citeturn865079view0turn539254view0

That means you need to know which errors are:

• full import blockers
• row blockers
• field-value blockers

Start with HubSpot’s actual technical requirements

Before looking at error messages, it helps to know what HubSpot requires up front.

HubSpot’s import format docs say import files must:

• be .csv, .xlsx, or .xls
• contain only one sheet
• include a header row whose column headers correspond to HubSpot properties
• contain fewer than 1,000 columns
• be UTF-8 encoded if the file includes foreign language characters citeturn539254view0

HubSpot also documents plan-based size and row limits. On free tools, file size is up to 20 MB, while Smart CRM and paid Starter/Professional/Enterprise accounts can import files up to 512 MB. HubSpot also documents daily row and import limits and simultaneous-import limits. citeturn539254view0

These are the first checks to make before debugging deeper property-level errors.

The fastest triage model

A practical triage model for HubSpot CSV failures looks like this:

Layer 1: file-level blockers

Examples:

• invalid file type
• invalid sheet count
• invalid spreadsheet
• file too large or import limit exceeded

Layer 2: schema and mapping blockers

Examples:

• incorrect number of columns
• property definition not found
• missing required property
• invalid association identifier

Layer 3: value-level errors

Examples:

• could not parse date
• could not parse number
• invalid enumeration option
• multiple owners found
• multiple companies with this domain

This model makes troubleshooting much faster because not every error means the same thing operationally.

Common rejection reasons and fixes

1. Incorrect number of columns

HubSpot says Incorrect number of columns means the import file contains at least one column without a header, and the data in columns without headers was not imported. citeturn865079view0

Why it happens

• the header row is shorter than later rows
• there is a stray extra delimiter in the file
• one or more trailing columns have no header
• a manual spreadsheet edit introduced an extra blank column

Fix

• inspect the header row and compare column counts across rows
• make sure every populated column has a header
• remove accidental blank columns
• validate delimiter and quote handling before re-uploading

This error is one reason a header checker is worth running before HubSpot sees the file.

2. Property definition not found

HubSpot says Property definition not found means the file contains a column header that does not match a HubSpot property, so the data in that column was not imported. HubSpot’s fix is to map the column to an existing property, create a new property, or skip importing the unmatched column. citeturn865079view0

Why it happens

• the header does not exactly match a property you intended
• a vendor renamed a field
• the property does not exist yet in HubSpot
• the mapping step was skipped or done incorrectly

Fix

• confirm whether the property already exists in HubSpot
• create the property before import if needed
• map the column explicitly during import
• normalize inconsistent source headers before upload

This is one of the most common “the file is fine but HubSpot still rejected data” cases.

3. Missing required property

HubSpot says Missing required property means the file is missing a value for a required property, and that row was not imported. HubSpot’s format docs also list the required fields for object creation, such as:

• Contacts: at least one of First name, Last name, or Email
• Companies: at least one of Name or Company domain name
• Deals: Deal name, Pipeline, and Deal stage for new deals
• Tickets: Ticket name, Pipeline, and Ticket status for new tickets citeturn865079view0turn539254view0

Why it happens

• a required field column is missing entirely
• the column exists but the affected row is blank
• the import mode is “create” or “create and update” and required create fields are absent

Fix

• verify the object-specific required fields for your import mode
• fill missing values in the file
• if you only want to update existing records, ensure you selected the correct import behavior and included a valid identifier

4. Invalid record ID or unknown bad request

HubSpot says Invalid record ID means a column was mapped to Record ID but the values do not match existing HubSpot record IDs. HubSpot also documents Unknown bad request as another case where an invalid Record ID does not match any existing record. In both cases, the import does not update the intended record. citeturn865079view0

Why it happens

• you exported or copied the wrong IDs
• the file mixes IDs from another environment or portal
• the column was mapped to Record ID when it should have used Email, Company domain, or another unique identifier
• the import should have been create-only, not update

Fix

• export current HubSpot records and verify the correct IDs
• switch to another valid unique identifier if that is safer
• unmap Record ID if you are not updating existing records
• retry with the corrected identifier column

5. Could not parse date

HubSpot says Could not parse date means the file contains a date value that does not match the format selected during import. The affected records may still import, but the date property remains blank. citeturn865079view0

HubSpot’s format docs also explain accepted date and datetime formats, including accepted separators, month formats, and how timestamps can be provided. citeturn539254view0

Why it happens

• file dates do not match the selected import format
• timestamps are missing or malformed
• spreadsheet software changed the display but not the underlying exported text
• locale-driven date formats were mixed in one file

Fix

• make all date values consistent
• choose the correct date format during import
• export dates as plain text values if spreadsheets are reformatting them
• test one or two rows before re-running a large import

6. Could not parse number / invalid number size

HubSpot says Could not parse number means the file contains non-numeric characters for a number property, and Invalid number size means the numerical value is too small or too big. In both cases, the record may still import while the number property remains blank. citeturn865079view0

HubSpot’s formatting docs also specify number rules for currencies, percentages, and phone numbers. citeturn539254view0

Why it happens

• currency symbols or thousands separators are inconsistent
• values include stray text
• percentages are formatted differently than HubSpot expects
• numbers exceed the accepted size range

Fix

• strip non-numeric noise where needed
• align with HubSpot’s property-specific number rules
• keep one numeric style across the whole file
• validate suspicious large values before re-import

7. Invalid enumeration option

HubSpot says Invalid enumeration option means a value in the file does not match an existing option in an enumeration property such as dropdown, multi-select, radio select, or checkbox. The row may still import, but the property is left blank. For default properties, HubSpot says values must match either the internal value or the English label. citeturn865079view0turn539254view0

Why it happens

• the source value uses a label that does not exist in HubSpot
• the value is misspelled
• custom options were never created in HubSpot
• a locale-specific label was used where HubSpot expects English for default properties

Fix

• compare file values to the HubSpot property options directly
• normalize or map the values before import
• add the missing option to the property if appropriate
• prefer internal values when your workflow supports them

8. Multiple owners found / could not find owner

HubSpot says Could not find owner means the owner value does not match an active user in the account. Multiple owners found means the owner value matched more than one user, which often happens when the file uses a person’s name instead of a unique email. HubSpot recommends using the owner’s email or internal owner value. citeturn865079view0turn539254view0

Why it happens

• the file uses names instead of unique emails
• the owner is inactive
• duplicate names exist in the account
• the wrong owner field was mapped

Fix

• use owner email addresses rather than names
• verify the user is active in the account
• avoid ambiguous owner-name strings
• re-import only the affected rows if needed

9. Multiple companies with this domain

HubSpot says Multiple companies with this domain means the imported company domain matches multiple companies already in the account, so HubSpot cannot decide which company to update. citeturn865079view0

Why it happens

• duplicate company records already exist in HubSpot
• the chosen identifier is not actually unique anymore

Fix

• search the domain in HubSpot
• merge or delete duplicate companies
• choose a more reliable unique identifier for update logic if necessary

This is a good reminder that CSV imports often expose pre-existing CRM hygiene problems.

10. Invalid file type / invalid sheet count / invalid spreadsheet

HubSpot documents:

• Invalid file type for unsupported file types
• Invalid sheet count when the file contains more than one sheet
• Invalid spreadsheet when the spreadsheet file itself is not valid citeturn865079view0turn539254view0

Why it happens

• wrong file extension or corrupted file
• workbook has multiple sheets
• spreadsheet export is malformed
• a user saved the file in the wrong format

Fix

• export a fresh .csv, .xls, or .xlsx
• ensure only one sheet is present
• re-save the file cleanly before import

11. Row data too large

HubSpot says Row data too large means a cell or row contains more than 1 MB of data, so that row is not imported. citeturn865079view0

Why it happens

• large pasted notes or HTML blobs
• oversized text fields from upstream systems
• repeated content or malformed exports

Fix

• trim or split the oversized field
• keep very large blobs out of standard CRM imports
• validate long text columns before upload

12. Limit exceeded

HubSpot documents a Limit exceeded error category, and its import format page also lists account-level file, row, and daily import limits that vary by subscription. citeturn865079view0turn539254view0

Why it happens

• too many rows for the day
• too many imports started
• file too large for the subscription tier
• object storage limits or account limits are reached

Fix

• compare the job to the current account limits
• break large imports into smaller batches when appropriate
• stagger import timing
• confirm whether the subscription tier is the real blocker

The safest review path before re-importing

A strong fix workflow usually looks like this:

1. preserve the original file
2. confirm the file still meets HubSpot’s technical requirements
3. inspect the header row and column counts
4. verify object-specific required properties
5. verify the identifier strategy for updates vs creates
6. normalize dates, numbers, and enumeration values
7. retry a small sample import if the file is large
8. only then rerun the full import

This is faster than repeatedly guessing inside the import tool.

A few HubSpot-specific rules worth remembering

HubSpot’s format docs include a few details that often matter in troubleshooting:

• blank cells are ignored, so blank imports do not clear existing values
• multiple checkbox values are separated by semicolons with no spaces
• additional emails and domains also use semicolon-separated values
• owners can be assigned by name, email, or internal value, but email is safer when names are not unique
• if you are updating existing records, a valid unique identifier must be included citeturn539254view0turn218061search1

These are small rules, but they explain a lot of partial-import confusion.

Common anti-patterns

Fixing the file only in Excel without understanding the error

That often introduces new date, number, or delimiter issues.

Assuming the whole import failed

Some HubSpot errors only drop field values or specific rows.

Using names instead of stable identifiers

This is especially risky for owners and record updates.

Treating unmatched headers as harmless

Unmatched columns are often silently skipped, which can hide lost data.

Ignoring the object’s required creation fields

Contacts, companies, deals, and tickets do not all have the same required-property rules. citeturn539254view0

Which Elysiate tools fit this article best?

For this topic, the most natural supporting tools are:

• Free QR Code Generator
• SVG QR Code Generator
• CSV Validator
• CSV Format Checker
• CSV Delimiter Checker
• CSV Header Checker

These fit naturally because HubSpot import failures often start at the file-shape and header-mapping layer before they become CRM-specific property errors.

FAQ

What is the most common reason HubSpot rejects a CSV import?

A common cause is a mismatch between your file headers or values and HubSpot’s expected properties and field formats, even when the CSV itself is structurally valid. HubSpot explicitly requires a header row that corresponds to HubSpot properties. citeturn539254view0turn865079view0

Can HubSpot import a file that is valid CSV but still has bad property values?

Yes. HubSpot may import the row but leave some properties blank when specific values fail parsing or validation, such as dates, numbers, or enumeration options. citeturn865079view0

Why does HubSpot say Property definition not found?

It means a column header in your file does not match an existing HubSpot property and was not correctly mapped during import. citeturn865079view0

What should I check first before re-uploading a rejected HubSpot file?

Check the file type, header row, required properties, mapping to HubSpot properties, and whether dates, numbers, owners, and identifiers match HubSpot’s formatting and uniqueness rules. citeturn539254view0turn865079view0

Why do some rows import while others still fail?

Because many HubSpot import errors are row-level or field-level rather than whole-file blockers. Some records import, but affected properties are left blank or affected rows are skipped. citeturn865079view0

What is the safest identifier for updating existing records?

It depends on the object, but HubSpot’s docs make clear that updating existing records requires a valid unique identifier such as Record ID, Email, or Company domain name, depending on the object and workflow. citeturn539254view0turn865079view0turn218061search1

Final takeaway

HubSpot CSV imports fail for reasons that are usually understandable once you stop treating the issue as “bad CSV” and start treating it as a three-layer problem:

• file requirements
• property mapping
• object-specific value rules

The safest baseline is:

• keep the original file
• confirm HubSpot file requirements first
• verify headers and required properties
• use valid unique identifiers for updates
• normalize dates, numbers, owners, and enumeration values
• re-import only after you know which layer failed

That turns HubSpot import troubleshooting from guesswork into a repeatable fix path.