How to Set Up GoHighLevel for Multiple Locations and Brands

Run six branches out of one GoHighLevel account and every lead, pipeline and phone number ends up in the same pile. The fix is to treat GoHighLevel multiple locations as separate sub-accounts that all start from one tested template, so each branch stays tidy and you still manage the lot from a single agency login.
The steps below follow the order we'd work in, from the master build to the first update you push after launch. They apply whether the locations are branches of one company or separate brands under one owner.
How GoHighLevel multiple locations work as sub-accounts
Each location gets its own sub-account, and each sub-account keeps its own contact database, pipeline, phone numbers, messaging and automation workflows. That separation is what stops a lead for the Leeds branch showing up in the Manchester team's inbox.
The agency account sits above them and gives you oversight of every sub-account. Omni Online Strategies' multi-location guide, published in June 2026, describes exactly this structure and recommends it for businesses with several locations.
One sub-account per brand follows the same logic. Two brands rarely share customers, offers or phone numbers, so they shouldn't share a pipeline either. Getting GoHighLevel multiple locations right comes down to the build order and the maintenance afterwards.
Build one master sub-account first
Start with a single sub-account that isn't any real location. Put everything every branch will need in it: pipelines, workflows, templates, forms, calendars and custom fields. Then test it as if a customer were using it.
Every mistake you leave here gets copied to every location. Fixing a broken follow-up sequence once is easy, and fixing it in twelve live sub-accounts is not.
Keep the master generic. Leave out local phone numbers, addresses, staff names and opening hours, because those belong to individual branches and get added later.
Turn the master into a snapshot
A snapshot is a saved copy of a sub-account's setup that you can use to build others. From the agency account, create one from the master and name it with the business name and a version number, for example 'Acme Dental v1'. The version number saves you from guessing which template a branch was built from.
If you'd rather not build the master yourself, our GoHighLevel snapshot service covers it, and the same team can handle the wider GoHighLevel setup.
Create each location from the snapshot
The cleanest way to launch GoHighLevel multiple locations is to create each new sub-account directly from the snapshot rather than loading it afterwards. According to HighLevel's help article on creating a sub-account from a snapshot, you open Account Snapshots in the agency dashboard, click the blue Create New Account button beside the snapshot, fill in the details and click Add Sub-Account.
Because everything is applied at creation, nothing in the new account gets overwritten. Funnels and websites arrive as drafts and stay unpublished until you connect a custom domain and publish them.
You can pick only one snapshot at creation. If a location needs a second one, apply it by hand afterwards. And once a snapshot is applied you can't unload it, only remove or edit its parts one at a time, so check you've chosen the right version before you click.
Local details for GoHighLevel multiple locations
A copy of the master is still a copy. It becomes a branch when you add what is true only for that branch.
- Buy or connect a local phone number.
- Connect the location's Google Business Profile.
- Enter the address and opening hours.
- Staff the calendars with the people who work there.
- Check the reporting view compares the new branch with the others on lead volume, show rates and pipeline movement.
That list comes from the same Omni walkthrough, and it matches what we see go missing most. A branch that launches with the master's placeholder hours is a branch that books appointments nobody is there for.
Over 100 GHL accounts have been built and configured by our team, and the pattern is always the same: the template is quick, and the local details are where the time goes.
Loading a snapshot into locations that already exist

Photo by Vitaly Gariev on Pexels
Plenty of businesses start with a few sub-accounts and only later decide on a standard template. You can still apply one without opening each account.
In Agency View, go to My Account Snapshots and click Load Updates to Sub-Account next to the snapshot. HighLevel's help page on loading a snapshot into multiple sub-accounts says you can narrow the list with the All, Linked or Available tabs, tick the destination accounts and click Load. If the flow shows conflicts, you resolve them on screen before you confirm.
That page doesn't spell out what is overwritten in an account that already has its own setup. Try it on one quiet location first and read the conflict options before you load the rest.
Keep brands apart and locations consistent
For GoHighLevel multiple locations under one company, the branches should look the same, so they share one snapshot. Separate brands should each get their own master, because their pipelines, messages and offers differ.
It's tempting to cram two brands into one master with a lot of branching. We wouldn't. A master that tries to serve everyone is hard to test, and the first time someone edits a workflow for brand A, brand B's customers get the message.
Agencies reselling to several clients with several sites each can go a step further and keep one master per client. Our page for agency owners shows how we support that structure, including white-label support under your own name.
Pushing updates after launch
Once your GoHighLevel multiple locations are live, snapshot changes don't reach them on their own. The Omni guide says each change needs a manual update or a new snapshot redeployed, so it recommends changing the core system rarely and batching the changes.
HighLevel does give you a route that avoids rebuilding. HighLevel's help article on refreshing snapshots says to click the Refresh icon next to the snapshot, choose the assets to include, wait for the load, then click Push Update and pick the sub-accounts that imported it. The article describes pushes as selective and not destructive.
Even so, one detail deserves a warning. If a refresh removes a step from a workflow, such as a wait step, contacts waiting on that step are removed, and the Execution Logs record 'Removed by - Snapshot Refresh'. Before you push to live locations, find out which workflows have people sitting in them.
Push Update also only reaches sub-accounts inside your own agency.
Getting hands on the software before you commit
If you haven't built a sub-account before, rehearse on a throwaway one. The HighLevel 30 day Bootcamp trial is a low-risk place to build a master and practise creating a branch from it.
Our pricing page shows what it costs to have a team do the build and run it: plans for business owners start from $149 per month.
Frequently asked questions
Can I load a snapshot into several locations at once?
Yes. From My Account Snapshots in Agency View, use Load Updates to Sub-Account, tick the sub-accounts you want and click Load. Resolve any conflicts the flow shows before you confirm.
Do snapshot updates reach my existing locations automatically?
No. The snapshot has to be refreshed, and then you push the update to the sub-accounts that imported it. Changes made to the master alone don't appear in live locations.
Can I use more than one snapshot when I create a location?
No, creation accepts a single snapshot. Any others have to be applied manually afterwards.
Does every location need its own phone number?
Each sub-account keeps its own phone numbers, and a local number is one of the first things to add after the branch is created from the snapshot.
Sources
- How to set up GoHighLevel multi-location sub-accounts — Omni Online Strategies
- Create a New Sub-Account Using Snapshot — HighLevel Support
- Load Multiple Sub-Accounts to a Snapshot — HighLevel Support
- Refresh or Update Snapshots in HighLevel — HighLevel Support
Cover photo by Sora Shimazaki on Pexels
Need help implementing this in GoHighLevel?
Our team builds, automates, and scales GoHighLevel systems for agencies every day. Book a free call and we'll map out exactly what to ship next.
Book a free call