Guide · HubSpot after an acquisition

Two HubSpot accounts can’t be merged. Here is how to combine them.

HubSpot has no merge button for accounts. One account absorbs the other: records are exported, matched and imported, and everything that runs on top of them is rebuilt. Done in the wrong order, the combined account inherits both companies’ duplicates and neither company’s reports.

This guide is the order of operations for a HubSpot to HubSpot consolidation after an acquisition or a merger of two teams.

Get a one-page teardown Read the guide

By Luis García · Last reviewed November 9, 2026 · 7 min read

The short answer

HubSpot says it plainly in its export documentation: there is no way to merge all the data between HubSpot accounts. The supported route is to export data from one account, then import it or recreate it in the other. HubSpot docs

So a "portal merge" is really three projects in one:

  • A decision project. Which account survives, which definitions win, and who owns each shared customer.
  • A data project. Contacts, companies, deals, tickets, custom objects, their associations and their history.
  • A rebuild project. Workflows, forms, lists, reports, sequences, templates and integrations, which point at IDs that only exist in the old account.

Most of the risk sits in the first project, which is why it comes first here.

First, check you need one account

Combining accounts is the right call when one sales team will sell to one customer base, or when leadership needs one pipeline and one set of numbers. It is the wrong call when the acquired business will keep operating separately for a long time, or when legal, regional or contractual reasons require its data to stay apart. Get that answer in writing before any export.

If the two businesses must stay separate but share a brand or a team, look at HubSpot’s options for running several brands inside one account, or for linking accounts on Enterprise, before committing to a migration. Both keep complexity, just in a different place.

Choose the account to keep

Seniority is a poor reason to pick the destination. Compare the two accounts on the things that are expensive to change:

  1. Subscriptions and seats. Which tools each team depends on, at which tier. A workflow that needs Professional will not rebuild on Starter.
  2. Integrations. Every connected app, and above all a Salesforce, billing or product sync. These are the hardest pieces to repoint.
  3. The website. The account whose tracking code, forms and domains are live on the main site carries traffic history that does not move.
  4. Data model. Custom objects, pipelines and association labels. The cleaner, simpler model is usually cheaper to keep.
  5. Data quality. Duplicate rates, companies without a domain, records with no owner.
How to check

Open Settings > Integrations > Connected apps in both accounts and list every app, what it writes, and who owns it. Then open Settings > Objects and list custom objects and pipelines. The account with fewer things you would have to rebuild is usually the destination.

Agree definitions before mapping fields

Two accounts can use the same property with different meanings. "SQL" might mean a booked meeting in one company and confirmed budget in the other. "Customer" might mean any paid invoice, or an active contract. If those values are mapped by label, the combined funnel reports a number nobody can explain.

Write one page with every lifecycle stage, lead status, deal stage and deal type from both accounts, side by side, and get the sales and marketing owners on both sides to sign one meaning for each. Where a meaning cannot be agreed yet, map old values into a temporary field so trends stay readable for a quarter.

Definitions sheet · excerpt Account A and Account B Illustrative

Four values that will not map by label

ValueAccount AAccount BDecision
Lifecycle: SQLMeeting bookedBudget confirmedSQL = meeting booked. B’s meaning moves to a deal stage.
Lifecycle: CustomerAny paid invoiceActive contractActive contract. Past customers get a separate value.
Deal stage: Closed wonContract signedFirst payment receivedContract signed, with a contract date property.
Deal type: New businessNew logoAny new dealNew logo only. Upsells use Existing business.

Illustrative excerpt. Your values and owners decide the real sheet.

Match the records both accounts share

Record IDs are specific to each account, so they cannot be used to match records across accounts. Matching has to run on business keys, and each object needs its own rule:

  • Contacts on email address, which is how HubSpot deduplicates contacts on import. Watch for people with a personal and a work address.
  • Companies on company domain, with a reviewed list for subsidiaries, regional domains and companies created without a domain by integrations. HubSpot docs
  • Deals are rarely duplicated across accounts, but two open deals for the same account and product are a commercial question for the two owners, not a merge rule.

