---
title: "Structuring franchise company records in HubSpot"
description: "How to structure franchise company records in HubSpot: company per franchisee, parent and child companies, or a custom location object, and when to use each."
url: "https://jetstack.ai/answers/franchise-company-records-hubspot/"
---

# How should a franchise structure company records in HubSpot?

Structure franchise company records in HubSpot around what you report on: usually one company record per franchisee business, a stable location property (or a custom object for each site on Enterprise), and associations to the contacts and deals at that site. Use parent and child company associations for franchise groups that own several locations. Keep location IDs stable so routing and reports don't break.

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

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

Updated October 30, 2026

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:

1. **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.
2. **Decide which object owns the location:** contact, company, deal or the custom object. Use the one your routing and reports read.
3. **Create the properties and association labels first,** then import.
4. **Import parents before children.** HubSpot’s bulk import maps children to existing parents.
5. **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](https://jetstack.ai/build) 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](https://jetstack.ai/docs/projects/capabilities) and [Jetstack for franchises](https://jetstack.ai/franchise).

## Sources

- [Add a parent or child company (HubSpot Knowledge Base)](https://knowledge.hubspot.com/records/add-a-parent-or-child-company)
- [Deduplication of records (HubSpot Knowledge Base)](https://knowledge.hubspot.com/records/deduplication-of-records)
- [Set up your import file (HubSpot Knowledge Base)](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
- [Create custom objects (HubSpot Knowledge Base)](https://knowledge.hubspot.com/object-settings/create-custom-objects)
- [Create and use association labels (HubSpot Knowledge Base)](https://knowledge.hubspot.com/object-settings/create-and-use-association-labels)
- [What Jetty can build (Jetstack AI documentation)](https://jetstack.ai/docs/projects/capabilities)

Checked October 30, 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 a franchise structure company records in HubSpot?

Structure franchise company records in HubSpot around what you report on: usually one company record per franchisee business, a stable location property (or a custom object for each site on Enterprise), and associations to the contacts and deals at that site. Use parent and child company associations for franchise groups that own several locations. Keep location IDs stable so routing and reports don't break.

Do parent and child companies share activity?

No. HubSpot's parent and child labels describe the relationship, but they don't share activities or data between the records. Report on the group with filters or rollups instead.

Should the location be a property or a custom object?

A property is enough when each record belongs to one location and you only need to filter and route. Use a custom object (Enterprise) when locations have their own data, such as opening hours, managers or territories, and relate to many records.

Can a child company have two parents?

No. In HubSpot a parent company can have several children, but a child company can have only one parent.
