GoHighLevel Snapshot Guide: What's Inside Dental, Real Estate and Coaching Builds

A GoHighLevel snapshot is a saved copy of a sub-account's configuration: pipelines, custom fields, workflows, forms, calendars, funnels and message templates. You load it into a new sub-account and the whole system arrives at once. What it does not carry is any live data, and that gap decides whether the snapshot works on day one.

This post opens up the three industry snapshots we get asked about most, dental, real estate and coaching, and lists what sits inside each one: the pipeline stages, the fields, the automations and the forms. It also covers what fails to transfer, because that list is where most snapshot installs quietly break.

What is a GoHighLevel snapshot?

A GoHighLevel snapshot is a reusable template captured from a working sub-account. It copies configuration, not customers: workflows, pipelines, custom fields, custom values, calendars, forms, funnels, email and WhatsApp templates, dashboards and AI agents. You apply it to a new or existing sub-account instead of rebuilding those assets by hand.

HighLevel's own documentation is blunt about how one gets made: "You do not build a Snapshot directly from scratch. First, configure the source sub-account with the assets and settings you want to reuse, then create a Snapshot from that account."

That sentence carries the most useful design rule in this whole topic. A snapshot is only as clean as the sub-account it was taken from. If the source account has test contacts' leftover tags, three abandoned versions of the same workflow and a custom field called "Field 7", every client that loads it inherits the mess. We keep one master sub-account per vertical that never touches a live client, and we only ever snapshot from that.

HighLevel groups what a snapshot can copy into 12 asset categories, from advertising and AI agents to memberships, documents and WordPress sites. The part that matters for an industry build is narrower: CRM structure (pipelines, custom fields, custom values, tags, smart lists), automation (workflows and triggers), calendars, forms and surveys, and message templates.

What does a GoHighLevel snapshot not copy?

A snapshot does not copy contacts, appointments, conversations, message history, reputation data, Stripe connections or third-party integrations. HighLevel's snapshot overview lists 16 items that do not transfer, and several of them are exactly the things a new client expects to work on the first morning.

The ones that bite in practice:

• Phone numbers and sending domains. Workflows arrive intact but have nothing to send from until you assign a number and verify an email domain.
• WhatsApp templates. The template text copies across, but each one needs Meta approval inside the new account before it can send.
• Payment connections. Stripe (and Razorpay for Indian clients) must be reconnected, so any invoice or payment-link workflow is inert until you do.
• Voice AI agents. The agent configuration copies; the phone number assigned to it does not.
• Integrations generally, including anything wired through n8n or a Zapier-style connector. The webhook action copies, the credentials behind it do not.

So a snapshot load takes a few minutes, and making the account usable takes the rest of a working day. Anyone quoting "live in minutes" is describing the first half.

How should an industry snapshot be structured?

Build it in two layers: a core layer that every client gets, and an industry layer on top. The core carries naming conventions, lead-source tracking, consent fields, owner assignment, custom values and reporting. The industry layer carries the pipeline, the vertical-specific fields and the automations that follow that buyer's journey.

The core layer is where a snapshot earns its keep, and custom values are the piece most marketplace builds get wrong. Every template, email and WhatsApp message should pull the business name, address, booking link, Google review link and support number from custom values, never from hardcoded text. Then the post-load job is filling in one settings screen rather than hunting through every template for the previous clinic's name.

Our core layer, loaded under every vertical, contains:

• A lead source field (dropdown, not free text) so reporting works from the first lead.
• A WhatsApp consent field with a timestamp, which matters under India's Digital Personal Data Protection Act, 2023.
• A naming convention for workflows: vertical, stage, action, so "DENT | Booked | 24h reminder" tells you what it does before you open it.
• A rule for tags versus fields: fields hold facts about a contact (budget, treatment interest), tags hold short-lived states that trigger automations.
• A dashboard with speed-to-lead, bookings and show rate, because those three numbers tell an owner whether the system is working.

We covered the order these decisions get made in, and which ones cannot be undone, in our GoHighLevel setup guide. A snapshot freezes those decisions and copies them into every client, which is why a bad field model is so expensive: you are not making the mistake once, you are shipping it.

