Skip to content
Book a build

Designing HubSpot for multiple locations

Choose a portal boundary, define a shared schema and preserve local decisions when reusing configuration across locations.

Jetstack AI / Working guides

The location model

Standardise deliberately

Location overlay
Shared definitionservice_locationStable values + eligibility rules
North regionLocal overlayOwner mapping
Fallback decision
Example SouthLocal overlayOwner mapping
Fallback decision

Review each destination independently

On this page

“One portal or one per location?” is an operating-model question before it is a tooling question. Shared reporting, separate ownership, consent practices and local autonomy can pull in different directions. Reusing configuration is easier to reason about after those boundaries are agreed.

This guide is a design checklist, not a claim about franchise customer results. The location names and schema below are illustrative. Validate HubSpot plan requirements, team permissions, business-unit features and object availability in the actual accounts before committing to an architecture.

1. Decide what must be shared

Write down which processes need a common definition: enquiry qualification, lifecycle stages, location assignment, pipeline stages or reporting categories. Then write down what must remain local: routing owners, operating hours, sender details, regional content and escalation contacts.

Ask who can change each definition. A central team may own a common property contract while a local team owns its assignment rules. If both can edit the same thing, define how a disagreement is resolved. Copying the configuration cannot settle governance that has not been agreed.

2. Choose the portal boundary deliberately

A shared portal can make common definitions easier to manage, but access, segmentation and reporting need careful design. Separate portals provide distinct operating spaces while adding repeated configuration and cross-portal reporting considerations. Neither option automatically delivers isolation, compliance or a complete central view.

Design questionWhat to establish
Who owns the customer relationship?Shared account ownership or distinct local organisations
Who can view and edit records?Actual HubSpot permission behaviour, not a diagram alone
Which reports must be comparable?Common definitions, time periods and source data
Which messages may each location send?Local sender, consent and subscription requirements
Who approves shared changes?Named central and local decision owners

Confirm the relevant permissions with representative users. A location property is a classification field; it should not be presented as an access-control boundary. Get specialist advice for legal or regulatory requirements instead of assuming a portal arrangement meets them.

3. Define a stable location schema

Choose a stable internal identifier and a policy for missing or unknown locations. Do not use free-text labels as the only routing key if labels may change. Decide whether the location belongs to the contact, company, deal or another appropriate object based on the process you need to represent.

The following illustrative schema is a planning example, not an automatically generated architecture:

contact:
service_location:
type: enumeration
values: [north_branch, south_branch, unassigned]
shared_rule: Route only when eligibility and location are resolved
local_overlay:
north_branch:
owner: A reviewed destination owner
fallback: A named local review queue
south_branch:
owner: A separately reviewed destination owner
fallback: A named local review queue

Check records that legitimately interact with more than one location. A single field may be insufficient for a process that needs multiple concurrent relationships. Do not introduce a custom object solely to make a diagram elegant; verify subscription availability, reporting needs and operational maintenance first.

4. Separate the baseline from local overlays

Document the reusable baseline in ordinary language: internal property names, option meanings, required lists and the intended workflow structure. Keep local owner mappings, pipeline identifiers, message content and activation choices in a destination-specific review record.

For example, the same routing pattern may be reusable while the destination’s owner and pipeline stages differ. An existing asset might be a suitable match, or it might share only a label. Review definitions before choosing reuse. A changed local rule is an exception to inspect, not necessarily an error to overwrite.

5. Roll out to one location or many

Portal reuse can remap IDs and references and match destination assets. Treat each destination as its own deployment: confirm the portal, inspect available features and permissions, approve mappings, deploy, then verify. It is not a bulk push to every location and it is not a promise of ongoing automatic synchronisation.

Follow dependencies before consumers. A shared list definition may require the destination property options to exist first; its workflow may then need a destination-specific owner. Do not approve a consumer while its prerequisite mapping is unresolved. The pipeline mapping documentation describes the corresponding product step.

6. Verify locally and maintain a change register

Inspect references in the destination, then test authorised scenarios for the local process. Include a resolved location, a missing location and an exclusion such as an existing owner. Confirm that messages and assignments reach the intended local team before enabling live behaviour.

Keep a baseline description, the destination decisions, the execution record and the acceptance owner together. When the central model changes, compare that proposal with the local record instead of treating a fresh copy as an upgrade. Choose whether to update, retain an exception or investigate a conflict. Review that decision again for the next portal.

Location rollout review

A reading checklist. Selections stay on this page only and are not saved.

Further reading

Use the copying guide for the dependency and mapping sequence. Read the multi-account configuration article for related context, and explore Portal reuse for destination-specific deployment.

The implementation workflow

Standardise deliberately.

A shared schema with local decisions kept visible.

Explore Portal reuse