On this page
What HubSpot does natively
Each HubSpot copy route handles a missing property differently.
| Route | Missing custom property |
|---|---|
| Multi-account management | HubSpot creates it in the destination. The selection screen shows how many custom properties will be created. |
| Partner Portability (beta) | Required connected assets are added to the copy; custom objects copy with their custom properties. |
| Sandbox deploy | New custom properties and property groups can be deployed as connected assets. Edits to existing properties, and to HubSpot-defined properties, can’t. |
| Manual rebuild, CSV or script | Nothing creates it for you. The reference has no target. |
For new sandbox properties, HubSpot notes that access settings and sensitive-data settings must be set up again in production.
What breaks when the property is missing
A HubSpot asset refers to a property by its internal name. When that name doesn’t exist in the target portal:
- Workflow enrollment triggers and branches can’t evaluate, so records don’t enroll or go down the wrong branch.
- Set property actions have nothing to write to.
- List and segment filters lose the condition, which can widen or empty the list.
- Form fields mapped to the property can’t be created as that field.
- Personalization tokens in emails have no value to show.
The asset may still save. That’s the risk: it looks fine and behaves differently.
How to prevent missing property errors before you copy
- List the properties each asset uses. Check enrollment criteria, branch conditions, actions, form fields, list filters and email tokens.
- Compare with the target portal. Export all properties from both portals (Settings → Properties → Export all properties) and compare internal names, types and options.
- Create the missing ones first, with identical internal names, types and option values. See how to import custom properties from another portal.
- Map the ones that exist under another name instead of creating a duplicate.
- Copy the asset, then check each reference in the destination before activating it.
Calculated and rollup properties need extra care: they read other properties by internal name, so those dependencies must exist first. Score properties depend on the source portal’s scoring rules, so map them to a score property in the destination.
Where Jetstack AI fits
Jetstack AI’s Portal reuse compares every property a selected asset references against the target portal before deploying. Exact internal-name matches are used as they are, missing custom properties can be created, and properties that differ ask you to map them; required mappings must be set before the deploy can continue. If a property exists with a different type, Jetstack creates a suffixed copy and logs a warning rather than changing the existing one. Calculated and rollup properties don’t need building by hand: Jetstack copies calculated properties with their formulas remapped, and supported rollup definitions (read from the source with the Chrome extension) after the properties and association labels they depend on. A rollup it can’t copy fails with an explicit reason, and the assets that read it are held back instead of deploying with a broken reference. 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 property and asset mapping.
Sources
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Assets eligible to be deployed to production (HubSpot Knowledge Base)
- Property and asset mapping (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