Skip to content
Book a build

Can I copy HubSpot custom objects to another portal?

Yes, in some cases. Partner Portability copies custom objects with their custom properties from a partner account to a managed client, and a standard sandbox can deploy new custom objects to production. Between other portals, recreate the schema by hand or through the schemas API, then add pipelines, association labels and records. To copy HubSpot custom objects with their records, import the records afterwards.

On this page

What HubSpot supports natively

RouteCustom objects?Limits
Partner Portability (beta)Yes: the object and its custom propertiesPartner account → managed client only
Sandbox deployNew custom objects, new properties and associationsEdits to existing custom objects don’t deploy
Multi-account managementNoCopies automated emails, forms, segments and workflows
Import toolRecords onlyThe object must already exist in the destination

How to copy custom objects to another portal

A custom object is several parts. Rebuild them in this order:

  1. The schema: internal name, singular and plural labels, primary display property, and which properties are required and searchable. Developers can create this through HubSpot’s custom object schemas API.
  2. The properties, with the same internal names, types and option values as the source.
  3. Associations and labels between the object and contacts, companies, deals or other custom objects. See how to copy association labels.
  4. Pipelines, if the object uses them.
  5. The records, by export and import, with their associations. Keep the source record ID in a property.
  6. The assets that use the object: workflows, lists, reports and record page layouts, pointed at the new object type ID.

Common mistakes

  • Mismatched internal names. Integrations and API scripts look up the object and its properties by internal name.
  • Importing records before associations exist. Associations can’t be set if the association definition isn’t there yet.
  • Hitting the plan limit. HubSpot caps how many custom objects a portal can have by subscription; check the destination’s allowance before planning a copy.

Where Jetstack AI fits

Jetstack AI’s Portal reuse copies the full custom object schema between any two connected portals and deploys it before everything else, so dependent properties, lists and workflows can be remapped to the new object type ID. Pipelines and custom association labels come along with the object. If the destination already has an object with the same name or label, Jetstack uses it and doesn’t change its schema. It doesn’t move records. 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. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See custom object handling.

Sources

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

Copy & migrate between portals

Related questions.

Can I copy HubSpot custom objects to another portal?

Yes, in some cases. Partner Portability copies custom objects with their custom properties from a partner account to a managed client, and a standard sandbox can deploy new custom objects to production. Between other portals, recreate the schema by hand or through the schemas API, then add pipelines, association labels and records. To copy HubSpot custom objects with their records, import the records afterwards.

Will the object type ID be the same in the new portal?

No. Each portal assigns its own object type ID. Workflows, lists, reports and integrations that use the old ID need updating.

Can I copy the custom object's records?

Not with the copy features. Export the records and import them into the destination; HubSpot's import tool supports custom objects and associations.

What if the destination already has a similar object?

Compare the schema before creating a second one. If it serves the same purpose, add the missing properties to the existing object rather than creating a near-duplicate.