Migration
Checked against HubSpot’s knowledge base, 3 November 2026.
How do you merge two HubSpot portals into one?
HubSpot has no button to merge two accounts. You choose the account to keep, map both setups onto one structure, move the records and their history across, and rebuild the things that don’t transfer, such as dashboards, saved views and email templates. Done well, with a test run first and the switch made over a weekend, your team logs in on Monday and carries on working.
Will Andrew
Founder & Lead Consultant
Running two HubSpot accounts?
Tell us about both and we’ll scope the merge after a short discovery call.
Why businesses end up with two HubSpot accounts
An acquisition or merger. Each business arrives with its own HubSpot.
Separate teams or brands. A second account was set up for a new product, country or division.
History. Someone started a fresh account years ago, and nobody closed the old one.
Two accounts mean two licences, two sets of reports, and teams who can’t see each other’s conversations with the same customers.
What HubSpot says
HubSpot’s knowledge base says there is no way to merge all the data between HubSpot accounts. Its advice is to export your data from one account and import it, or recreate it, in the other.
A plain export and import is fine for contacts and companies, but it loses a lot: emails, calls, meetings and notes don’t come out in a standard export, and associations between records need careful rebuilding. For most businesses, that history is the reason the merge matters.
HubSpot Enterprise accounts can also be linked to share some data between them, but that keeps two accounts. It isn’t a merge.
What moves across, and what has to be rebuilt
Usually moves across | Usually rebuilt by hand |
Contacts, companies and deals | Reporting dashboards |
Tickets and custom objects | Saved views and filters |
Notes, calls, meetings, emails and tasks | Email and message templates |
Associations between records | Workflows and sequences |
Record owners | Integrations with other tools |
Properties and pipelines (once mapped) | Marketing email history |
What can move depends on your HubSpot editions and the tools used, so check this list against your own accounts before you start.
The steps
Choose the account to keep. Usually the one with the most data, the most integrations or the better setup.
Map both setups. Pipelines, deal stages, properties, owners and teams. Decide what stays, what merges and what goes.
Agree how duplicates are handled. The same company or contact will often exist in both accounts. Decide which record wins and what happens to the other.
List everything that depends on the old account. Integrations, forms on your website, reports exported elsewhere, and anything connected with a user’s own login.
Run a test migration. Use a sandbox or test account to find problems before they touch real data.
Switch over out of hours. Freeze the old account, move the data, check it, and have the new account ready for the next working day.
Rebuild and tidy up. Dashboards, views, templates and integrations. Then set the old account to read-only, and cancel it once everyone is settled.
A real example: Octopus Energy
Octopus Energy ran its B2B partner network across two HubSpot accounts: one for its installer network of about 1,200 companies, and one for Zero Bills and Tenant Power, with UK and German teams. Teams working with the same partners couldn’t see each other’s history, and Octopus was paying for two licences.
We merged them into one account in three weeks:
A test run first. It showed that companies sharing the same website domain would collapse into one record, silently dropping the others. Every affected record was fixed before the real migration.
A weekend switch. The team used HubSpot as normal on Friday, we migrated on Saturday, and they logged in to the new account on Monday morning.
Nothing about ownership lost. Both accounts had different owners for the same records, so we kept the original owner history in its own property.
Rebuilt where tools couldn’t reach. A Google Sheets reporting workflow, saved views for both teams and the German team’s inbox.
Over 7,000 records moved across, no working day was lost, and retiring the second account saves Octopus £14,000 a year in licence costs. Read the full case study.
Common mistakes
Skipping the test run. Problems like the same-domain issue only show up with real data at full size.
Merging during the working week. People keep working in the old account and their changes get missed.
Forgetting the hidden dependencies. A report someone exports every Monday, or an integration connected with one person’s login.
Losing who owned what. When both accounts have owners for the same record, decide the rule before you migrate, and keep the old values.
Cancelling the old account too soon. Keep it read-only until the team is happy nothing is missing.
What a merge costs
A simple merge starts from £550. That’s when one account is small, both are set up in a similar way, and it’s mainly a case of moving records and their history across.
Most merges need consolidation as well: two sets of pipelines, properties, automations and reports to compare, decide on and rebuild as one. That’s where most of the work is, so we scope it in a short discovery call and quote a fixed price before anything starts. All prices exclude VAT.
Our take
A portal merge is a data project first and a HubSpot project second. Most of the work happens before anything moves: mapping, agreeing the rules for duplicates and owners, and finding everything that depends on the old account. Get that right and the switch itself is the quiet part.
If you’re merging after an acquisition, treat it as a chance to tidy up. There’s little point moving five years of unused properties into a clean account.
Frequently asked questions
Can HubSpot merge two accounts for us?
No. HubSpot’s knowledge base says there’s no way to merge all the data between accounts. You export from one and import or recreate it in the other, or bring in a partner to migrate it for you.
Will we lose our email and call history?
Not if it’s migrated properly. A standard export doesn’t include emails, calls, meetings and notes, so they need to be moved separately with their links to the right records.
How long does merging two HubSpot accounts take?
It depends on how much data and how many integrations you have. Octopus Energy’s merge took three weeks from preparation to live, with the switch itself done over one weekend.
Will our team lose time during the switch?
It shouldn’t. Run the migration over a weekend so the team stops on Friday and starts in the new account on Monday.
What happens to duplicate contacts and companies?
You agree the rules before the migration: which record wins, which details are kept and what happens to owners. A test run shows how many duplicates there are and whether the rules work.
Which account should we keep?
Usually the one with more data, more integrations or the better setup. Sometimes it’s simpler to keep the account on the higher HubSpot edition.
How much does it cost to merge two HubSpot accounts?
A simple merge starts from £550. Merges that need consolidation, such as combining two sets of pipelines, properties and automations, are quoted at a fixed price after a short discovery call.
Does merging save money?
Often. You stop paying for a second set of licences. For Octopus Energy, retiring the second account saves £14,000 a year.
Sources
HubSpot knowledge base, Export your content and data (merging data between accounts): https://knowledge.hubspot.com/articles/kcs_article/account/can-i-merge-data-resources-between-different-hubspot-accounts (checked 3 November 2026)
HubSpot knowledge base, Mirror data between HubSpot accounts with multi-account management: https://knowledge.hubspot.com/account-management/mirror-data-between-hubspot-accounts (checked 3 November 2026)
Pineo case study, Octopus Energy: https://pineo.com/case-studies/octopus-energy
Answers
