On this page
What HubSpot supports natively
| Tool | What it does | Limit |
|---|---|---|
| Export all properties (Settings → Properties) | A file per object with each property’s name, internal name, type, description, group, options, creator, usages and fill rate | Export only; no matching import |
| Record import, “create a new property” | Creates a custom property for an unmatched column | One property at a time, defined by hand |
| Multi-account management | Creates a missing custom property when a copied asset uses it | Only properties that copied assets need |
| Sandbox deploy | Deploys new custom properties, groups and conditional logic | Sandbox to its own production; edits to existing properties don’t deploy |
| Properties API | Create properties, including in batches | Developer work |
How to import custom properties from another portal
- Export all properties from the source portal, choosing the objects you need.
- Filter to what you’ll use. Drop properties with no usages and an empty fill rate unless you have a reason to keep them.
- Export the destination’s properties too and compare internal names. A match with a different type or different options needs a decision, not a duplicate.
- Create the property groups first.
- Create each property with the same internal name, type, field type and, for dropdowns and checkboxes, the same internal option values. Labels can change; internal values shouldn’t.
- Create calculated, score and rollup properties last, after the properties they reference.
- Check the result by exporting the destination’s properties again and comparing.
Common mistakes
- Matching on labels. Workflows, lists, forms and integrations use internal names and internal option values.
- Changing types to fit. A property imported as text when the source was a dropdown breaks every filter that compares options.
- Forgetting access settings. Restricted or sensitive-data properties need their access set again in the destination.
To see what breaks if you skip a property, read what happens when a referenced property doesn’t exist in the target portal.
Where Jetstack AI fits
Jetstack AI’s Portal reuse imports property sets from one portal and deploys them to another, creating missing groups, reusing properties with the same internal name, adding missing dropdown options without removing existing ones, and creating a suffixed copy with a warning when types clash. It copies the properties people usually rebuild by hand, too. Calculated properties come across with their formulas remapped to the destination’s internal names, created after the inputs they read. Supported rollup definitions (count, sum, min, max, average, earliest or latest date), read from the source with the Chrome extension, are created after the properties and association labels they depend on and checked by reading them back. A rollup it can’t copy stops with an explicit error instead of landing as a plain property. Score properties map to an existing score property; for those, or any rollup shape Portal reuse doesn’t support, a Project (currently in limited release) can build them in the destination from a brief instead. You can also create properties in bulk from a spreadsheet. 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 bulk properties.
Sources
- Organize and export properties (HubSpot Knowledge Base)
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Import records for a single object (HubSpot Knowledge Base)
- Properties (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.
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