---
title: "HubSpot for franchises and multi-location businesses"
description: "HubSpot for franchises: one portal with teams and a location field, or a portal per location with a shared baseline. What HubSpot supports and how to choose."
url: "https://jetstack.ai/answers/hubspot-for-franchises/"
---

# How should franchises and multi-location businesses set up HubSpot?

HubSpot for franchises takes one of two shapes: one portal with a location property, teams and permissions (plus Brands for separate brands), or a portal per location sharing one baseline. Choose by who owns the customer and the data. Jetstack AI builds that baseline once and deploys it to every location's portal, with each portal's mappings reviewed.

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

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

Updated November 5, 2026

On this page

## What HubSpot supports natively

Franchise setups combine general HubSpot features:

| Feature                  | What it gives a franchise                                                                                                                                                    | Requirement                                                                     |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| Teams                    | Group users by location; team-only record access; team-based reports                                                                                                         | Professional or Enterprise; nested teams need Enterprise                        |
| Asset access limits      | Restrict some assets to specific users and teams                                                                                                                             | Varies by asset; Super Admins still see restricted assets                       |
| Brands                   | Separate domains, emails, forms and subscription types per brand in one account                                                                                              | Marketing Hub Enterprise plus one add-on per brand                              |
| Multi-account management | Connect separate location 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 |

## How franchises should set up HubSpot

| Question                      | One shared portal                 | A portal per location                |
| ----------------------------- | --------------------------------- | ------------------------------------ |
| Who owns the customer?        | Head office                       | The franchisee                       |
| Shared marketing database?    | Yes                               | Each location has its own            |
| Local autonomy over settings? | Limited                           | Full                                 |
| Network-wide reporting        | Native, in one account            | Multi-account reports or a warehouse |
| Cost structure                | One subscription, more seats      | One subscription per location        |
| Franchisee leaves             | Remove users and reassign records | Hand over or close their portal      |

Whichever you pick, follow the same order:

1. **Agree the shared definitions:** lifecycle stages, enquiry types, pipeline stages and a stable location identifier.
2. **Decide what stays local:** owners, opening hours, sender details, local offers.
3. **Build the baseline once** and test it with one pilot location.
4. **Roll it out location by location,** mapping owners and pipelines in each.
5. **Keep a change register** so later updates don’t overwrite legitimate local changes.

How to model the franchisee businesses themselves is covered in [how a franchise should structure company records](https://jetstack.ai/answers/franchise-company-records-hubspot), and the full design in the [multi-location guide](https://jetstack.ai/guides/multi-location-hubspot).

## Where Jetstack AI fits

Jetstack AI builds the baseline once with [Projects](https://jetstack.ai/build), currently in limited release: you describe the shared properties, pipelines and workflows in a brief, approve the plan and then the deployment, and get a receipt read back from HubSpot. Portal reuse then brings that baseline into each location’s portal, matching existing assets and remapping owners, pipelines and properties. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. Each deployment is a separate, reviewed copy; there is no automatic enforcement across the network. You can roll back a Portal reuse deployment: Jetstack shows you what will be removed first, then deletes the assets that deployment created in the destination portal. It won’t delete anything another deployment or Project still uses, and it skips assets that were changed after the deployment. See [Jetstack for franchises](https://jetstack.ai/franchise) and [property mapping](https://jetstack.ai/docs/implementations/deploying/property-mapping).

## Sources

- [Create and manage teams (HubSpot Knowledge Base)](https://knowledge.hubspot.com/user-management/create-and-manage-teams)
- [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)
- [Property mapping during deployment (Jetstack AI documentation)](https://jetstack.ai/docs/implementations/deploying/property-mapping)

Checked November 5, 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

## One standard, adapted for each location.

Build the standard setup once, then adapt and deploy it to each location portal.

[See the franchise workflow](https://jetstack.ai/franchise)

On this page

Multiple portals & franchises

## Related questions.

How should franchises and multi-location businesses set up HubSpot?

HubSpot for franchises takes one of two shapes: one portal with a location property, teams and permissions (plus Brands for separate brands), or a portal per location sharing one baseline. Choose by who owns the customer and the data. Jetstack AI builds that baseline once and deploys it to every location's portal, with each portal's mappings reviewed.

Can franchisees only see their own records in one portal?

You can get close with teams: on Professional and Enterprise, users with team-only permissions see records owned by their team. Test it with real users, and remember Super Admins see everything.

Can head office report across franchisee portals?

With multi-account management, an Enterprise account can build reports that combine data from connected accounts, as long as all of them host their data in the same location.

Who should own the portal?

Decide this before setup. If a franchisee leaves the network, a separate portal is easier to hand over; a shared portal keeps the customer data with head office.
