How to Fix Common HubSpot Import Errors

When you import data into HubSpot, small formatting mistakes or missing values can create confusing errors and partial uploads. This guide explains how to read those messages, correct your files, and complete a clean import without breaking your CRM data.

All tips below are based on HubSpot’s own import error rules so you can quickly understand what went wrong and how to fix it before trying again.

Before You Start: Understand HubSpot Import Basics

To reduce errors, prepare your data and file format before running an import.

• Use CSV, XLS, or XLSX formats only.
• Keep one header row with clear column names.
• Confirm property types in your CRM match what you are importing.
• Decide whether you are creating new records, updating existing ones, or both.

If you need broader CRM or implementation help around HubSpot, you can also work with a consulting partner such as Consultevo.

How HubSpot Shows Import Errors

After you run an import, HubSpot will show a summary with:

• Total rows processed
• Number of rows successfully imported
• Number of rows with errors

You can download a detailed error file, which contains each failed row plus a description of why the import did not succeed. Always start by reviewing this file, since the line number and error type tell you exactly where to look in your original spreadsheet.

General Steps to Fix HubSpot Import Errors

1. Run your import and wait for it to finish processing.
2. Download the error file from the import results screen.
3. Sort or filter the error file by the error column.
4. Open your original file and correct the problematic rows.
5. Save a new, clean version of the file.
6. Re-import only the corrected data.

Most errors are repeating patterns. Once you identify the cause in a few rows, you can often fix the entire spreadsheet with a single change.

HubSpot Import Errors Related to File Format

Many common issues come from the structure of the file instead of the data values themselves.

Incorrect Column Headers for HubSpot Properties

If a header does not match a valid property or mapped field, HubSpot may fail to import the column or return an error.

To fix this:

• Review property names in your CRM settings.
• Match header names exactly, including spelling and spacing.
• During the import mapping step, manually map unmatched columns.

Missing Required Columns

Some record types need specific properties for HubSpot to create or associate them correctly. For example:

• Contacts often need an email address or another unique property.
• Companies usually require a company domain name if you want automatic associations.

Add the required columns to your file, fill in the data, and run the import again.

Wrong File Encoding or Delimiters

If your file uses non-standard delimiters or encodings, some characters may fail. To reduce errors:

• Save your CSV as UTF-8.
• Use commas as separators unless your locale requires otherwise.
• Remove stray line breaks inside cells where possible.

HubSpot Import Errors for Required and Unique Properties

Missing Values for Required Properties

When a column is marked as required in your CRM, HubSpot will not accept blank cells for that property.

To correct this:

• Filter rows that show the error in your error file.
• Fill in the missing values in the original spreadsheet.
• If data is truly unavailable, either make the property optional in settings or remove those rows from the import.

Duplicate Values in Unique Properties

Unique properties, such as email or company domain name, must not contain duplicates. If two rows share the same unique value, HubSpot may fail the row or only update one record.

Steps to fix:

1. In your spreadsheet, use filters or conditional formatting to highlight duplicates.
2. Decide which row is correct or should be kept.
3. Either merge the details into one row or remove extra duplicates.
4. Re-import after cleaning up the conflicts.

HubSpot Errors with Property Types and Values

Invalid Options for Dropdowns and Multiple-Choice Fields

For properties like dropdown select, multiple checkboxes, and radio selects, HubSpot expects values that match existing options exactly.

If the value in your file does not match an internal option, you may see an error such as an invalid option or failed property update.

To resolve this:

• Export a list of options from your property settings.
• Confirm each cell matches one of those options (case-sensitive in many cases).
• Update the spreadsheet to align labels or add new options to the property in your CRM.

Wrong Data Format for Dates, Numbers, and Booleans

HubSpot has specific expectations for structured data.

• Dates: Often need a standard date format or a numeric timestamp, depending on the property.
• Numbers: Must not include currency symbols or extra text.
• Booleans: Typically require values such as “true/false” or “yes/no” based on property configuration.

Adjust your file so each value matches the expected pattern before re-importing.

HubSpot Association and ID-Based Import Errors

Missing or Invalid Record IDs

When updating existing records or importing associations, you might use record IDs. If an ID does not exist in your CRM, or if it is formatted incorrectly, HubSpot cannot map that row.

Fix this by:

• Exporting the relevant records from your CRM to get accurate IDs.
• Replacing incorrect IDs in your file with valid ones.
• Ensuring the ID column is mapped correctly at import time.

Association Errors Between Objects

When you import associations, such as contacts to companies or deals to companies, the association keys must match real records.

To reduce these errors:

• Use reliable identifiers such as email, company domain, or object ID.
• Verify that associated records already exist if you are only importing the association.
• Or, import parent objects first, then import child objects with association columns.

HubSpot Import Limits and Partial Failures

Some issues are related to account limits rather than formatting. Large files, rate limits, or exceeding property counts may create partial imports or rejected rows.

In those situations:

• Split very large files into smaller batches.
• Remove unused columns or obsolete properties where possible.
• Check your subscription tier to confirm record and property limits.

Advanced Troubleshooting and HubSpot Resources

If errors persist after you have cleaned up your file, compare your situation with the official documentation. HubSpot provides a detailed reference of import error types and their meanings, which you can review at this import error troubleshooting page.

You can also:

• Test a small sample file (10–20 rows) to confirm your mapping and formats.
• Use separate imports for different object types or workflows.
• Document a standard template so future imports follow the same rules.

Summary: Clean Imports in HubSpot

Most import problems come down to missing required values, wrong property formats, or value options that do not exist. By validating your headers, correcting property data types, and carefully reviewing the error file, you can complete clean, repeatable imports into HubSpot and keep your CRM accurate over time.