On this page
What HubSpot supports natively
An association says two records are connected. A label says how. HubSpot’s rules:
| Topic | What HubSpot says |
|---|---|
| Subscription | Professional or Enterprise (Marketing, Sales, Service, Data, Content Hub or Smart CRM) |
| Permissions | Super Admin to create labels |
| Limit | Up to 50 labels per object pair; a paired label counts as one |
| Single label | Both sides use the same word, e.g. Colleague or Partner |
| Paired labels | Each side has its own word, e.g. Parent and Child; setting one sets the other |
| Association limits | Per direction: Many, or a custom number of records |
| Where they’re used | Segment filters, workflow triggers, branches and actions, report axes, breakdowns and filters |
| Deleting | Permanent; remove the label from records and tools first |
When to use association labels
Use a label when the relationship itself carries meaning that a property on either record can’t hold:
| Situation | Use | Why |
|---|---|---|
| A contact is the billing contact for one company and a user at another | Label on contact-to-company | The role differs per company, so it can’t be a contact property |
| A deal has a decision maker, a champion and a blocker | Labels on contact-to-deal | Workflows can email only the decision maker |
| A franchise company has many location companies | Paired labels Parent and Child on company-to-company | Reports can roll up by parent |
| A contact is a “VIP” | Property on the contact | It’s true of the contact everywhere |
| A deal has exactly one primary contact | Label with a limit of 1 | The limit stops a second one being added |
How to set up association labels
- List the relationships that drive actions: who gets which email, who owns which renewal, which company rolls up into which.
- Decide single or paired for each. If the two sides need different words, use a paired label.
- Create them in the data model or object settings as a Super Admin, and set association limits where only one record should hold the role.
- Add them to imports with an Association label column. See importing contacts and companies together.
- Use them: build a segment that filters on the label, or a workflow that emails only the contacts with it.
- Document each label’s meaning, since nothing in HubSpot explains what Partner means to your team.
Common mistakes
- Using labels as tags. If it’s about one record, use a property.
- Too many near-duplicates like Decision maker and Decision-maker. Agree names before creating them.
- No limits on roles that should be unique. Without a limit, two contacts can both be the primary.
Where Jetstack AI fits
To set up new labels, use Jetstack AI’s Projects: name the labels and the objects they connect in a brief (for example “Billing contact” and “Decision maker” between contacts and companies), approve the plan, then approve deployment separately. Labels are built alongside the properties and custom objects they connect, and the receipt confirms each one by reading it back from HubSpot. Projects is currently in limited release; see what Projects can build. To copy labels to another portal, Portal reuse imports user-defined labels, creates both directions of a paired label, remaps custom object IDs and skips labels that already exist in the destination. Setting a label’s limit is attempted afterwards and is reported as a warning if HubSpot refuses it. See how association labels are deployed.
Sources
- Create and use association labels (HubSpot Knowledge Base)
- Set up your import file (HubSpot Knowledge Base)
- Association labels (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