What's inside a dental clinic GoHighLevel snapshot?

A dental snapshot is built around two loops: turning an enquiry into a first consultation, and bringing existing patients back for recall. The pipeline follows the patient from enquiry to completed treatment, and the automations do most of their work around appointments: confirmations, reminders, no-show recovery and review requests.

Pipeline

New enquiry → Contacted → Consultation booked → Showed → Treatment plan presented → Treatment accepted → In treatment → Completed. A separate recall pipeline tracks patients due for a six-month check-up so they never clutter the new-patient view.

Custom fields

• Treatment interest (implants, aligners, root canal, cleaning, cosmetic)
• Preferred doctor and preferred branch, for multi-chair or multi-location practices
• Treatment plan value, as a monetary field so the pipeline shows real money at each stage
• Last visit date and recall due date
• WhatsApp consent

Automations

• Speed-to-lead: a WhatsApp reply and a call task for the front desk the moment an enquiry lands.
• Appointment confirmation, then reminders at 24 hours and 2 hours.
• No-show recovery that offers a rebooking link the same day.
• Treatment-plan follow-up at day 2, day 7 and day 21 for patients who were quoted but did not accept, the stage where most dental revenue leaks.
• A review request after a completed visit, sent from custom values so it points at the right Google profile.
• A recall reminder when the recall due date arrives.

Forms and calendars

A new-patient intake form mapped field by field to the list above, and one calendar per doctor with service durations set per treatment type, so a 20-minute cleaning and a 60-minute implant consult cannot be booked into the same slot.

What's inside a real estate GoHighLevel snapshot?

A real estate snapshot is built for a long, high-value cycle with one decisive moment: the site visit. Buyers can take months to commit, so the pipeline is short and the nurture is long. The automations focus on getting a portal lead to a site visit quickly, then staying useful until the buyer is ready.

Pipeline

New lead → Qualified → Site visit scheduled → Site visit done → Negotiation → Token or booking → Registered. Leads that go quiet move to a separate long-term nurture pipeline rather than sitting in "Qualified" forever and poisoning the conversion numbers.

Custom fields

• Budget range and configuration (1, 2, 3 BHK or villa)
• Preferred micro-market
• Possession preference: ready to move or under construction
• Home loan needed (yes, no, pre-approved)
• Project of interest, and the agent assigned

Custom values that matter here

Project name, site address, map link and RERA registration number sit in custom values. Section 11(2) of the Real Estate (Regulation and Development) Act, 2016 requires a promoter's advertisements to carry the project's RERA registration number, so pulling it from one place into every template means a single edit keeps every message compliant.

Automations

• Round-robin assignment across agents, with a call task and a WhatsApp reply within minutes of a portal lead arriving.
• Site visit confirmation with the map link, plus a morning-of reminder.
• Post-visit feedback that asks one question and moves the deal based on the answer.
• A monthly long-cycle nurture: new inventory, price revisions, possession updates.

One caution: property portal lead feeds are integrations, so they never come across in the snapshot. Each brokerage reconnects its own portal feeds after the load, usually through an email parser or an n8n workflow.

What's inside a coaching GoHighLevel snapshot?

A coaching snapshot runs an application funnel into a sales call, then hands the enrolled client into onboarding and delivery. Unlike dental or real estate, much of the value sits after the sale: course access, weekly check-ins and renewals. HighLevel's snapshots copy membership offers, products, webinars and certificates, so the delivery side can ship too.

Pipeline

Application submitted → Qualified → Discovery call booked → Call completed → Offer sent → Enrolled → Onboarding → Active → Renewal due.

Custom fields

• The application answers themselves: goal, current situation, timeline, budget band
• Program of interest and cohort
• Start date, renewal date and payment plan

Automations

• Application scoring that routes qualified applicants to the booking calendar and everyone else to a nurture sequence.
• Call reminders and a no-show follow-up.
• Offer follow-up after the call, stopping the moment a payment lands.
• Onboarding: course access, welcome sequence and a first check-in booking.
• Failed-payment follow-up for instalment plans. This only works once the payment connection is re-established, because Stripe does not transfer.
• A renewal sequence starting 30 days before the renewal date.

