---
title: "One HubSpot portal or several for company divisions"
description: "Whether a company with several divisions should use one HubSpot portal or several: what each option supports natively, a decision table and the costly mistakes."
url: "https://jetstack.ai/answers/one-hubspot-portal-or-several-divisions/"
---

# One company, several divisions: one HubSpot portal or several?

A company with several divisions usually belongs in one HubSpot portal when the divisions share customers, reporting or a sales team, using teams, permissions and Brands to separate them. Several portals make sense when divisions sell to different customers, need different settings or may be sold. Pick the HubSpot portal setup for company divisions by how data must be shared; tooling comes second.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 29, 2026

On this page

## What HubSpot supports natively for divisions

**In one portal:**

| Feature             | Use for divisions                                                   | Requirement                                        |
| ------------------- | ------------------------------------------------------------------- | -------------------------------------------------- |
| Teams               | One team per division; team-only record access; division reports    | Professional or Enterprise                         |
| Nested teams        | Division > region > team, with parents seeing everything below      | Enterprise                                         |
| Asset access limits | Keep some assets visible only to a division’s users and teams       | Varies by asset; Super Admins still see them       |
| Brands              | Separate domains, emails, forms and subscription types per division | Marketing Hub Enterprise plus one add-on per brand |

**Across several portals:**

| Feature                  | Use for divisions                                                                                                                                                   | Requirement                                                                                                       |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Multi-account management | Connect division portals; mirror contacts and companies (read-only in the destination); copy automated emails, lists and forms; multi-account workflows and reports | Enterprise main account; up to 29 connected Professional or Enterprise accounts; same data location for reporting |
| Account switching        | One login for every portal a user belongs to                                                                                                                        | The user is added to each portal                                                                                  |

## One HubSpot portal or several: how to decide

| Question                                       | One portal | Several portals                       |
| ---------------------------------------------- | ---------- | ------------------------------------- |
| Do divisions sell to the same customers?       | Yes        | No                                    |
| Do they share a sales or service team?         | Yes        | No                                    |
| Same lifecycle stages and pipelines?           | Mostly     | Different                             |
| One revenue view needed daily?                 | Yes        | Occasional, via multi-account reports |
| Might a division be sold or spun off?          | Unlikely   | Likely                                |
| Separate legal, consent or data-hosting needs? | No         | Yes; get specialist advice            |

If most answers fall in the first column, use one portal and design teams and permissions carefully. If several fall in the second, use separate portals and plan how you’ll keep shared definitions consistent.

## Common mistakes

- **Splitting early** for tidiness, then needing cross-division reports every week.
- **One portal without partitioning,** so every user sees every division’s records and workflows.
- **Assuming a location or division property controls access.** It classifies records; permissions control access.

## Where Jetstack AI fits

For one portal, Jetstack AI [Projects](https://jetstack.ai/build), currently in limited release, builds the agreed division properties, pipelines and routing workflows from a brief, with the plan and the deployment approved separately and a receipt read back from HubSpot; teams and users stay a manual step. For separate division portals, build the shared setup once with a Project, then Jetstack’s [Portal reuse](https://jetstack.ai/roll-out) deploys it to the destination portal you choose, matching assets that already exist and remapping references. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See [Jetstack for in-house teams](https://jetstack.ai/in-house) and [how deployment works](https://jetstack.ai/docs/implementations/deploying/how-it-works).

## Sources

- [Create and manage teams (HubSpot Knowledge Base)](https://knowledge.hubspot.com/user-management/create-and-manage-teams)
- [Limit access to your HubSpot assets (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-security/limit-access-to-your-hubspot-assets)
- [Set up multi-account management (HubSpot Knowledge Base)](https://knowledge.hubspot.com/account-management/set-up-multi-account-management)
- [Manage your brands with HubSpot Brands (HubSpot Knowledge Base)](https://knowledge.hubspot.com/branding/manage-your-brands-with-hubspot-brands)

Checked October 29, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

Multiple portals & franchises

## Run your own portal like a delivery team.

Audit your own portal, scope the change and ship it with approvals and a record of what changed.

[See how in-house teams use Jetstack](https://jetstack.ai/in-house)

On this page

Multiple portals & franchises

## Related questions.

One company, several divisions: one HubSpot portal or several?

A company with several divisions usually belongs in one HubSpot portal when the divisions share customers, reporting or a sales team, using teams, permissions and Brands to separate them. Several portals make sense when divisions sell to different customers, need different settings or may be sold. Pick the HubSpot portal setup for company divisions by how data must be shared; tooling comes second.

Can we start in one portal and split later?

You can, but splitting means recreating configuration in the new portal and migrating records, and HubSpot has no built-in split. If a division is likely to be sold, start it in its own portal.

Can we merge separate portals later?

Consolidating portals is a migration project: configuration, records and history all need a plan. It is easier to choose deliberately up front.

Do divisions in one portal need Enterprise?

Not always. Teams and team-based record access work on Professional. Nested teams, Brands and restricting some assets and properties by team need Enterprise subscriptions.
