Skip to content
Book a build

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.

On this page

What HubSpot supports natively

Franchise setups combine general HubSpot features:

FeatureWhat it gives a franchiseRequirement
TeamsGroup users by location; team-only record access; team-based reportsProfessional or Enterprise; nested teams need Enterprise
Asset access limitsRestrict some assets to specific users and teamsVaries by asset; Super Admins still see restricted assets
BrandsSeparate domains, emails, forms and subscription types per brand in one accountMarketing Hub Enterprise plus one add-on per brand
Multi-account managementConnect separate location 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

How franchises should set up HubSpot

QuestionOne shared portalA portal per location
Who owns the customer?Head officeThe franchisee
Shared marketing database?YesEach location has its own
Local autonomy over settings?LimitedFull
Network-wide reportingNative, in one accountMulti-account reports or a warehouse
Cost structureOne subscription, more seatsOne subscription per location
Franchisee leavesRemove users and reassign recordsHand 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, and the full design in the multi-location guide.

Where Jetstack AI fits

Jetstack AI builds the baseline once with Projects, 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 and property mapping.

Sources

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

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

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.