Skip to content
Book a build

How do I copy or import custom properties from another HubSpot portal?

HubSpot can export custom properties but has no import for property definitions. To import custom properties from another HubSpot portal, export all properties from the source, then recreate each one in the destination with the same internal name, type and option values, by hand, through the properties API, or with a tool. Multi-account copies and sandbox deploys create missing properties only for assets they copy.

On this page

What HubSpot supports natively

ToolWhat it doesLimit
Export all properties (Settings → Properties)A file per object with each property’s name, internal name, type, description, group, options, creator, usages and fill rateExport only; no matching import
Record import, “create a new property”Creates a custom property for an unmatched columnOne property at a time, defined by hand
Multi-account managementCreates a missing custom property when a copied asset uses itOnly properties that copied assets need
Sandbox deployDeploys new custom properties, groups and conditional logicSandbox to its own production; edits to existing properties don’t deploy
Properties APICreate properties, including in batchesDeveloper work

How to import custom properties from another portal

  1. Export all properties from the source portal, choosing the objects you need.
  2. Filter to what you’ll use. Drop properties with no usages and an empty fill rate unless you have a reason to keep them.
  3. 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.
  4. Create the property groups first.
  5. 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.
  6. Create calculated, score and rollup properties last, after the properties they reference.
  7. 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

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

Copy & migrate between portals

Related questions.

How do I copy or import custom properties from another HubSpot portal?

HubSpot can export custom properties but has no import for property definitions. To import custom properties from another HubSpot portal, export all properties from the source, then recreate each one in the destination with the same internal name, type and option values, by hand, through the properties API, or with a tool. Multi-account copies and sandbox deploys create missing properties only for assets they copy.

Can I create properties during a record import?

Yes, one at a time. When an import column doesn't match a property, HubSpot lets you create a new custom property for it in the mapping step. That's fine for a few fields, but it doesn't copy option values or groups from the source.

Do property values come across too?

Not with the definitions. Values live on records, so they move when you import the records into the new properties.

What about calculated and rollup properties?

Recreate them after the properties their formulas use. A formula that refers to a missing internal name can't be saved as intended. Jetstack's Portal reuse handles that order for you: it copies calculated properties and supported rollups after the properties they read.