GoHighLevel Dental Snapshot: What It Copies, What It Doesn't, and What to Change Before Going Live
Quick answer
A GoHighLevel dental snapshot is a template of workflows, pipelines, forms, funnels, calendars and message templates copied into your sub-account. It does not copy contacts, phone numbers, integrations or domains, and it carries no consent records. Here is what to check, import and change before a dental practice uses one, including the HIPAA add-on question.
Part of the guide: GoHighLevel expert for dental practices
Key takeaways
- A snapshot copies configuration (workflows, pipelines, forms, funnels, calendars, templates, custom fields). It never copies contacts, conversations, integrations, or assigned phone numbers.
- Importing a snapshot only adds it to your agency library. You then load it into a sub-account as a separate step, and Override choices on conflicts cannot be undone through the load.
- HighLevel's HIPAA article does not mention snapshots, so whether a given snapshot is safe in a HIPAA sub-account is your call: keep PHI out of templates and review every message before it sends.
- Third-party dental snapshots come with placeholder offers, consent wording and pricing. Treat each one as a draft to audit, not a finished compliance setup.
- The HIPAA add-on is US$297 a month and cannot be cancelled once enabled (checked Oct 21, 2026), so decide on it before you load patient-facing workflows.
A GoHighLevel dental snapshot is a ready-made template of configuration, copied from one sub-account into another, that gives a dental practice a starting pipeline, forms, calendars, workflows and message templates. It saves build time. It does not set up your phone number, your domain, your integrations or your patient consent process, and it holds no patient data.
Checked on October 21, 2026 against HighLevel’s help center articles on snapshots, importing, loading and HIPAA. We did not verify any specific dental snapshot listing, price or contents, so this page tells you what to look for rather than naming products.
What is a GoHighLevel snapshot?
A snapshot is a reusable template that captures selected configuration from a source sub-account so it can be copied into new or existing sub-accounts. HighLevel’s Snapshots overview (modified October 9, 2026) says you build the setup in a source sub-account first, then create the snapshot from it. You cannot build one from scratch.
For a dental practice, the assets that matter most are:
- Workflows and triggers, for new-inquiry follow-up, confirmations, reminders and recall.
- Pipelines, tags, custom fields and custom values, for tracking inquiry to booked to treated.
- Calendars and services, including calendar groups and service resources.
- Forms, surveys, funnels and websites, for new-patient and emergency pages.
- Text and email templates, and Review Settings.
- Conversation AI and Voice AI agents, if the creator included them.
Snapshots are not updated automatically. The creator must refresh them, and HighLevel’s article says loading is for initial deployment, with a separate push workflow for updating sub-accounts later.
What does a snapshot copy, and what does it not copy?
A snapshot copies configuration and never copies live data or connections. This table sorts what HighLevel’s overview article lists, plus the items it does not mention, which you should assume are yours to set up.
| Item | Copied by a snapshot? | What you do |
|---|---|---|
| Workflows, triggers, pipelines, tags | Yes | Review every step and every message |
| Forms, surveys, funnels, websites | Yes | Replace content and consent wording |
| Calendars and services | Yes | Rebuild with your real providers and chairs |
| Text and email templates | Yes | Edit for your practice and your rules |
| Contacts, appointments, conversations | No | Import your own patients or leads separately |
| Stripe and third-party integrations | No | Reconnect your own accounts |
| Voice AI phone numbers | No | Assign your own number |
| Smart List records | No (configuration only) | Lists fill from your own contacts |
| Domains, A2P registration, users | Not listed as copied | Set up per account |
| Consent records | Not listed as copied | Collect fresh consent from your own patients |
Source: HighLevel Support, Snapshots overview, modified October 9, 2026, checked October 21, 2026. The last three rows are not in the article’s copied or not-copied lists, so treat them as things to verify in your own account.
The overview article also notes that website or WordPress assets may need domain, plugin or license updates after loading.
How do I import a snapshot into GoHighLevel by link?
Open the share link while signed in to your agency, review the pop-up and click Import Now. HighLevel’s import article (modified September 12, 2026) gives these steps:
- Make sure your user has Snapshot permissions, including Share/Import Snapshots, and sign in to the target agency.
- Open the share link (paste it into a new tab if it does not open).
- Review the import pop-up and optionally rename the snapshot.
- Click Import Now.
- Check your imported snapshots list, and wait for the greyed-out processing state to clear.
- Load it into a sub-account separately.
Importing does not place any assets in a client account. Links can fail if they have expired, if a one-time link was already used, or if a restricted link is opened outside the intended agency.
How do I load it into a dental sub-account without breaking anything?
Use Manage Client, then Actions, then Load Snapshot, pick the snapshot, choose the assets, then resolve conflicts. HighLevel’s load article (modified September 27, 2026) says loading does not delete your data, but if you choose Override on a conflicting asset, “the override cannot be undone through the Snapshot load.” So:
- Load into a new, empty sub-account where you can.
- If the account already has workflows, forms or calendars, choose Skip unless you are certain.
- Load only the asset categories you plan to audit. You can always load more later.
The load modal on the imported snapshots tab also keeps a View History log of each load, which helps if you need to see what went in.
Is a third-party dental snapshot safe to install?
It is safe only if you audit it, because you are inheriting someone else’s wording, offers and automation logic. Search results for this keyword are mostly seller pages and agency blogs, so claims about what a snapshot contains are marketing until you open the assets yourself. What to look for before you install:
- A clear asset list. If the seller cannot say which workflows, forms and calendars are inside, skip it.
- Placeholder consent language. Many templates ship with generic opt-in text written for marketing agencies, not dental practices.
- PHI inside templates. No template should include patient names, treatment details or anything clinical. Keep reminders to date, time and location.
- Dental-specific logic that matches how you work. New-patient inquiry, emergency, cosmetic or implant consult, recall and reactivation flows all assume a workflow in your office. Confirm yours matches.
- Pricing and offers you did not write. Remove any discount, financing claim or before-and-after content before it goes live.
- Seller support and update history. Snapshots do not update on their own, so ask how fixes reach you.
HighLevel’s Marketplace developer docs describe a review process for listed apps, but we found no HighLevel guidance telling buyers how to vet a snapshot, so the review is yours.
Does the HIPAA add-on change how snapshots work?
HighLevel’s HIPAA article (modified June 11, 2026) does not mention snapshots, so we cannot confirm any rule about loading one into a HIPAA sub-account. What the article does say, checked October 21, 2026:
- HighLevel accounts are not HIPAA compliant by default.
- The add-on is US$297 a month and covers encryption of ePHI, Business Associate Agreements, audit logging and MFA enforcement.
- It applies to all location accounts, and Agency Owners must still turn the HIPAA toggle on for each sub-account under Advanced Settings.
- It cannot be cancelled, refunded, removed or downgraded once enabled.
Practical reading: a snapshot holds no patient data, so the content risk sits in the template itself. Do not paste PHI into any template, and keep reminders minimal. If you plan to use a HIPAA sub-account, ask HighLevel support to confirm snapshot loading in writing, and read Is GoHighLevel HIPAA compliant? and our HIPAA setup steps. None of this is legal advice; your counsel decides what your practice needs.
What should I change in a dental snapshot before going live?
Work through this checklist in a test sub-account before any patient or lead is added.
| Symptom in the template | Likely cause | Fix before launch |
|---|---|---|
| Another practice’s name, phone or address on a page | Placeholder content from the creator | Search every form, funnel, template and email footer and replace |
| Messages never send by SMS | No number, or A2P not registered | Buy or port your number and finish A2P registration |
| Form says “I agree to receive marketing messages” with unclear scope | Generic consent text | Rewrite with your counsel, matching what you actually send |
| Booking page shows wrong chairs or providers | Calendar copied without your team | Rebuild services, resources, hours and buffers |
| Reminder mentions a treatment type | Template wording carries clinical detail | Cut it to date, time and location |
| Workflow fires for existing patients | Trigger has no filter on tags or opt-in | Add conditions and test with a dummy contact |
| Reviews or links go to someone else’s profile | Review Settings copied | Set your own review link |
| Website pages not on your domain | Domains are not copied | Connect your domain and check it loads |
| Payments or calendars show disconnected | Integrations not copied | Reconnect your own Stripe and Google or Outlook calendar |
| Dashboard or Smart Lists look empty | Configuration copied, records not | Import your own contacts, then confirm lists fill |
Compiled by aibrevo from HighLevel’s snapshot, import and load articles checked October 21, 2026. Fixes are our recommended practice, not HighLevel rules.
Finish with an end-to-end test: submit each form, book each calendar, trigger each workflow and read every message as the patient would. Our dental practice GoHighLevel guide shows what a full build looks like around a template.
Should I use a snapshot or have the account built?
A snapshot saves hours on the repeatable parts, and does nothing for the parts that depend on your practice. If you are a single-location practice with simple needs, a vetted snapshot plus careful setup can work. If you have multiple locations, a practice management system to connect, or strict consent and HIPAA requirements, you are rebuilding much of it anyway. Our GoHighLevel setup for dental practices and GoHighLevel for dental practices pages explain what we cover, and the dental expert page is where to start if you want help.
aibrevo’s GoHighLevel setup is quoted from $1,499 to $4,999 for a single business, with multi-location work quoted individually. For other costs, see GoHighLevel pricing and the implementation cost guide. For snapshot basics, read GoHighLevel snapshots explained and the snapshot marketplace guide.
Founder’s note, Alpit Patel. A snapshot saves build time, but it also copies someone else’s choices. I’d read every message, form and consent line in it before it goes near a live number, and I’d never trust placeholder consent language. The copy that matters is yours. I founded aibrevo in San Francisco in 2021, and through autoesta I have overseen 320+ GoHighLevel implementation projects across med spas, real estate, healthcare, dental, home services, SaaS and professional-services clients in the US, UK and UAE. About Alpit
Sources
- HighLevel Support, Snapshots overview, modified October 9, 2026.
- HighLevel Support, How to import snapshots in HighLevel, modified September 12, 2026.
- HighLevel Support, Load snapshots into an existing sub-account, modified September 27, 2026.
- HighLevel Support, Imported snapshots: load modal and history tracking, modified July 31, 2026.
- HighLevel Support, HIPAA compliance with HighLevel, modified June 11, 2026.