A surprising number of businesses end up with two HubSpot portals. An old free CRM account created years ago sits next to a new paid portal; an acquisition brings a second portal into the fold; a well-meaning agency built a client's assets inside the wrong account. Sooner or later someone asks the obvious question: can we just merge them?
The short answer is no — HubSpot does not offer a native "merge two portals" button. But moving data from one HubSpot portal to another is absolutely doable, and teams that follow a structured sequence preserve their records, their associations, and their email subscription compliance along the way. The teams that skip steps discover months later that deal-to-contact associations were lost or that unsubscribed contacts started receiving marketing email again.
This guide explains what actually transfers between HubSpot portals, what has to be rebuilt, and the migration sequence that keeps the move clean.
Quick Answer
HubSpot cannot merge two portals, but you can migrate data between them. Contacts, companies, deals, tickets, and custom objects move via export/import using each record's Record ID to preserve associations. Automation, lists, forms, and content must be rebuilt or moved with migration tools. User permissions and billing are portal-specific, so a super admin on the paid portal must recreate access, and license consolidation is a separate conversation with HubSpot. Vantage Point runs portal-to-portal migrations as a structured project so nothing quietly breaks downstream.
Key Takeaways (TL;DR)
- No native merge: HubSpot has no portal-merge feature; migration is export/import plus rebuild.
- Record IDs preserve relationships: exporting with Record IDs and importing them back keeps contacts, companies, and deals associated.
- Subscriptions are a compliance issue: email opt-out status must be exported and re-imported, not assumed.
- Automation does not transfer: workflows, lists, forms, and sequences are rebuilt in the destination portal.
- Billing stays put: paid subscriptions belong to the portal that purchased them; consolidating licenses requires your HubSpot rep.
Why do businesses end up with two HubSpot portals?
The pattern is remarkably consistent. A free CRM account gets created for an early experiment and quietly accumulates years of companies and contacts. Later, the business signs up for a paid subscription — sometimes through a different email address, sometimes through a partner — and a second portal is born. In other cases, one portal holds the sales team's CRM while a legacy marketing portal holds the website and email history.
The result is predictable confusion: users log in and cannot see licensed features because their user account lives in the wrong portal, leadership sees two incomplete versions of the truth, and nobody is sure which portal is "real."
Can HubSpot merge two portals into one?
No. There is no native account-merge function. Each HubSpot portal is a separate account with its own subscription, users, data, and settings. "Merging" is really a migration project: pick the destination portal (almost always the paid one), move the data, rebuild the configuration, re-point anything public-facing, and retire the old portal.
That framing matters because it sets expectations. A portal consolidation is not a toggle — it is a mini-migration with the same disciplines as moving between any two CRM systems, just with friendlier tooling.
What transfers between portals — and how?
| Asset | How it moves | Watch out for |
|---|---|---|
| Contacts, companies, deals, tickets | Export with Record IDs, import into the destination portal with the same IDs | Record IDs are portal-specific — you import them into a custom "legacy ID" property, not HubSpot's own ID field |
| Record associations | Multi-object imports keyed on the legacy Record ID re-link contacts to companies and deals | Skipping association mapping is the most common way migrations quietly fail |
| Notes, calls, emails, meetings | Engagements export via API or reporting tools and re-import as activities | Timeline order and original timestamps need deliberate mapping |
| Email subscription status | Export opt-outs and subscription preferences; import them before any marketing send | Treating this as optional is a compliance risk, not a data nicety |
| Files and documents | Download from the files tool and re-upload | Public file URLs change — check for hard-coded links |
| Lists, workflows, forms, sequences | Rebuilt manually (or cloned where the tool allows cross-portal copying) | Budget real time here; it is usually the largest workstream |
| Website, landing pages, blog | HubSpot's content migration tooling or a marketplace migration app | Re-point domains and re-embed the tracking code after cutover |
| Users and permissions | Recreated by a super admin in the destination portal | Only a super admin can add users; confirm who holds that role first |
| Subscription and billing | Does not move — the license belongs to the portal that bought it | Consolidating contracts is a conversation with your HubSpot account manager |
What is the right sequence for a portal-to-portal migration?
- Confirm super admin access to both portals. This sounds basic and is the step that stalls real projects — users blocked from licensed features because nobody in the room is a super admin on the paid portal. Fix access before touching data.
- Decide the destination. Usually the paid portal, but confirm which portal owns the subscription, the sending domain, and the tracking code before committing.
- Export with Record IDs. Pull every object with its associations so relationships can be reconstructed downstream.
- Dedupe before importing. Two portals almost always contain the same customers. Merge duplicates in a spreadsheet or staging environment, not inside the live destination portal.
- Import in dependency order. Companies first, then contacts associated to them, then deals and tickets, then engagements — each pass keyed on the legacy Record ID.
- Re-import subscription status. Opt-outs and communication preferences go in before any marketing email is sent from the destination portal.
- Rebuild automation and assets. Workflows, lists, forms, sequences, and templates — rebuilt and tested with sample records.
- Re-point the public footprint. Sending domains, the tracking code, connected inboxes, and integrations move to the destination portal.
- Resolve licensing. Ask your HubSpot rep about consolidating contracts so the business pays once; this is a commercial step, not a technical one.
- Retire the old portal on a schedule. Keep it read-accessible for a defined window, then cancel deliberately with an export archived.
What breaks when teams skip steps?
The failures are quiet. Contacts import fine but their deals belong to no one. A marketing email goes out from the new portal to people who unsubscribed years ago in the old one. A sales rep's "recent activity" is empty because engagement history stayed behind. None of these produce an error message — they surface as lost trust, so the checklist above exists to catch them before users do.
What should businesses do next?
- Inventory both portals: objects, record counts, workflows, forms, connected tools, and who holds super admin rights.
- Name the destination portal and write down why.
- Run a pilot import of a few hundred records with associations before committing to the full load.
- Schedule the licensing conversation with HubSpot in parallel — it is often the slowest track.
- Set a retirement date for the old portal before the project starts.
How Vantage Point Helps
Vantage Point runs HubSpot portal consolidations as structured migrations: access audit, export mapping, association-preserving imports, subscription-status handling, and automation rebuilds. Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver. Our HubSpot technology team and HubSpot implementation service handle portal-to-portal moves alongside broader CRM migrations, and our system integration and data migration practice covers the exports, mappings, and validation that make the cutover boring.
Two HubSpot Portals, One Business?
A portal consolidation pays for itself the first time leadership trusts the pipeline report again. Talk to Vantage Point about your HubSpot portal migration.
Frequently Asked Questions
Can HubSpot merge two accounts into one portal?
No. HubSpot does not offer a native merge between portals. Consolidating two portals is a migration project: data is exported from one portal and imported into the other, automation is rebuilt, and billing is consolidated separately through your HubSpot account manager.
Will my contact and company associations survive a portal migration?
Yes, if you export records with their Record IDs and use multi-object imports keyed on those IDs. The associations are reconstructed during import. Skipping the ID mapping is the most common way associations are lost.
Does email subscription status transfer between HubSpot portals?
Not automatically. Opt-outs and subscription preferences must be exported from the old portal and imported into the new one before any marketing email is sent. Treating subscription status as optional creates a real compliance risk.
Who can add users to the destination portal?
Only a super admin can create users and assign permissions. Before starting a consolidation, confirm who holds super admin rights on the paid portal — users locked out of licensed features are often simply users who were never added to the right account.
Can I move my paid HubSpot subscription to the other portal?
Subscriptions belong to the portal that purchased them and do not move with the data. Consolidating or reassigning contracts is a commercial conversation with your HubSpot representative, handled in parallel with the technical migration.
How long does a portal-to-portal migration take?
For a straightforward CRM-only move, plan on a few weeks including testing; portals with websites, heavy automation, or many integrations take longer. The automation rebuild and licensing conversations usually take more calendar time than the data load itself.
