On this page
What HubSpot supports natively
HubSpot imports several objects at once and associates them, as long as each row identifies both records:
| Approach | How records are linked | Sample file |
|---|---|---|
| One file, several objects | Each row has the contact’s and the company’s columns plus an identifier for each | Contacts and companies; contacts and companies with association labels |
| Two files | A common column (for example company name) links rows across files | Companies and contacts |
| Same-object associations | Contact-to-contact or company-to-company in one CSV | Company-to-company |
Rules from HubSpot’s import file guide:
- Identifiers: Record ID for any object, Email for contacts, Company domain name for companies, or a custom unique-value property.
- Rows without identifiers create new records. The exception: in a single-file, multiple-object import set to Create and update, rows with identical object data are treated as one record, even without an identifier. If the data differs at all, HubSpot creates separate records, and the exception doesn’t apply to Create new only or Update existing only imports.
- To associate one record with several others, repeat the row with a different identifier each time.
- Association labels (Professional or Enterprise): add an Association label column; the labels must already exist; use Primary for a primary company; separate several labels with semicolons.
How to import contacts and companies together
- Download the contacts and companies sample from HubSpot’s sample files, with or without association labels.
- One row per contact-company pair. Fill Email, First name, Last name, Company name and Company domain name.
- Add Record IDs for any contacts or companies that already exist, or rely on email and domain.
- Create the association labels first if you’re using them, such as Billing contact. See association labels.
- Start the import and choose multiple objects, then contacts and companies.
- Map each column to the right object. A column like Phone could belong to either; pick deliberately.
- Import ten rows first, open a few contacts and check their companies and labels.
- Import the rest and review the import’s error file.
Common mistakes
- Company name only, no domain. Outside the identical-data exception, every row becomes a new company, and a single spelling difference between rows breaks that exception too. Use the domain.
- Free email domains as company domains. Contacts with gmail.com addresses shouldn’t create a “gmail.com” company.
- Mapping company columns to contact properties. Check the object for every column on the mapping screen.
Where Jetstack AI fits
Jetstack AI doesn’t import records; in Projects, data imports are a step you do yourself. Projects can build what the import relies on first, such as custom properties, association labels and custom objects, so the import maps cleanly. Projects is currently in limited release; see what Projects can build.
Sources
- Set up your import file (HubSpot Knowledge Base)
- Sample import files (HubSpot Knowledge Base)
- Projects capabilities (Jetstack AI documentation)
Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
HubSpot admin
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects