---
title: "Consolidate two HubSpot instances into one"
description: "How to consolidate two HubSpot instances into one: choosing the receiving portal, settling conflicting setups, moving records and retiring the other account."
url: "https://jetstack.ai/answers/consolidate-two-hubspot-instances/"
---

# How do I consolidate two HubSpot instances into one?

To consolidate two HubSpot instances into one, pick the account that will survive, settle which properties, pipelines and lifecycle definitions win, then move the other instance's configuration and records into it. HubSpot can't merge accounts, so records move by export and import, which dedupes contacts by email and companies by domain. Retire the old instance only after you reconcile counts and switch integrations.

![](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 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

1. **Choose the receiving account** and write down why.
2. **Audit both.** List properties, pipelines, lifecycle stages, lead status values, workflows, forms and integrations in each.
3. **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.
4. **Build the combined configuration** in the receiving account: properties and options, pipelines and stages, custom objects, association labels.
5. **Create users and teams** so owner assignments carry over.
6. **Import records** in order (companies, contacts, deals, tickets, custom objects, activities), keeping each source record ID in a custom property.
7. **Move automation and content,** then point it at the combined properties and pipelines.
8. **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](https://jetstack.ai/answers/avoid-losing-data-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](https://jetstack.ai/roll-out) 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](https://jetstack.ai/build), 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](https://jetstack.ai/docs/implementations/deploying/how-it-works) and [what Projects can build](https://jetstack.ai/docs/projects/capabilities).

## Sources

- [Export your content and data (HubSpot Knowledge Base)](https://knowledge.hubspot.com/website-and-landing-pages/export-web-content-and-data)
- [Deduplication of records (HubSpot Knowledge Base)](https://knowledge.hubspot.com/records/deduplication-of-records)
- [Import objects (HubSpot Knowledge Base)](https://knowledge.hubspot.com/import-and-export/import-objects)

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.

How do I consolidate two HubSpot instances into one?

To consolidate two HubSpot instances into one, pick the account that will survive, settle which properties, pipelines and lifecycle definitions win, then move the other instance's configuration and records into it. HubSpot can't merge accounts, so records move by export and import, which dedupes contacts by email and companies by domain. Retire the old instance only after you reconcile counts and switch integrations.

Can HubSpot Support merge two accounts for me?

HubSpot doesn't offer an account merge. Its documentation says you can't merge all data between HubSpot accounts, so consolidation is an export-and-import project.

Which account should survive?

Usually the one with the more important history: the active email sending domain, the larger marketing database, the integrations the business relies on, or the higher subscription. Record the reasoning; it settles later arguments.

What if both instances have a property with the same name but different options?

Decide the surviving definition, add the missing options to it, and map the old values to the new ones in the import file. Don't import into a property whose options don't match, or values are dropped.
