Skip to content
Book a build

Can you clone an entire HubSpot portal?

No. HubSpot can't clone an entire portal into a new account. The closest native feature is a standard sandbox, which copies supported assets and up to 5,000 contacts once, and only as a test copy of the same account. A full copy is several jobs: configuration, content, records and settings, each with its own tool, plus integrations you reconnect by hand.

On this page

What HubSpot supports natively

FeatureHow close to a clone
Standard sandboxCopies 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 PortabilityCopy a short list of assets between linked accounts
Design Manager copyTemplates, themes and modules, without content
Export and importRecords 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:

JobWhat movesTypical route
ConfigurationProperties, pipelines, custom objects, association labels, lists, forms, emails, workflowsNative copy where accounts are linked; otherwise a configuration copy tool
ContentTemplates, themes, modules, pages, blog posts, HubDB tablesDesign Manager for themes; rebuild or a tool for pages
RecordsContacts, companies, deals, tickets, custom objects, activitiesExport and import, or a records migrator
SettingsUsers, teams, domains, subscription types, sending setupBy hand
ConnectionsIntegrations and connected appsReauthorize 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:

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

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 you clone an entire HubSpot portal?

No. HubSpot can't clone an entire portal into a new account. The closest native feature is a standard sandbox, which copies supported assets and up to 5,000 contacts once, and only as a test copy of the same account. A full copy is several jobs: configuration, content, records and settings, each with its own tool, plus integrations you reconnect by hand.

What's a HubSpot portal replicator?

A general name for tools that copy a portal's configuration into another portal. datawarehouse.io sells one called Schema Replicator, which copies configuration without records.

Can I clone a portal for a new client without their data?

Yes, that's the usual case: copy the configuration and content, not the records. Build from a template portal that holds no client data, so nothing personal travels with it.

Would a cloned portal stay identical to the original?

No. Copies are independent. Each portal changes on its own after the copy, so record which version each one started from.