Clean CRM Data Migration: Merge Portals
Two HubSpot portals usually exist for a reason that made sense at the time. A regional team set up its own. An acquired company came with its account. Marketing and sales started on separate subscriptions. Eventually someone decides it should all live in one place, and that is when the real size of the job appears.
The hard part of merging portals is not moving the data. It is moving it without creating a second copy of every person and company that already exists in both. This guide covers why that happens and how to run a clean CRM data migration between HubSpot accounts.
Why Portal Merges Create So Many Duplicates
There is no general one-click button that combines two HubSpot accounts into one. In most cases the route is to choose a destination portal, export records from the source portal, and import them into the destination, either by hand, with a migration app or with a partner. Check with HubSpot about the options for your subscription before you plan.
When those records arrive, HubSpot deduplicates the import on a small number of fields. Contacts are matched on email address and companies on domain (plus Record ID, which will not match across two different portals). Anything that does not match on those fields is created as a new record.
That is fine for the overlap that shares a clean work email. It is not fine for everything else, and two portals that grew separately have plenty of everything else:
- The same person stored with a work email in one portal and a personal email in the other
- A contact with an email address in portal A and only a LinkedIn URL in portal B
- Companies with no domain, or with different domains (a regional site, an old brand) for the same business
- Name variations: "Jon Smith" and "Jonathan Smith" at the same company
- Deals, which have no natural unique identifier, so imported deals are created as new
On top of that, each portal already has its own duplicates. Merge two portals without cleaning them and you inherit both sets, plus the cross-portal ones.
Step 1: Clean Each Portal on Its Own First
Start with the problems you already have. Deduplicate contacts and companies inside the source portal and inside the destination portal before you move anything. Every duplicate removed now is one fewer record to reconcile later.
The native tools will catch exact matches. For the partial ones, see how to find and merge duplicate contacts in HubSpot and how to deduplicate HubSpot companies and deals.
Step 2: Decide What Not to Migrate
A merge is the cheapest moment you will ever have to leave data behind. Before exporting, agree which records are not worth bringing:
- Contacts with no email, phone or LinkedIn URL and no activity in the period you choose
- Hard-bounced and long-unsubscribed contacts you have no reason to keep
- Records past your data retention period
- Test records, internal staff and old partner lists
Anything left behind does not need deduplicating, mapping or storing. It also reduces your GDPR exposure, which matters if either portal holds EU contacts. Our RevOps guide to CRM data governance covers how to set retention rules you can defend.
Step 3: Find Cross-Portal Duplicates Before the Import
This is the step that decides whether the merged portal is clean. You need to know, before importing, which records in the source portal already exist in the destination under a different email, without an email, or under a slightly different name.
Doing this in a spreadsheet works for a few hundred records. Beyond that, a manual VLOOKUP on email simply reproduces HubSpot's own logic and misses the same pairs. The comparison has to cover more than one field.
Step 4: Standardise Before You Map
Two portals rarely use the same conventions. Lifecycle stages, lead status values, country names, job titles and owner names will differ. Agree the destination's version of each, convert the source data to match, and only then map properties. Mapping first and standardising later means cleaning the same field twice.
Step 5: Import in Order and Rebuild Associations
Import companies first, then contacts, then deals, then engagements, so each object has something to associate with when it arrives. Keep the source portal's Record IDs in a custom property on every imported record. If something goes wrong, that ID is how you trace a record back.
Then check associations. A contact without its company, or a deal without its contacts, is the most common quiet failure in a portal merge. For a wider checklist, see how to clean your CRM data before a HubSpot or Pipedrive migration.
Step 6: Run a Final Duplicate Check After the Merge
However careful the preparation, check again once everything is in. A post-import scan catches the duplicates created by the import itself and gives you a baseline data quality score for the new combined portal.
How EazyMatch AI Supports a Clean CRM Data Migration
The steps above depend on one capability HubSpot does not provide natively: matching on more than email and domain. That is what EazyMatch AI does.
For contacts it compares email address, similar names within the same company, partial name matches, LinkedIn URL and mobile number. For companies it compares LinkedIn company URL and website domain. So when portal A has "Sarah Chen" with an email and no LinkedIn URL, and portal B has "Sarah Chen" with a LinkedIn URL and no email, EazyMatch AI flags them as the same person. HubSpot's import would create her twice.
The same scan flags missing data, scores data quality, standardises job titles and checks records against your retention rules, which covers steps 1, 2, 4 and 6 in one place. And no change happens on its own:
- Connect your HubSpot portal
- Run the checks
- Review each suggested merge and update, with the matching fields shown
- Approve what should change. Only approved changes sync back to HubSpot.
Try EazyMatch AI free →
Clean both portals before the merge and check the result after it.
FAQ
Q: Can I merge two HubSpot portals directly?
A: In most cases there is no self-serve option to combine two portals. The common approach is to export from one and import into the other, or to use a migration partner or app. Confirm the options for your subscription with HubSpot.
Q: Will HubSpot deduplicate contacts when I import from another portal?
A: It matches contacts on email and companies on domain. Records that share neither, including people stored with different emails or without an email, are created as new records.
Q: Should I clean data before or after a portal merge?
A: Both. Clean each portal before the merge so you do not migrate existing duplicates, and run a final check afterwards to catch anything the import created.
One Portal, One Version of Each Record
The reason to merge portals is to get one view of every customer. A merge that doubles your contacts gives you the opposite. A clean CRM data migration means removing duplicates inside each portal, leaving behind what you do not need, matching across portals on more than email, and checking again once the import is done.
Planning a portal merge and want a second opinion on the approach?
