On this page
What HubSpot supports natively
An association label has two layers: the definition (“Decision maker” between contacts and companies) and the labeled associations on records. HubSpot handles them separately.
| Need | Native route | Limits |
|---|---|---|
| Label definitions, sandbox to production | Sandbox deploy includes new object associations | Only to the sandbox’s own production account; edits to existing ones don’t deploy |
| Label definitions, any other portal | None. Create them in the destination’s settings or through the associations API | Manual |
| Labeled associations on records | Import, with association label columns | Professional or Enterprise; a new label in the file won’t overwrite an existing one |
Multi-account management doesn’t copy association labels.
How to copy association labels to another portal
- List the custom labels in the source for each object pair, in both directions. A label between contacts and companies has a forward and an inverse name, which may differ (for example “Parent” and “Child”).
- Note any association limits, such as one “Primary contact” per company.
- Create custom objects first if a label involves one; the label needs the object to exist.
- Create each label in the destination with the same names and limits.
- Import the records with association label columns, after both records and labels exist.
- Update anything that filters on labels: workflows, segments, reports and integrations.
Common mistakes
- Creating labels after the import. Records arrive with plain, unlabeled associations, and you relabel them by hand.
- Recreating HubSpot’s default labels. They already exist; a copy just adds confusion.
- Matching only one direction. Check the inverse label’s name, not just the forward one.
For the object side, see how to copy custom objects to another portal.
Where Jetstack AI fits
Jetstack AI’s Portal reuse copies user-defined association label definitions between any two connected portals, creating both directions, remapping custom object type IDs, and reusing a label that already exists with the same name. It sets association limits where HubSpot allows them and warns where it doesn’t. Labels between a custom object and its partners come with the object. Check the labels in the destination after deploying. It doesn’t move records or their associations. You can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. See the association labels reference.
Sources
- Assets eligible to be deployed to production (HubSpot Knowledge Base)
- Import objects (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.
Copy & migrate between portals
Take a proven setup to the next portal.
Import a setup with its dependencies, map it to the destination portal and deploy it with references rewritten.
Explore Portal reuse