GoHighLevel snapshot questions
17 answers, grouped by the thing you are trying to work out. If the one you need is missing, ask us and we will add it.
Snapshots, explained
A snapshot is a saved copy of the structure of a sub-account: funnels, websites, workflows, pipelines, calendars, forms, surveys, triggers, custom fields, custom values and message templates. Importing one recreates all of that in another sub-account in a few minutes. It is the closest thing HighLevel has to a project template.
No. This is the single most common misunderstanding. A snapshot moves structure only. Contacts, opportunities, conversations, call recordings, payments and appointment history all stay behind. If you need those, you export and import them separately.
A template is one asset, usually a funnel or an email. A snapshot is the whole account structure with the connections between assets intact, so a form still feeds the right workflow and the workflow still moves the right pipeline stage. Buying templates leaves you wiring them together; buying a snapshot does not.
To import and manage snapshots across sub-accounts, yes, you need agency level access. A single sub-account user can receive a shared snapshot link but cannot create or manage a snapshot library.
Buying from BuildKitHQ
Individual industry kits run from $647 to $1,197 depending on how much is inside. The all-access bundle covers all 16 kits and every future release for one payment. Full detail is on the pricing page.
One time. You buy the kit, you keep the kit, and updates for the first twelve months are included. There is no recurring licence and nothing stops working if you never buy anything else.
Yes, for accounts you own or manage as an agency. What you cannot do is resell or redistribute the snapshot itself as a product. The full terms are on the terms page.
Yes, three of them, and they are complete kits rather than stripped demos. They are on the free snapshots page and the only cost is your email address.
Tell us within fourteen days and we refund it. We would rather return the money than have a kit sitting unused in your account with our name on it.
Installing and using a kit
From the agency view, open Account Snapshots, choose the snapshot, then load it into the sub-account you want. Our kits arrive as a share link, so you click it once from your agency login and the snapshot appears in your own library ready to load.
The import itself is usually under fifteen minutes. Configuring it for a specific business, which means domains, calendars, numbers and the custom values, is another one to three hours. Every kit ships with the checklist of what to change.
Yes. Once loaded, every workflow, funnel, form and template is a normal asset in your sub-account and there is no lock of any kind. Most buyers change roughly a fifth of the copy and leave the structure alone.
Not automatically, and you would not want them to. Pushing an update overwrites customisation. When we release an update you get the new version plus a change list, so you can apply only the parts you want.
Nine times out of ten it is a permissions issue on the agency account or a sub-account that is still provisioning. Send us the error and we will look at it the same business day; support on our kits does not expire.
Build services
Yes. On white-label work nothing carries our name, we do not contact your clients, and the documentation we produce lives in your workspace.
Seven business days for a standard done-for-you setup, from the scoping call to the training session. A2P approval sits outside that window because carrier review time is not ours to control.
Yes, and it is a large share of what we do. It starts with an audit, because rebuilding four broken workflows usually beats adding four new ones.
Still not sure
Send the actual question. A person reads it, and the answer usually arrives the same working day rather than as a templated reply about how much we value your enquiry.