---
title: "Can I copy settings to a new HubSpot portal? · Jetstack AI"
description: "Whether you can copy settings to a new HubSpot portal: what HubSpot's copy features skip, and a checklist of account settings to recreate in the new portal."
url: "https://jetstack.ai/answers/copy-settings-to-new-hubspot-portal/"
---

# Can I copy settings to a new HubSpot portal?

Mostly no. HubSpot's copy features move assets such as workflows, forms, segments and automated emails, not account settings. Users, teams, permissions, domains, sending setup, subscription types, currencies and integrations have to be set up again in the new HubSpot portal. Properties, pipelines and record layouts sit in between: no native route copies them between unrelated portals, but tools can.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 29, 2026

On this page

## What HubSpot supports natively

HubSpot’s cross-account features copy assets, not settings.

| Native feature             | Copies                                                                                           | Doesn’t copy                                                               |
| -------------------------- | ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------- |
| Multi-account management   | Automated emails, forms, segments, workflows; creates missing custom properties those assets use | Account settings; custom subscription types must be set in the destination |
| Partner Portability (beta) | Agent templates, workflows, forms, automated emails, segments, custom objects                    | Account settings                                                           |
| Standard sandbox           | Supported assets and some users, once, at creation                                               | Integrations; and it’s the same account’s sandbox, not a new portal        |
| Export all properties      | A file of property definitions                                                                   | No matching import                                                         |

## Settings to recreate in a new portal

Work through these in roughly this order:

| Area              | What to set up                                                                                     |
| ----------------- | -------------------------------------------------------------------------------------------------- |
| Users and access  | Users, teams, permission sets, Super Admins                                                        |
| Account defaults  | Company name, time zone, currencies, fiscal year                                                   |
| Data model        | Properties and groups, lifecycle stage and lead status options, custom objects, association labels |
| Sales and service | Deal and ticket pipelines, stage properties, deal rotation, record page layouts                    |
| Marketing         | Subscription types, email sending domain, footer, brand settings                                   |
| Website           | Domains, tracking code, cookie banner and privacy settings                                         |
| Connections       | Connected inboxes and calendars, integrations, private apps                                        |

## How to copy the setup faster

1. **Export properties from the old portal** and use the file as your blueprint. Keep internal names identical.
2. **Copy assets with the native routes** where your accounts are linked, and expect missing custom properties to be created for you on multi-account copies.
3. **Document everything that’s only in settings screens.** Screenshots of pipeline rules, rotation and record layouts save rework.
4. **Reconnect integrations last,** once properties exist, and check their field mappings.

If you’re replicating a whole setup rather than a few settings, see [whether you can clone an entire HubSpot portal](https://jetstack.ai/answers/clone-entire-hubspot-portal).

## Where Jetstack AI fits

Jetstack AI doesn’t copy account-level settings such as users, domains or integrations. Its [Portal reuse](https://jetstack.ai/roll-out) copies the configuration around them: properties, pipelines, custom objects and association labels, plus settings-like assets such as permission sets (as definitions, not assigned to users), lead scoring, CRM cards and preview views, some of which need the Chrome extension. 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. For settings Portal reuse doesn’t copy, such as lifecycle stages, subscription types, meeting types, call outcomes and the properties required at a deal or ticket stage, a Jetstack AI [Project](https://jetstack.ai/build) can add them in the new portal from a brief, with a plan and the deployment each approved separately and a receipt read back from HubSpot. Projects only adds to settings, never deletes them, and is currently in limited release. See [Ultimate assets](https://jetstack.ai/docs/implementations/asset-types/ultimate-assets) and [what Projects can build](https://jetstack.ai/docs/projects/capabilities).

## Sources

- [Copy assets to another HubSpot account (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/copy-assets-to-another-hubspot-account)
- [Set up a HubSpot standard sandbox account (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account/set-up-a-hubspot-standard-sandbox-account)
- [Organize and export properties (HubSpot Knowledge Base)](https://knowledge.hubspot.com/properties/organize-and-export-properties)
- [Ultimate assets (Jetstack AI documentation)](https://jetstack.ai/docs/implementations/asset-types/ultimate-assets)

Checked October 29, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

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](https://jetstack.ai/roll-out)

On this page

Copy & migrate between portals

## Related questions.

Can I copy settings to a new HubSpot portal?

Mostly no. HubSpot's copy features move assets such as workflows, forms, segments and automated emails, not account settings. Users, teams, permissions, domains, sending setup, subscription types, currencies and integrations have to be set up again in the new HubSpot portal. Properties, pipelines and record layouts sit in between: no native route copies them between unrelated portals, but tools can.

Does a sandbox copy settings from production?

It copies supported assets and some users at creation, but HubSpot says integrations aren't connected and sandbox users are managed independently. A sandbox is also a copy of the same account, not a new production portal.

Can I export my settings to a file?

You can export all property definitions from Settings → Properties, which helps you compare portals. HubSpot doesn't offer a general settings export you can import into another account.

Do permission sets copy?

Not natively between accounts. Recreate them, then assign users in the new portal.
