Home › Guides › GoHighLevel Snapshot Build-Out
What a GoHighLevel Snapshot Build-Out Actually Is
"Snapshot" is the most confused word in the GoHighLevel world. A snapshot packages the STRUCTURE of a sub-account — so an agency can build a system once and load it into every new client account. It never packages the client's data or connections.
Inside a snapshot
Workflows (triggers, actions, waits, branches), funnels and websites, pipelines, email and SMS templates, forms and surveys, calendars, custom fields, tags, custom-value KEYS, reputation settings, smart lists, products and membership structures.
Never inside a snapshot
- contacts
- conversations
- opportunities
- payments/billing
- API keys
- phone numbers/LC-Phone
- A2P 10DLC registration
- connected domains
- third-party integrations
Every one of those is reconnected per sub-account — which is why a Kronos build-out ships the reconnection checklist with the blueprint.
How a Kronos build-out reaches your account
Step 1. Build the system in your own GoHighLevel sub-account using this blueprint, workflow recipes and copy package
Step 2. This generated package is a document, not a native snapshot, import file or share link
Step 3. After you build the system yourself, you may create and share your own snapshot using GoHighLevel tools; Kronos never holds customer credentials
Step 4. Run the per-client configuration pass using the blueprint's reconnectionChecklist: fill custom values, connect domain, calendar and Stripe, register A2P 10DLC and provision phone numbers, reconnect third-party integrations
Step 5. Test one end-to-end lead through every workflow before launch
Build yours
GoHighLevel Build-Outs — pick a blueprint, Kronos generates the package around your brand and offer.