Before any import, create a property in the destination for the source account’s Record ID on every object, and set it to require unique values. Use it as the identifier in every import file. It lets you re-run a failed batch without creating copies and trace any record back to where it came from. HubSpot docs

How to check

Export companies from both accounts with Company domain name and Record ID. Count exact domain matches, then review a sample of 50 near matches by hand. The size of that review queue is the best early estimate of how hard the merge will be.

Decide what history must survive

A plain export and import moves properties. It does not carry everything the team thinks of as "the record". Make a list, object by object, of what must still be visible after the move, and test each item in a sandbox or test account first:

  1. Associations. Contact to company, deal to company, deal to contact, with their labels. Imports can create associations and labels, but only if the files carry the keys.
  2. Activity history. Calls, meetings, notes and tasks can be imported as activities. Logged emails and marketing engagement need a plan, often an integration tool or the API.
  3. Dates. Imported records get a new create date. Store the original create date and the date each deal entered its stages in properties, and point reports at those.
  4. Owners. Owners map by user. Records owned by people who left need a named home before import day.
  5. Consent. Recreate subscription types in the destination first, then import opt-outs and check a sample before a single email is sent from the combined account.

Rebuild what points at the old account

Anything that references internal IDs needs to be rebuilt or repointed, because those IDs do not exist in the destination:

  • Workflows and sequences reference properties, lists and owners. Rebuild them from the agreed definitions, and do not switch on two routing workflows that both assume they own the same lead.
  • Forms and tracking code embedded on the website belong to the source account. Swap them on a set date, and keep form fields mapped to the destination’s properties.
  • Reports and dashboards are rebuilt, not copied. Start with the five reports leadership actually opens.
  • Integrations. If either account syncs with Salesforce, a billing tool or your product, settle the destination’s sync rules before importing, or the sync will create or overwrite records while you are loading them. HubSpot docs

Cut over, then freeze the old account

The order that keeps the combined account usable:

  1. Test load. Your ten hardest accounts, both sides, into a test account. Check contacts, deals, owners and labels on each.
  2. Freeze. Agree a date after which no one creates properties, workflows or imports in the source account.
  3. Load in dependency order. Companies, then contacts, then deals and tickets, then activities, then associations that were not carried in earlier files.
  4. Reconcile. Count by object, then compare last quarter’s closed-won total and open pipeline by owner against the source. Explain every difference in writing.
  5. Read-only, then retire. Keep the source account available to a few people for reference until the first reporting cycle closes on the destination.
How to check

On the morning after cutover, open five shared customers in the destination. Each should show one company, the right owner, every open deal, and its contacts with their roles. If any of the five fails, stop and fix the rule before users find the rest.

Sources used in this guide

Last reviewed November 9, 2026 by Luis García Checked against the HubSpot and Salesforce documentation linked above

Questions

Can HubSpot support merge two accounts for us?

No. HubSpot’s documentation says there is no way to merge all data between HubSpot accounts. Data is exported from one account and imported or recreated in the other, by your team or a partner.

Should we just keep both HubSpot accounts?

Sometimes, for a set period with a cutover date. Running two accounts indefinitely means two definitions of every number, and combined reporting ends up in spreadsheets.

What usually breaks first after a portal merge?

Ownership and routing. Shared customers end up with two owners or none, and two sets of workflows fight over the same field. Agree ownership rules and switch off duplicate workflows before go-live.

How long does a HubSpot to HubSpot migration take?

It depends on the number of objects, integrations and how far the two companies’ definitions diverge. It should be scoped after seeing both accounts, with a written plan and acceptance checks.

Combining two HubSpot accounts?

Send your website and a line on both accounts. The teardown names the decision that will decide whether the combined account is usable, and the first check to run.

Get a one-page teardown

Written by Luis, back within 1 business day. No call needed. Prefer to talk? Book a 20-minute fit call.

Sample teardown · real, anonymized Acquired customers are a migration, not a pipeline. One page for a new CRO, written from public information before any call: what public signals show, the likely gap, the fix order and one CRM pull to check it. Read the full page →