How to copy properties from one HubSpot account to another

HubSpot has no button that copies a set of properties from one account to another on its own, although some of its newer tools bring properties along with other things. It's a common need: an agency reuses its standard setup for each new client, a company moves to a new HubSpot account, or a team wants a test account that matches production. This guide covers what HubSpot can do on its own, where each option stops, and a faster way when you do this often.

First: is the other account a sandbox?

If you have an Enterprise subscription and the second account is meant for testing, use a HubSpot sandbox. It's the native tool that copies the most of a property setup.

• When you create a sandbox, HubSpot copies most properties from production, including calculated and rollup properties, plus default and custom property groups, validation rules and conditional property logic (what's copied).
• Not copied: dropdown properties that use controlling properties with conditional options, data agent settings, view and edit access settings, and property groups created by connected integrations.
• Back to production: after testing, a Super Admin can deploy supported changes from a standard sandbox to production, up to 300 changes per deploy (HubSpot guide). Legacy standard sandboxes stopped being supported on 30 April 2026, and deploy to production needs a new standard sandbox.

A sandbox only works between an account and its own sandbox. It can't copy from your agency's template account into a client's account, or between two production accounts.

Second: do the accounts belong to one organization, or are you a Solutions Partner?

HubSpot has two newer tools that copy between production accounts. Both copy assets, and bring properties along only as part of those assets.

• Multi-account management asset copying. If your accounts are connected in one organization, you can copy workflows, forms, segments and automated emails from one account to another. HubSpot creates the custom properties those assets use in the destination account. The organization's main account needs an Enterprise subscription, and the connected accounts need Professional or Enterprise (copy assets to another account, set up multi-account management).
• Partner Portability (beta). A Solutions Partner can copy agents, workflows, forms, automated emails, segments and custom objects, including the properties of those custom objects, from the partner's own account to a client account where the partner is a Partner Admin, in the same data region. HubSpot keeps a copy history (copy partner assets to client accounts).

If either fits, start there. What they don't do is copy a plain set of contact, company, deal or ticket properties, with their groups and options, as such; show a property-by-property difference before copying; or work for clients on Free or Starter outside a partner relationship.

Option 1: export the properties, then rebuild them

1. Export from the source account. Go to Settings > Properties, click Export all properties in the upper right, select the objects and a file format, and click Export. HubSpot emails you a download link (HubSpot guide). The file lists each property's name, internal name, type, description, group, options (if applicable), who created it, where it's used and its fill rate.
2. Create the groups in the target account. In Settings > Properties, open the Groups tab and click Create group for each custom group.
3. Create each property with Create property. For dropdowns, open the Field type tab, click Load options and paste the option labels from the export (HubSpot guide).

This is free and works on every plan, but it's manual. HubSpot has no import for that export file, so every property is created by hand. Watch out for:

• Internal names. Integrations, workflows and reports in the new account often expect the same internal names. Type them exactly, because HubSpot doesn't let you change a property's internal name after creating it.
• Option internal values. Load options sets each option's internal value from its label, and HubSpot says internal values can't be changed after saving. If the source account uses different internal values (common for older or integration-made properties), add those options with + Add option instead.
• Blank options for user-based properties. HubSpot Community members report that the options column comes out empty for Owner and HubSpot Team in property exports (Ideas thread). Those options are the account's users, so they can't be copied to another account anyway.

Option 2: create properties during a record import

If you're also moving records, HubSpot's import tool can create a property for an unmatched column: on the mapping step choose Create new property in the HubSpot Property column (HubSpot guide). It's one property per column, set up by hand in a side panel, and dropdown options must exist before the import. It saves a few clicks, not the setup work.

Option 3: use the Properties API

Developers can read properties from one account and create them in another with HubSpot's Properties API, which has batch create endpoints. It's flexible, but you need a private app or token in each account and a script that handles groups, option order, internal values and errors.

Where the built-in options stop

• Copying a standalone property set between two production accounts, or from an agency template account into client accounts, without workflows, forms or custom objects to carry it.
• Free and Starter client accounts, which sandboxes and multi-account copying don't cover.
• More than a handful of properties. Rebuilding 50 properties with their options by hand takes hours and invites typos.
• Seeing the difference first. Outside a sandbox deploy, none of the native routes show which properties and options differ between the two accounts before you start.
• Keeping accounts in step later, when someone adds an option in one account and not the other.

An app that copies the setup for you

Full disclosure: we built an app for this, Bulk Property Import & Export. Install it in both accounts and link them with a one-time code in the app settings. Then:

• Copy to another account shows a preview of the differences (new properties, changed labels, missing options) for the objects you choose, and copies properties, groups and options with their internal names and values. Nothing in the target account is removed unless you tick the option to do so.
• It works on any HubSpot plan, including Free and Starter, and you can run it again later to bring the accounts back in step.
• Export gives you the whole setup as CSV or JSON, with option labels and internal values. The CSV uses the same columns as the app's import, so you can also edit the file and import it into any account.

What it doesn't do: it doesn't copy records or property values, workflows, forms, pipelines or access settings. Calculation properties and properties whose options come from HubSpot users or records are listed in the preview but not copied, so you recreate those by hand. A custom object has to exist in the target account before its properties can be copied. It only asks for property settings permissions, so it never sees contact, company, deal or ticket records.

Export and import are free. Copying between accounts is part of Pro, which every new account gets free for 14 days (no card). Marketplace listing: https://ecosystem.hubspot.com/marketplace/listing/bulk-property-import-export. See the setup guide.

Short video of copying custom properties between two HubSpot portals (about 2 minutes, no sound, captions): https://youtu.be/VzkNEAdgr4U

FAQ

Can I import HubSpot's property export into another account? Not natively. HubSpot exports property definitions but has no import for them.

Do sandboxes copy properties? Yes, most of them, but only between an Enterprise account and its own sandbox.

Can multi-account management copy properties? Only the custom properties used by the workflows, forms, segments or emails you copy, and only with an Enterprise main account and Professional or Enterprise connected accounts.

Can I change an internal name after creating a property? No. That's why it's worth getting internal names right when you copy.

Questions or corrections: [e-mail]. HubSpot is a registered trademark of HubSpot, Inc. Kayabyte is an independent developer and is not affiliated with HubSpot. Originally published at https://kayabyte.dev/hubspot/guides/copy-hubspot-properties-between-accounts