On this page
What HubSpot supports natively
| Feature | How close to a clone |
|---|---|
| Standard sandbox | Copies supported production assets and, optionally, the 5,000 most recently updated contacts, once at creation. Skips pages, reports, dashboards, integrations and surveys. It’s a test account tied to production, not a new portal |
| Multi-account management, Partner Portability | Copy a short list of assets between linked accounts |
| Design Manager copy | Templates, themes and modules, without content |
| Export and import | Records and activities, one file at a time |
HubSpot’s export guide says you can’t merge all data between HubSpot accounts. The same limits apply to cloning one.
How to build a full copy of a portal
Treat the clone as five separate jobs:
| Job | What moves | Typical route |
|---|---|---|
| Configuration | Properties, pipelines, custom objects, association labels, lists, forms, emails, workflows | Native copy where accounts are linked; otherwise a configuration copy tool |
| Content | Templates, themes, modules, pages, blog posts, HubDB tables | Design Manager for themes; rebuild or a tool for pages |
| Records | Contacts, companies, deals, tickets, custom objects, activities | Export and import, or a records migrator |
| Settings | Users, teams, domains, subscription types, sending setup | By hand |
| Connections | Integrations and connected apps | Reauthorize by hand |
Do them in that order, with workflows switched on last.
When a full clone is the wrong goal
Most “clone the portal” requests are really one of these:
- A starter setup for a new client. You want configuration only. See how to replicate a portal configuration for agency clients.
- A test environment. A standard sandbox fits, if you have Enterprise.
- Moving to a new account. That’s a migration, with records; see what a HubSpot-to-HubSpot portal migrator does.
Where Jetstack AI fits
Jetstack AI doesn’t clone an entire portal: it doesn’t copy CRM records, integrations, themes or account settings. Its Portal reuse handles the configuration and content jobs, copying selected assets and their dependencies with references remapped. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. 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. Pages and HubDB tables must be unpublished before they can be rolled back. For the settings job, a Jetstack AI Project can add lifecycle stages, subscription types and other supported settings in the new portal from a brief, with the plan and the deployment approved separately; users, teams, domains and sending setup stay manual, and Projects is currently in limited release. See the known limitations and what Projects can build.
Sources
- Production assets eligible to copy to a sandbox (HubSpot Knowledge Base)
- Export your content and data (HubSpot Knowledge Base)
- Copy assets to another HubSpot account (HubSpot Knowledge Base)
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