A GoHighLevel CRM Setup Guide That Starts With Structure

Where a GoHighLevel CRM setup guide actually begins

Every new location inside GoHighLevel begins as a sub-account: a separate workspace with its own contacts, pipelines and branding under your agency's parent account.

That distinction, agency account versus sub-account, is the first thing any GoHighLevel CRM setup guide has to get right, because nothing you configure next carries over automatically between the two.

When you create a sub-account, HighLevel asks which kind it is. Choose "This is my client's account" for a business you're onboarding, or "This is my own account" for your agency's internal workspace.

An agency sub-account gets a blue badge and handles things a client account doesn't, including SaaS subscriptions and rebilling. It also can't be transferred to another agency afterward, so get the type right at creation.

Pipelines and custom fields decide what the CRM remembers

A pipeline is the Kanban-style board that tracks a deal through named stages. Creating one takes a short form: open Opportunities, click Pipelines, hit "Create new pipeline," name it, and add stages.

Won and Lost stages appear automatically, so you don't build those yourself. Pipeline names have to stay unique inside a sub-account, and stage names unique within a pipeline, which matters once you're copying the same structure across several client accounts.

Custom fields work differently. They make the setup specific to the business rather than the platform, and you create them under Settings and Custom Fields.

The first decision, Contact or Opportunity, is permanent. HighLevel's own documentation is direct about this: a field's object cannot be switched after it's created. Get that wrong on a lead-source dropdown, and you're rebuilding the field, not editing it.

The available types cover:

• Single-line and multi-line text, for short entries and longer notes
• Numbers and monetary values, for budgets and deal size
• Dropdowns, radio buttons and checkboxes, for fixed choices
• Date pickers, file uploads and signatures, for anything with a timestamp or document attached

Once a field exists, it can feed forms, workflows, Smart Lists and reporting. Decide the object and the type before you build the form that depends on it.

Snapshots turn one setup into a repeatable template

If you're doing this more than once, a snapshot keeps the second client's build from starting at zero. It packages funnels, forms, workflows, calendars and settings into one file you apply to a new sub-account.

Creating a sub-account from a snapshot runs through the Agency Dashboard: open Account Snapshots, find the one you want, and click the blue "Create New Account" button beside it.

Funnels and websites copied in this way land as drafts. They won't go live until someone connects a custom domain and publishes them, so a snapshot shortens the work. It doesn't finish it.

Only Agency Admins can apply a snapshot, and only one applies per sub-account at creation. Get the order right the first time: sub-account type, then fields, then pipelines, then the snapshot that bundles all three for the next client.

SaaS CRM launches diverge from a plain client sub-account right here.

A client account only needs to work for one business. Reselling it is different: that account needs rebilling and SaaS configuration built into the snapshot itself, since every clone inherits whatever is missing from the one before it.

None of these steps is complicated alone. What's hard is repeating the same order on the tenth client as the first, which is the actual work behind GHL setup and configuration, and why a snapshot built once ends up worth more than a checklist followed carefully every time.

If pipelines are still the part you're building by hand on every new account, building a sales pipeline in GoHighLevel from scratch covers that piece on its own.

Cover photo by MART PRODUCTION on Pexels