HubSpot Company Matching: Domain vs Name vs Record ID

Before you create a HubSpot Contact–Company association CSV, you need a rule that decides which Company belongs to each Contact. Domain, company name, and record/custom IDs solve different data problems, and they do not have the same failure modes.

Email domain to Company domain name

This is useful when Contacts mostly use business email addresses and the Company export contains a clean Company domain name.

For example, alex@example.com can be compared with example.com after trimming whitespace and normalizing case. The match should still be treated as unresolved if more than one Company row uses the same domain.

Watch for subsidiaries that share a parent domain, Companies with several brands, and Contacts using Gmail or another personal mailbox provider. Those cases often need a different key.

Company name to Company name

Name matching is easy to understand and easy to audit manually. It is also sensitive to duplicate names, abbreviations, punctuation, and renames.

Use exact normalized matching for an import-preparation tool. Fuzzy matching may look helpful, but it can convert a similar name into the wrong CRM relationship. When two company rows normalize to the same name, stop and review them.

Record ID or a custom unique key

HubSpot Record ID is the clearest identifier when the source data already contains the correct Company record ID. A custom property configured to require unique values can play a similar role when both exports share a stable business key.

This approach is usually preferable to names because it expresses identity rather than similarity. It also avoids problems caused by later display-name changes.

| Match strategy | Best use | Main risk | | --- | --- | --- | | Email domain → company domain | Clean B2B email data | Shared domains and personal email addresses | | Company name → company name | Small, manually reviewable datasets | Duplicate and renamed companies | | Record/custom ID → same ID | Stable exported identifiers | Wrong environment or stale/incorrect ID source |

Keep the import identifier separate from the match key

The field you use to discover the relationship does not have to be the same field you send to HubSpot as the record identifier. For example, you can match by email domain but emit the Contact Email and Company Record ID in the final association CSV.

That separation is useful because it lets you use a human-friendly matching rule while still importing with a strong record identifier.

What the Nablyx builder does

The builder offers email-domain, company-name, and custom/record-ID matching. It normalizes the comparison value, rejects ambiguous company keys, keeps unresolved rows out of the final import, and adds Association label=Primary to confirmed pairs. Processing stays in the browser; the CSV contents are not sent to HubSpot by the tool.

HubSpot documents supported import identifiers in its import file setup guide.