HubSpot Contact–Company Association Import Errors and Fixes

When a HubSpot association import will not proceed, the CSV itself is often only part of the problem. The import also needs the correct object pair, a usable identifier for each object, and an association label that HubSpot can map.

HubSpot error: ASSOCIATION_RECORD_NOT_FOUND

HubSpot writes import error codes in uppercase with underscores in the downloadable error file. ASSOCIATION_RECORD_NOT_FOUND means the import could not find the record identified by the association key, such as Record ID, Email, Company domain name, or another unique property. Correct the missing or invalid identifier, then re-import the affected rows. HubSpot documents this error in its import error reference.

This is a strong reason to verify both sides of the association file before importing: a syntactically valid CSV can still fail when the identifier does not resolve to a real CRM record.

The importer shows the wrong association type

If the mapping screen treats the file as Contact–Contact instead of Contact–Company, go back to the import setup and confirm that Contacts and Companies are the two objects in the import. A company-name column inside a Contact file does not by itself tell HubSpot to create a Company association.

For association work, use the advanced import workflow. The quick contact importer is designed for a simpler contact import and does not expose the same association setup.

The company cannot be identified

HubSpot needs an identifier that resolves the company record. Common choices are Company domain name, Record ID, or a company property configured to require unique values.

Before import, check for duplicates in the identifier column. Two Companies with the same proposed match key make the relationship ambiguous even when every Contact row looks valid.

The Contact cannot be identified

For Contacts, Email and Record ID are common identifiers, and a custom unique property can also be used. Empty identifiers should be fixed before the association file is imported.

Do not use a display name as if it were a guaranteed unique Contact key unless your own data model enforces that rule.

The association is created but is not Primary

Map an association-label column and use the value Primary for the relationship that should be primary. Do not assume that setting a Company name property produces the same result.

If a Contact already has several associated Companies, spot-check the record after import to confirm that the intended association carries the Primary label.

The match looks correct but the source data is ambiguous

The dangerous cases are the ones that look plausible: two Companies called the same thing, several subsidiaries sharing a domain, or a shared customer code used more than once. A CSV builder should surface these cases rather than choosing one record silently.

Nablyx excludes unmatched and ambiguous pairs from the generated association CSV so they remain visible for review. That makes the final file smaller, but it avoids turning uncertainty into a CRM relationship.

A useful troubleshooting order

1. Confirm the import uses Contacts and Companies.
2. Confirm each object has a valid identifier column.
3. Check the company-side key for duplicates.
4. Verify the generated association-label value is Primary.
5. Import a small sample and inspect the resulting associations before running a larger batch.

HubSpot's import troubleshooting documentation covers import-level errors, while its record association documentation explains association behavior.