One CRM, many brands.

Regional groups rarely start with one CRM. They acquire a brand here, launch a market there, and each arrives with its own tools. Years later, the group has five CRMs, three definitions of a customer and no clear picture of who buys from it.

The question we hear most from group CIOs and CMOs is whether all of this can live in one HubSpot account without the brands tripping over each other. Usually it can. The design decisions decide whether it works.

One account or several?

Start from the customer, not the org chart. If the same people or companies buy from more than one brand, one account is almost always right: you see the full relationship, avoid duplicate outreach and can build cross-brand journeys. If brands genuinely share no customers, no data and no teams, separate accounts can be simpler.

Most groups we meet sit firmly in the first camp. Their customers do not care about internal structure. They notice when three brands from the same group email them on the same day.

How does HubSpot separate brands in one account?

HubSpot's Brands feature lets users with Marketing Hub Enterprise and the Brands add-on manage multiple brands in one account. HubSpot says each add-on allows one brand, up to 100 brands (HubSpot Knowledge Base).

Assets such as pages, domains, workflows, social accounts, quote templates, invoices and custom properties can be associated with a brand and reassigned later. One detail catches teams out: HubSpot notes that “campaigns, emails, and forms can only be associated with Brands when created” and cannot be reassigned afterwards (HubSpot Knowledge Base). Set up brands before marketing teams start building, not after.

Who should see what?

Brand separation is about marketing assets. Access separation is about people. HubSpot lets you limit access to assets by team and user. Some controls are available on all accounts, some need Professional, and others, including dashboards, reports, properties, campaigns and emails, need Enterprise (HubSpot Knowledge Base). Super Admins can still see everything.

We design teams to mirror how the group actually runs:

• Group level for leadership, RevOps and shared services, with full visibility.
• Brand level for marketing and sales teams that own a brand.
• Market level inside each brand, where local teams own local pipeline.

Then decide, record by record, what is shared. Companies and contacts are usually shared. Deals and tickets are often visible to the owning brand and to group leadership only.

How do you handle markets, currencies and languages?

Regional groups sell in several currencies. HubSpot supports multiple currencies on Starter, Professional and Enterprise, with exchange rates set against a company currency, and updates rates on open deals automatically (HubSpot Knowledge Base). Group reporting in one currency then becomes a configuration task, not a monthly spreadsheet.

Languages matter for service. HubSpot supports knowledge base articles in multiple languages, organised into language groups, on Service Hub Professional or Enterprise (HubSpot Knowledge Base). That same content becomes what an AI agent draws on, so getting it right serves people and agents at once.

What should be standard, and what local?

This is the decision that makes or breaks the design. Our rule: standardise anything the group needs to compare, and localise only what the market genuinely needs.

• Standard: the definition of a lead, lifecycle stages, deal stage meanings, service categories, core company and contact properties, and the company hierarchy.
• Local: language, currency, tax and regulatory fields, product ranges, and market-specific steps inside a pipeline.
• Brand-specific: marketing assets, domains, templates and brand voice.

Where a brand's process is truly different, use a separate pipeline rather than bending a shared one. Where a business sells something the standard objects do not describe well, such as units, projects or policies, HubSpot's custom objects can model it; they require an Enterprise subscription (HubSpot Knowledge Base).

How should group reporting work?

Design reporting in two layers. Brand dashboards answer the brand leader's questions: pipeline, conversion, campaign return. Group dashboards answer the board's: total pipeline, revenue per customer across brands, cross-sell, and service performance by market.

The group layer only works if the standard definitions hold. If one brand calls a lead what another calls an opportunity, the group number is fiction. This is why the shared model comes first and the dashboards second.

How do AI agents fit a multi-brand account?

Agents raise the stakes on brand design. An agent answering for one brand must use that brand's voice, products and policies, and must not borrow another brand's offer. That means knowledge content organised by brand and language, clear rules on which brand each channel serves, and a named owner per brand for each agent in Agent Hub.

The upside is real. A group with one customer record can let an agent recognise that the person asking a service question is also a customer of a sister brand, and hand that context to the right team. Separate accounts can never do that.

Where to start

Map the brands, markets and customers that overlap. Agree the shared model, and review data protection where brands operate in different countries; our data protection answer covers the main laws. Set up brands and teams. Then migrate one brand at a time, using the approach in our legacy CRM migration playbook.