SaaS mode loads your snapshot into every self-serve signup with nobody there to configure it. Here is what that changes about the snapshot, the onboarding and the rebilling.
Missing Load Snapshot option, failed assets, duplicate workflows, broken trigger links and dashboards that arrive empty — the real causes, in the order worth checking them.
Custom fields store data about a contact. Custom values store facts about the business. Getting the distinction right is what lets one snapshot serve forty sub-accounts.
Brand then campaign, in that order. What each form actually wants, how long approval takes, the exact-match rule that fails most brands, and what to do when a campaign is rejected.
Login domain, dashboard, notification emails, mobile app, support links. What white-labelling covers at sub-account level, what it does not, and the setup order that avoids client questions.
The sub-account transfer flow, the relationship number, the exclusions nobody mentions, and the pre-transfer audit that stops a client losing their phone number mid-move.
Interface, API, or SaaS mode auto-provisioning. What each mechanism can and cannot do, where the real bottleneck sits, and how to roll out fifty accounts without fifty afternoons.
The plan fee is the smallest number. Here is the full cost of running one GHL sub-account — telephony, email, compliance, AI usage and build time — with the arithmetic shown.
Creating a GHL sub-account takes two minutes. Making it ready for a snapshot takes twelve settings. Here is the create-then-configure order that stops rework later.
Free GHL snapshots are real and some are good. Here is how to tell a starter demo from a working kit, the four questions to ask before loading one, and when free is the right call.
A GoHighLevel sub-account is one client's isolated CRM inside your agency account. Here is what is isolated, what is shared, where the ID lives and what that means operationally.
A step-by-step method for loading a GoHighLevel snapshot into a sub-account: pre-load conflict checks, publishing order, re-pointing trigger links and the test pass most installs skip.
Most GHL snapshots are a pile of workflows. A good one has a custom-value layer, a naming convention, real exit conditions and a load sheet. Here is how to tell them apart before you buy.
A practical naming convention for GHL workflows, pipelines, tags, calendars and custom values — the change that makes a sub-account maintainable by someone who did not build it.
Snapshots, templates and cloned sub-accounts solve different problems in GoHighLevel. Here is what each one carries, what it leaves behind, and when to use which.
The operational changes that make ten GHL sub-account builds in a month possible: one kit, one intake, batched builds, a load sheet and a hard rule about customisation.
A pre-launch checklist for a GHL sub-account: numbers, sending domain, custom values, calendar availability, workflow publishing order, test pass and handover documentation.
6 min read
Stop reading, start loading
The catalogue is more useful than the archive
Every guide here describes work that a kit already does. Twenty-two of them, one per niche.
Nothing matched “”. Try a kit name, a GoHighLevel feature, orask us directly.
Accessibility
Text size
Display
Turning animation off tears down the WebGL grid and the particle field — they stop running, they are not just hidden.
We keep cookies to a minimum
Only the essentials run by default — your theme, palette and accessibility settings, stored in this browser. Nothing analytics-shaped loads unless you accept. See theprivacy policy.