The GoHighLevel snapshot installation checklist

Read this first

A GoHighLevel snapshot installation is the work of loading a packaged sub-account configuration into a live account and making every part of it function against real numbers, real inboxes and real customers. The import is one step in that work and by far the shortest.

An imported snapshot is not a working snapshot. Treat the import as the beginning of the checklist rather than the end of it, and the rest of this page is survivable. Skip that distinction and you will find out about the gaps from a customer.

Before you import

• Decide which sub-account this is going into, and confirm it is one you are willing to have permanently shaped by this file. Un-importing is not a feature.
• Take an inventory of what is already in that sub-account. Existing calendars, pipelines and custom fields will sit alongside the imported ones and the duplicates are yours to reconcile.
• Collect the business details before you start: trading name, addresses, hours, booking policy, deposit rules, the phone number that should appear in messages, the domain the email will send from.
• Get the domain registrar login now. Not later. Every email delay in this process is really a delay in getting into a DNS panel.
• If the snapshot came from elsewhere, read the message copy before importing it. Anything you would not send to your own customer is work you have just bought.

The import

• Load the snapshot and then open every asset it carried rather than trusting the summary screen. Imports drop things quietly, and the report will not always say so.
• Check that workflow triggers survived. Triggers referencing a calendar, a form or a pipeline stage can arrive pointing at nothing, and a workflow with a broken trigger looks identical to one that is simply waiting.
• Check that calendars carry their availability, buffers and appointment durations. Availability is one of the most common casualties.
• Check that pipeline stages arrived in the intended order. Reordered stages will not stop anything from running, which is why nobody notices.
• Rebuild by hand anything that did not come through, and write down what it was. That list is useful evidence about the quality of the file you bought.

The rebrand

• Replace the placeholder business details everywhere they live, and do it through custom values rather than by editing individual messages. Custom values are the reusable business details wired through every message, and they are the difference between a rebrand that takes an afternoon and one that keeps surfacing an old name for a year.
• Set your colours, logo and typography on the site, then read the site as a stranger would. Placeholder copy is to be replaced, not hidden behind an image.
• Correct the service wording to what you actually sell, including the things you do not sell. A booking page offering a service you dropped last spring is worse than no booking page.
• Update the sending identities: from-name, reply-to, the signature block, the physical address required in marketing email.
• Check the legal pages carry your entity, not the builder’s.

A2P and 10DLC registration

• File this on day one. Filing takes minutes and approval is the carriers’ decision, so the clock is the constraint rather than the work.
• Write the brand and campaign descriptions to survive review rather than to be finished quickly. Vague use cases are the usual rejection reason.
• Make sure the opt-in language you describe in the filing is the opt-in language that actually appears on your forms. Reviewers check, and a mismatch fails.
• Confirm every form that feeds an SMS sequence carries visible consent wording and a stated message frequency.
• Track it to a result. A filed registration that was rejected three days ago and nobody read the notice is the single most common reason a launch date slips.

Domain email authentication

• Send from your own domain inside GoHighLevel rather than a shared sending identity. Deliverability is a property of your domain and you want to own it.
• Publish the authentication records at the registrar and verify them in the platform rather than assuming propagation.
• Warm the sending identity before the first campaign. A dormant domain that suddenly sends a bulk reactivation is the textbook way to earn a filtering reputation you will spend a month undoing.
• Prove it lands. Send to a real inbox on each of the major providers and confirm it arrives in the inbox rather than the promotions tab.

Testing on live numbers

• Book a real appointment from the public site, on a real phone, and let every message in the sequence arrive. Reading a workflow canvas is not testing.
• Reply to a reminder as a customer would, including replying something unhelpful such as “can we move it”, and see what the system does with an answer it did not expect.
• Cancel, reschedule, and no-show deliberately. The recovery path is the one nobody exercises before launch.
• Send the opt-out keyword and confirm the contact is genuinely suppressed everywhere, not just in the sequence you tested.
• Call the answering desk out of hours and listen to what it says when it does not know the answer.

What breaks silently

These are the failures that produce no error, and they are the reason installation is a checklist rather than a day.

• A workflow whose trigger points at a deleted asset. It never fires and never complains.
• A calendar with the wrong time zone. Everything books, and everything books an hour out.
• Custom fields that arrived but were never mapped on the forms, so the automation references an empty value and sends a message with a gap in it.
• Email authenticated on the domain but sending from a subdomain that is not.
• Registration approved for a campaign whose sample messages no longer match what is actually sent.
• Two sequences both entitled to send after the same trigger, so the customer receives duplicates while your reporting shows two healthy workflows.

The hours, stated plainly

Every edition in this library installs free, and free here means a specific allowance: eleven hours of installation time, to be booked and used within nine days of purchase. That is eleven hours of work rather than nine days of standing by, and the checklist above is roughly what those hours are spent on. Third-party integrations, third-party software and custom development are excluded and quoted separately, on every package here without exception.

For a snapshot that came from somewhere else, the same work is available as a commission: installation for a snapshot you already own. For everything that arrives after launch, the small jobs that accumulate once the account is live, see what to delegate to a GHL VA. Anything still unclear about timing, delivery or what is included is answered on the questions and answers page.