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
- Export properties from the old portal and use the file as your blueprint. Keep internal names identical.
- 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.
- Document everything that’s only in settings screens. Screenshots of pipeline rules, rotation and record layouts save rework.
- 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.
Where Jetstack AI fits
Jetstack AI doesn’t copy account-level settings such as users, domains or integrations. Its Portal reuse 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 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 and what Projects can build.
Sources
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
- Set up a HubSpot standard sandbox account (HubSpot Knowledge Base)
- Organize and export properties (HubSpot Knowledge Base)
- Ultimate assets (Jetstack AI documentation)
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