Merge Two HubSpot Portals: 3 Decisions Before Any Data Moves

Key takeaways
You cannot merge two HubSpot portals with one click: HubSpot's route is to export from one account and import into the other. Founders and heads of sales should first choose the surviving portal, decide whose properties and stages win, and name one owner of the merged pipeline before anyone exports.

The second HubSpot portal’s contract renews on a date your finance team already knows, and the plan is “export everything and import it into ours”. To merge two HubSpot portals before that date, three decisions come before any export. No import tool will make them for you.

Moving records is the easy part. The hard part is that two portals carry two definitions of a lead, a deal stage and an owner. Merge without choosing one set, and the combined portal keeps both. Then nobody trusts the reports.

What HubSpot actually offers when you merge two HubSpot portals

There is no button that combines two accounts. HubSpot’s export guide says plainly that there is no way to merge all the data between HubSpot accounts. The route it describes is to export data from one account, then import the objects or recreate the rest in the other.

Records, properties and reports export. Some things travel badly. Workflows export as a spreadsheet or a PNG image of a single workflow, not as working automation, and without their history or performance data. Past chat transcripts are not exported directly. Forms lose paid features and legacy CTAs stop working once the old account is deactivated.

The import side is strict. HubSpot’s import file guide requires every column header to match a property, and for deals the pipeline and stage values must already exist in the receiving account. Dropdown values must match options that are already defined. Without a unique identifier, such as email for contacts or company domain for companies, the import creates duplicates instead of updating records.

HubSpot does have multi-account management, which lets separate accounts share selected data, copy some assets and report across accounts. It is not a merge: each business keeps working in its own account. The setup flow includes reviewing beta feature information, so treat it as an evolving feature.

Who this matters for

  • Founders after an acquisition or a merger of two teams, who now pay for two portals and want one view of revenue.
  • Heads of sales whose two teams sell in one market but report from different pipelines with different stage names.
  • Heads of marketing who need one contact database, one set of lists and one attribution story, not two.

What to decide and check before any data moves

  1. Decide which portal survives. Pick the account with the cleaner data model and the integrations you keep, not the one with more records.
  2. Decide whose properties and stages win. Open Settings, then Properties, select an object, and list both portals’ properties side by side, as described in HubSpot’s properties guide. For each pair, keep one, rename one, or retire one. Do the same for deal stages under Settings, Data Management, Objects, Deals, Pipelines tab, using the pipelines guide. Build the final pipelines before the first import, because imports only accept stages that already exist.
  3. Decide who owns the merged pipeline. One person approves stage definitions, required properties and who can edit them. Without that owner, the second team rebuilds its old portal inside the new one.
  4. Plan the overlap. Contacts and companies that exist in both portals will need a matching key, or they will arrive as duplicates. If duplicates slip through, HubSpot’s merge records feature combines them, but merges cannot be undone, so agree on the rules first.
  5. List what must be rebuilt by hand. Export the workflows list from Automation, Workflows, Table actions, Export view, and decide which ones the surviving portal really needs.

We covered the record mapping side in our Salesforce to HubSpot migration and monday.com to HubSpot migration posts.

Our take

A portal mirrors how a team works. Two portals mean two processes, and a merge is the one moment when someone has the authority to pick one. Skip that question and both definitions of a qualified lead end up in one database.

The cost is mostly in hours of decisions, not hours of data moving. Budget time for a head of sales and a head of marketing to agree on stages, lifecycle definitions and ownership before the technical work starts. If nobody can give those hours before the renewal date, renew the second portal for one more term and merge properly, rather than merging fast and cleaning up for a year.

And if the two teams genuinely sell differently, say so out loud. Two pipelines in one portal, with shared contacts and companies, is a valid design. Forcing one pipeline on two motions breaks the forecast for both.

Implementation

Planning a HubSpot rollout or a migration?

We set up pipelines, data and onboarding so the team actually uses it.

Plan your rollout

FAQ

Can you merge two HubSpot accounts into one?

Not directly. HubSpot’s export documentation says there is no way to merge all the data between accounts. You export from one account and import or recreate the data in the other, so the data model of the surviving account has to be ready first.

What happens to workflows when you merge HubSpot portals?

They do not move as working automation. You can export a workflows list as a spreadsheet or a single workflow as an image, then rebuild the ones you still need in the surviving portal.

Should we merge our HubSpot portals or keep them separate?

Merge when both teams sell to the same buyers and need one forecast. Keep them separate, or connect them with multi-account management, when the businesses stay separate.

This week, put the renewal date of the second portal on the calendar and book one meeting with the heads of sales and marketing. Leave it with three names written down: the surviving portal, the owner of the merged pipeline, and the person who signs off on stage definitions. The exports can wait until those exist.

Alignify

Alignify is a HubSpot implementation and admin team. We set up portals, clean up CRM data and run HubSpot as a service for B2B companies.

On this page

Get the audit checklist

All 25 checks as a spreadsheet with auto-scoring.

By submitting, you agree to our Privacy Policy.

Talk to Alignify

45 minutes, your portal on screen, no slides. We show what we would fix first.

Want a second set of eyes on your HubSpot?

Book a 45-minute portal review. We look at your portal together on a screen share and show what we would fix first. No slides, no sales pitch.