If you want one of these installed and tuned to your business rather than built from a blank account, that is what our GoHighLevel snapshot and template service does: we match your business to the closest vertical build, load it, then configure it to your brand and offers.

How long does it take to load a GoHighLevel snapshot?

Loading a snapshot takes minutes: pick it in Account Snapshots, choose the target sub-account, select the assets and confirm. The configuration that follows takes most of a working day for a single location, because every non-transferring item has to be connected and every workflow tested before it goes live.

Our post-load checklist, in order:

• Fill in every custom value: business name, address, links, support number.
• Assign phone numbers and verify the sending domain.
• Connect WhatsApp through the BSP and submit each template for Meta approval.
• Reconnect Stripe or Razorpay, and any portal or form integrations.
• Add users, then set calendar owners and availability.
• Run a test contact through every workflow end to end.
• Only then switch workflows from draft to published.

The last two steps are the ones people skip. A workflow that fires on the first real lead with an unapproved WhatsApp template or an empty custom value fails quietly, and the first person to notice is usually the customer.

Should you buy a marketplace snapshot or build your own?

Buy one to learn how others structure an account; build your own for anything you will load into client accounts repeatedly. Marketplaces are large: Top GHL Snapshots advertises builds for 30 industries. The quality varies because a snapshot built to demo well is designed around screenshots, not reporting.

Before buying, ask for the asset list. HighLevel lets you view a snapshot's contents before loading it, and three things tell you most of what you need:

• Are custom fields typed (dropdown, date, monetary) or all free text? Free text means no reliable reporting.
• Do templates use custom values, or is the demo business name hardcoded?
• Are workflows named so you can tell what they do, or are they "Workflow 12 copy"?

If the answers are bad, the snapshot still saves time on funnel pages and email copy. Just rebuild the CRM structure underneath it before a client relies on it. We made the case for modular builds over one giant workflow in our post on what a GoHighLevel agency should deliver.

How do you update a snapshot after clients are using it?

Change the master sub-account, refresh the snapshot so it captures those changes, then push selected assets to the linked sub-accounts. HighLevel supports refresh and push natively, and its linked-asset controls decide which assets in each client account stay connected to future pushes.

The risk is overwriting a client's own edits. If a clinic rewrote its reminder copy and you push the master version, their change is gone. Our rule: anything a client is expected to edit (message copy, form wording) is unlinked after install, and only structural assets (workflow logic, fields, dashboards) stay linked for pushes. That split is decided at install, not after the first complaint.

Frequently asked questions

How do I create a snapshot in GoHighLevel?

From Agency View, open Account Snapshots and click Create New Snapshot. Name it for its use case, select the source sub-account, then choose Select All or expand each category to pick specific assets, and click Create. HighLevel's step-by-step guide covers the retry option if some asset categories fail to load.

Can I load a snapshot into a sub-account that already has data?

Yes. HighLevel supports loading a snapshot into an existing sub-account, and you can choose which assets to apply. Contacts and conversations already in the account are untouched, but assets with matching names can conflict, so load selectively and check pipelines and custom fields afterwards rather than importing everything blind.

Can I share a snapshot with another agency?

Yes. Sharing generates a link the other agency uses to import the snapshot into its own library. If you do not want your workflows and templates copied onward, HighLevel's Assets Protected Snapshots setting restricts what the recipient can reuse. Protected assets are one of the items HighLevel lists as not transferring through a snapshot.

Does a GoHighLevel snapshot include AI agents?

It includes Conversation AI, Voice AI agents, Agent Studio projects, brand voice and knowledge bases. It does not include the phone number a voice agent answers on, so every voice agent needs a number assigned in the new account, and any knowledge base referencing the previous business needs rewriting before it answers a real caller.

Is one snapshot enough for a multi-location business?

Usually yes: one snapshot, loaded once per location, with custom values carrying the location-specific address, number and links. Where locations run different services, keep the service-specific calendars and workflows in a separate small snapshot and load it only where needed, rather than maintaining near-identical full builds.

If you are choosing between a marketplace build and one designed around your sales process, book a 30-minute call with us and we will walk through which vertical build fits and what it would need changed.