On this page
What HubSpot supports natively
| Building block | What it does | Limits |
|---|---|---|
| Company records | One record per business, with its contacts and deals associated | Imports and forms match on the primary domain and manual entry warns on it; API-created companies aren’t matched that way |
| Parent and child companies | Default labels for how two companies relate | A parent can have many children; a child has one parent; no shared activity |
| Custom objects | A “Location” or “Site” object with its own properties and associations | Enterprise subscription; account access permissions to create |
| Association labels | Name the relationship, such as “Franchisee” or “Head office contact” | Plan the labels before importing |
| Teams | Group users by location for record access and reports | Professional or Enterprise |
When several locations share one domain. HubSpot deduplicates companies on the primary Company domain name, which matters when every franchisee uses the brand’s website:
- Imports match rows to existing companies by primary and secondary domain, so ten sites on one domain update one company. If you use a custom unique value property, such as a Location ID, as the import identifier, the file can include duplicate domains and each site gets its own company.
- Existing duplicates: if several companies already share a domain, an import that identifies by domain errors on that row and skips it. Once sites share a domain, identify them by Location ID or Record ID.
- Manual creation warns that a company with that domain already exists.
- API and installed third-party sync apps don’t deduplicate companies by domain, so an integration can create one company per site, or duplicates, depending on how it’s built.
How to structure franchise company records
| Model | Use when | Trade-off |
|---|---|---|
| Company per franchisee, location property on contacts and deals | Each franchisee runs one site | Simple; a multi-site owner needs a separate company or a multi-select value |
| Parent company (franchise group) with child companies (sites) | One owner runs several sites | Clear hierarchy; no shared timeline, so group reports need filters |
| Company per franchisee plus a Location custom object | Sites have their own data and many related records | Most flexible; Enterprise only, and more to maintain |
Then:
- Pick a stable location ID (a code, not a free-text name), create it as a company property that requires unique values (HubSpot only lets you set that when the property is created), and set a rule for unknown locations.
- Decide which object owns the location: contact, company, deal or the custom object. Use the one your routing and reports read.
- Create the properties and association labels first, then import.
- Import parents before children. HubSpot’s bulk import maps children to existing parents.
- Route and report on the ID, not the label, so renaming a site doesn’t break workflows.
Common mistakes
- Using the location property as an access control. It classifies records; permissions come from teams.
- Free-text location names that drift (“Leeds”, “Leeds City”).
- Importing before the parent companies exist.
Where Jetstack AI fits
Jetstack AI Projects can build the pieces of this structure in a portal: properties, custom objects and association labels, plus the lists and workflows that route on them. You review a plan, approve the build and the deployment separately, and get a receipt read back from HubSpot; workflows are created switched off, and Projects is currently in limited release. It doesn’t import the company records themselves. For a portal per location, Portal reuse brings the same structure into each location’s portal; you can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See what Projects can build and Jetstack for franchises.
Sources
- Add a parent or child company (HubSpot Knowledge Base)
- Deduplication of records (HubSpot Knowledge Base)
- Set up your import file (HubSpot Knowledge Base)
- Create custom objects (HubSpot Knowledge Base)
- Create and use association labels (HubSpot Knowledge Base)
- What Jetty can build (Jetstack AI documentation)
Checked October 30, 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