On this page
What HubSpot supports natively
HubSpot has no merge feature for accounts. Its export guide says you can’t merge all data between HubSpot accounts: export from one, then import or recreate in the other.
| Need | Native route | Limit |
|---|---|---|
| Records | Export, then import with associations | Contacts dedupe on email and companies on primary domain; other objects don’t dedupe unless you include a Record ID or unique-value property |
| Activities | Import calls, meetings, notes, tasks and emails | Existing emails, meetings, notes and tasks can’t be updated by import |
| Workflows, forms, segments, automated emails | Multi-account management, if both accounts are in one organization | Only those four types |
| Templates and modules | Design Manager “Copy to different account” | Files only, not content |
How to consolidate two HubSpot instances
- Choose the receiving account and write down why.
- Audit both. List properties, pipelines, lifecycle stages, lead status values, workflows, forms and integrations in each.
- Settle the conflicts. For every duplicate concept, decide which definition wins: which “Region” property, which sales pipeline, which lifecycle rules. This is the slowest step and the one tools can’t do for you.
- Build the combined configuration in the receiving account: properties and options, pipelines and stages, custom objects, association labels.
- Create users and teams so owner assignments carry over.
- Import records in order (companies, contacts, deals, tickets, custom objects, activities), keeping each source record ID in a custom property.
- Move automation and content, then point it at the combined properties and pipelines.
- Switch integrations, tracking code, forms and sending domains, reconcile counts, and keep the retiring account read-only for a period.
When it’s worth getting help
Get help if both instances run active marketing email (subscription and consent status must survive), if integrations write to both, or if the two sales teams use different pipelines for the same motion. The records move is mechanical; agreeing on one setup is not.
For the records step in detail, see how to avoid losing data in a HubSpot-to-HubSpot migration.
Where Jetstack AI fits
Jetstack AI doesn’t merge portals and doesn’t move CRM records. Once you’ve settled the combined design, its Portal reuse can copy the configuration you’re keeping from the retiring instance into the receiving one, matching assets that already exist there by name and remapping references. 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. Where the combined design needs something neither instance has, such as a combined pipeline or a new property, build it in the receiving account with Projects, currently in limited release: you describe it in a brief, approve the plan and then the deployment, and get a receipt read back from HubSpot. See how matching and remapping work and what Projects can build.
Sources
- Export your content and data (HubSpot Knowledge Base)
- Deduplication of records (HubSpot Knowledge Base)
- Import objects (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