Skip to content
Book a build

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.

On this page

What HubSpot supports natively for divisions

In one portal:

FeatureUse for divisionsRequirement
TeamsOne team per division; team-only record access; division reportsProfessional or Enterprise
Nested teamsDivision > region > team, with parents seeing everything belowEnterprise
Asset access limitsKeep some assets visible only to a division’s users and teamsVaries by asset; Super Admins still see them
BrandsSeparate domains, emails, forms and subscription types per divisionMarketing Hub Enterprise plus one add-on per brand

Across several portals:

FeatureUse for divisionsRequirement
Multi-account managementConnect division portals; mirror contacts and companies (read-only in the destination); copy automated emails, lists and forms; multi-account workflows and reportsEnterprise main account; up to 29 connected Professional or Enterprise accounts; same data location for reporting
Account switchingOne login for every portal a user belongs toThe user is added to each portal

One HubSpot portal or several: how to decide

QuestionOne portalSeveral portals
Do divisions sell to the same customers?YesNo
Do they share a sales or service team?YesNo
Same lifecycle stages and pipelines?MostlyDifferent
One revenue view needed daily?YesOccasional, via multi-account reports
Might a division be sold or spun off?UnlikelyLikely
Separate legal, consent or data-hosting needs?NoYes; 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, 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 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 and how deployment works.

Sources

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

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

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.