Many growing organizations are not really one company. They are a parent business with two or three related brands, a sister company that shares some staff, or a separate business line that serves a different audience. When those organizations move to HubSpot, one of the first questions they ask is simple: should everything live in one HubSpot account, or does each brand need its own?
The answer affects almost everything that follows: who can see which records, which domain your emails come from, how unsubscribes work, how much administration you take on, and whether leadership can get a single view of the pipeline.
This guide walks through the three ways to run multiple brands or entities in HubSpot, how to choose between them, and the questions to settle before you import a single contact.
Most multi-brand organizations can run in one HubSpot account by using teams and permissions to control record visibility and, where marketing needs are distinct, the Brands add-on for Marketing Hub Enterprise to give each brand its own domain, tracking code, subscription settings, and assets. Separate HubSpot accounts make sense when entities need a hard wall between their data for legal, regulatory, or contractual reasons, or when they operate so independently that sharing settings would cause more friction than it saves. Enterprise customers can connect separate accounts with multi-account management to mirror data, copy assets, and report across them. Vantage Point helps organizations make this decision before implementation, when it is still cheap to change.
"Multiple brands" covers several different situations, and the right HubSpot setup depends on which one you are in. Before comparing options, describe your organization honestly:
The first situation almost always fits in one account. The last one almost always needs more than one. Most organizations sit somewhere in between, which is why the decision deserves a real conversation instead of a default.
HubSpot teams group users, and permissions can limit users to records owned by their team. With Professional or Enterprise subscriptions, you can assign users to teams and restrict what they see. Enterprise adds nested teams, which let you build a hierarchy (for example, a parent team for leadership with a team under it for each brand), and permission sets that make access easier to manage at scale.
This model works well when the goal is keeping sales teams focused on their own records, while leadership sees everything. It does not give each brand its own marketing identity.
HubSpot's Brands add-on is available to Marketing Hub Enterprise customers. Each add-on adds one brand, up to 100 brands, and comes with one additional brand domain. Each brand gets its own tracking code, so you can show different cookie banners on different sites. You can associate assets such as forms and pages with a brand, customize subscription pages per brand, and import opt-out lists for a specific brand. A Brands contact property lets you filter contacts by brand and set it automatically when someone submits a brand's form.
One detail matters a lot: when a contact opts out of all subscription types, that opt-out applies only to the brand in which it happened. That is usually what brands want, but it must be understood and documented.
Multi-account management lets businesses keep separate HubSpot accounts while still sharing some data and assets. The main account needs an Enterprise subscription, and it can connect up to 29 additional accounts on Professional or Enterprise subscriptions. Connected accounts can mirror data (so a salesperson in one account can see that a contact bought from another entity), copy marketing emails, lists, and forms, run workflows that create or update contacts in another account, and build reports across accounts. Cross-account reporting requires the accounts to have their data hosted in the same location, and the feature can't be set up in sandbox accounts.
| Question | One account + teams | One account + Brands | Separate accounts + multi-account management |
|---|---|---|---|
| Separate record visibility | Yes, through permissions | Yes, combined with teams and permissions | Yes, by default; shared only by choice |
| Separate domain, tracking code, and subscription pages | No | Yes, per brand | Yes, per account |
| Single pipeline view for leadership | Native | Native | Through multi-account reporting |
| Hard data wall between entities | No; relies on configuration | No; relies on configuration | Yes |
| Administration effort | Lowest | Moderate | Highest; settings, users, and properties per account |
| Best fit | One company, several sales teams | One company, several market-facing brands | Independent or regulated entities |
One account is usually right when the brands share more than they keep apart. Signs you are in that situation:
In this model, separate deal pipelines per brand, a brand property on contacts and deals, and team-based permissions do most of the work. If each brand also runs its own marketing, the Brands add-on adds separate domains, tracking, and subscription management without splitting the database.
Separate accounts are the safer choice when a mistake in permissions would be a real problem, not just an inconvenience. Consider separate accounts when:
Separate accounts do cost more administration. Every property, workflow, and integration has to be maintained in each account, which is why many organizations only split the entities that truly require it and keep the rest together.
Email is where multi-brand setups most often go wrong, because the recipient experience is what people notice. Settle these points before the first campaign:
Bring these questions to the first design session. The answers usually make the decision obvious:
Also think about how you'll structure company records. Our guide to modeling multi-location companies in your CRM covers parent-child relationships that often come up in the same conversation.
Start with a short design exercise before you configure anything. Map your entities, list who needs to see what, and note any separation that must be provable. Then choose the lightest model that meets those needs: one account with teams if the brands mostly share people and customers, the Brands add-on if each brand needs its own market presence, and separate connected accounts only where a hard wall is required.
Once the model is set, launch with the basics: contact imports with clean brand values, lifecycle stages, a pipeline per brand or entity, core workflows, and email sending set up per brand. Advanced automation can come after the foundation is stable.
Vantage Point helps organizations design HubSpot around how their businesses actually relate to each other. Our HubSpot implementation services cover account architecture, permissions, brands, pipelines, and email setup, and our compliance and security solutions team helps when entities need information barriers or review steps. We've completed 400+ engagements for 150+ clients, with a 4.71/5.0 average engagement rating and 95% client retention. Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver.
Get the account structure right before you import a single contact. Vantage Point can map your entities, recommend the right model, and build a setup your teams can grow into. Talk to Vantage Point about your multi-brand HubSpot setup.
Yes. Many organizations run several brands in one HubSpot account by using teams and permissions to control record access and, with Marketing Hub Enterprise, the Brands add-on to give each brand its own domain, tracking code, subscription pages, and assets.
It is an add-on for Marketing Hub Enterprise that lets you manage multiple brands in one account. Each add-on provides one brand and one additional brand domain, and you can add up to 100 brands.
Team-based permissions can limit users to records owned by their team, which keeps day-to-day work separate. They are still configuration that admins can change, so they are not a substitute for separate accounts when separation must be provable.
It is an Enterprise feature that connects separate HubSpot accounts in one organization. Connected accounts can mirror data, copy marketing assets, run cross-account workflows, and build reports that combine data across accounts.
The main Enterprise account can connect up to 29 additional accounts, and each connected account must have a Professional or Enterprise subscription for at least one product.
With the Brands add-on, an opt-out of all subscription types applies only to the brand where the contact opted out. Each brand should have its own subscription types so contacts can manage preferences brand by brand.
Yes, in most cases. A separate authenticated sending domain per brand helps recipients recognize the sender and keeps one brand's sending reputation from affecting another's.