On this page
What HubSpot supports natively
HubSpot’s sample import files article offers templates in three groups:
| Group | Templates |
|---|---|
| One object (XLSX or CSV) | Contacts, Companies, Deals, Tickets, Products, Tasks, Calls |
| Several objects in one file | Contacts and companies; contacts and companies with association labels; contacts and tickets; companies and deals; companies and notes; companies, deals and notes; and more |
| Several objects in two files | Companies and contacts linked by company name; deals and companies with association labels; deals and line items; calls and contacts |
| Same-object associations (CSV) | Contact-to-contact, company-to-company, deal-to-deal, ticket-to-ticket |
For anything not listed, the import tool can generate an example file for the objects you choose, with their required properties.
Required columns to create records:
| Object | Required |
|---|---|
| Contacts | |
| Companies | Name or Company domain name |
| Deals | Deal name, Pipeline and Deal stage (the stage must belong to that pipeline) |
Identifiers to update existing records: Record ID for any object, Email for contacts, Company domain name for companies, or a custom property that requires unique values.
How to build a HubSpot import template that works first time
- Start from the official sample for your objects, or generate one in the import tool.
- Match headers to property labels or internal names so columns map automatically.
- Add an identifier column (Record ID, Email or domain) if any row updates an existing record. Without it, you get duplicates.
- Create missing properties first. You can create one per unmapped column during the import, but a long list is quicker done beforehand; see bulk creating properties.
- Check option values against each dropdown’s internal values.
- Use a consistent date format such as year-month-day. HubSpot accepts several orders and separators.
- Test with ten rows, check the records, then import the rest.
Common mistakes
- Two companies, one domain. Custom unique properties don’t enforce uniqueness for company domains, so duplicate domains can be imported.
- Wrong pipeline stage. A deal stage from another pipeline fails the row.
- Associations without identifiers. To link records in one file, each row needs an identifier for both. See importing contacts and companies together.
Where Jetstack AI fits
Jetstack AI doesn’t import records; in Projects, importing or migrating data is listed as a step you do yourself. What it can do is build the structure an import depends on, such as properties with their options, custom objects and association labels, before you load the file. See what Projects can build.
Sources
- Sample import files (HubSpot Knowledge Base)
- Set up your import file (HubSpot Knowledge Base)
- Projects capabilities (Jetstack AI documentation)
Checked October 29, 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