HighLevel Snapshot Import Checklist Before Client Launch
A HighLevel snapshot import checklist catches the account-specific setup that still needs work after a snapshot has been loaded into a client sub-account.
The snapshot may bring over funnels, forms, workflows, calendars, pipelines, custom values, templates, and other reusable pieces. That does not mean the client account is ready for traffic.
Business details may still point to the source account. Calendars may have no assigned user. Form notifications may go to the wrong inbox. Workflows may contain old senders, test numbers, inactive steps, or sample links. Phone, email, payment, and permission settings may still need to be connected.
Loading the snapshot gives you the starting build.
The post-import check turns it into the client’s build.
Why a HighLevel Snapshot Import Checklist Is Still Needed
A snapshot saves build time. It does not remove client-specific setup.
That distinction is easy to miss because a loaded snapshot can look complete. The funnels are visible. The workflows exist. The pipeline has stages. The forms are in place. The account feels busy.
Busy is not the same as ready.
HighLevel separates importing a snapshot into the agency library from loading that snapshot into a client sub-account. Once the load finishes, the team still needs to review the destination account and replace anything tied to the original source setup.
HighLevel’s snapshot import guide explains that difference directly. The snapshot must first enter the agency library, then be loaded into the chosen sub-account.
The next mistake is assuming every item transfers in a usable state.
HighLevel’s snapshot overview lists many items that snapshots can copy. It also lists items that do not transfer, including contacts, appointments, conversations, Stripe connections, third-party integrations, and some assigned resources.
Some copied items also need client-specific connections or approvals before anyone should call the account live.
That is the job of the post-import review.
Importing a Snapshot Is Not the Same as Launching the Client
A clean snapshot gives your team a repeatable base. It should reduce rebuilding, not remove judgment.
After loading, treat the account like a fresh installation that already has part of the structure in place.
Your team still needs to answer basic questions:
Does every client-facing page show the right business?
Do appointments reach the right person?
Do forms create the right contact and opportunity records?
Do workflow messages use the right sender, links, and business details?
Can the account actually send email or SMS?
Do payments go to the client’s connected account?
Can the client see the areas they need without getting access to everything?
If those questions have not been tested, the build is not done.
HighLevel Snapshot Import Checklist: Confirm the Right Items Loaded
Start with a simple inventory check.
Do not begin editing workflows before confirming the expected pieces actually arrived. A snapshot may have been created with selected items instead of everything from the source sub-account. The person loading it may also choose which items to apply.
Review the destination account against the snapshot’s promised contents.
Check for the expected:
funnels and websites
forms and surveys
workflows
pipelines
calendars
custom fields and custom values
email and SMS templates
tags
trigger links
products or checkout-related items included in the package
Missing items do not always mean the load failed. The snapshot may not have included them. The wrong version may have been selected. A conflict may have been skipped. The source snapshot may need to be refreshed.
Find that out before someone starts rebuilding the missing piece manually.
1. Replace Custom Values and Business Details
Custom values make snapshots reusable, but they also make old account details easy to miss.
A source account may contain business names, phone numbers, support emails, booking links, office addresses, logos, review links, policy links, offer names, or sender details. Those values can appear across several parts of the account at once.
Check the custom-value settings first. HighLevel allows custom values to appear inside workflows, emails, SMS messages, funnels, websites, and other account content. One old value can therefore show up in many places.
HighLevel’s custom-values guide shows how widely those values can be used across a sub-account.
Replace or confirm:
business name
business address
main phone number
support email
website URL
booking URL
privacy policy and terms links
review link
offer or service names
default sender name
Then search the account for hard-coded details that do not use custom values.
A snapshot can have clean custom values and still contain an old phone number typed directly into a funnel footer or email template.
2. Check Calendars, Assigned Users, and Availability
A calendar can transfer without being ready to book real appointments.
The destination account may not have the same users as the source account. The assigned team member may not exist. The calendar may need new availability, time-zone settings, meeting locations, linked calendars, notifications, or routing rules.
Review every live calendar.
Check:
calendar name
assigned user or team
working hours
appointment duration
buffer time
minimum scheduling notice
meeting location
confirmation and reminder settings
linked Google or Outlook calendar
conflict-calendar settings
Book a real test appointment after making the changes.
Do not stop at checking the calendar screen. Confirm the available slots, form fields, confirmation page, appointment record, assigned user, and client notification.
3. Review Forms, Surveys, and Notification Emails
Forms and surveys are one of the easiest places for an imported account to look finished while still sending information to the wrong place.
Open each live form or survey and review:
fields
required-field settings
consent language
redirect URL
thank-you message
internal notification recipients
auto-response content
workflow connections
HighLevel supports direct email notifications and auto-responses for form and survey submissions. Those recipients and messages should match the client account, not the source build.
Use HighLevel’s form and survey notification guide if the team needs to confirm where submission alerts and auto-responses are set.
Submit each form yourself.
Confirm the contact record, field mapping, tag, opportunity, internal alert, thank-you path, and first follow-up message.
Viewing the form is not a test.
4. Inspect Workflow Triggers Before Activating Them
Imported workflows need a trigger review before they start touching real contacts.
A workflow may be set to draft or published. It may point to a form, survey, calendar, tag, pipeline, or custom field that changed during the import. It may contain filters copied from the source account. It may also hold test addresses or internal recipients.
Open each workflow tied to the client launch.
Check the trigger first:
Does it point to the correct form, survey, calendar, stage, or tag?
Do the filters match this client?
Could old contacts enter by mistake?
Should the workflow allow re-entry?
Does it need a start date or other limit?
Then inspect the actions.
Pay close attention to:
send-from names and addresses
SMS numbers
internal notification recipients
assigned users
pipeline and stage updates
calendar links
URLs
wait steps
if/else branches
goals and stop conditions
The workflow should not go live because it looks familiar.
Run a test contact through it and watch every step.
5. Fix Sending Steps, Domains, Phone Numbers, and A2P Dependencies
This is where a clean import often hits account-level reality.
Snapshots do not replace email-domain setup, phone-number assignment, third-party connections, or carrier requirements. HighLevel’s snapshot documentation states that connected accounts and integrations may not transfer, and some copied items need post-load configuration.
Check the client’s communication setup before activating live workflows.
Confirm the sending domain, sender address, sender name, reply-to address, and email service used by the account.
If the imported workflows contain email steps, review the sender inside every live path. A workflow can be structurally correct and still fail because the sender has not been connected or authenticated.
AgencySaaS already has a separate guide on HighLevel email deliverability fixes. Use that when the snapshot includes client-facing email and the sending setup still needs work.
Phone and SMS
Confirm that the client account has the correct phone number and that the workflows send from the intended number.
For U.S. application-to-person messaging, A2P registration and opt-in requirements can affect when the account is ready to send live SMS. The workflow existing inside the snapshot does not complete that registration.
Do not use live client contacts to discover that the number cannot send.
6. Review Pipelines and Opportunity Stages
A pipeline should match the client’s real sales path.
Imported stage names may be technically usable but wrong for the business. The source snapshot may use stages such as New Lead, Contacted, Booked, Won, and Lost. The client may need Quote Requested, Inspection Scheduled, Estimate Sent, Approved, Job Completed, or another sequence.
Review:
pipeline name
stage names
stage order
opportunity ownership
workflow actions that create or move opportunities
automations that fire from stage changes
reporting that depends on the pipeline
Do not rename stages without checking the connected workflows.
A stage name can look like simple wording inside the interface while still being part of the account logic.
7. Connect Payment Links and Checkout Settings
A snapshot should never carry the assumption that payment is ready.
HighLevel lists Stripe connections among the items that do not transfer through snapshots. Payment providers, products, payment links, taxes, currencies, receipts, and order behavior need their own review inside the client account.
Check every client-facing payment path:
connected payment provider
product name
price
currency
one-time or recurring setting
trial or setup fee
receipt behavior
post-purchase redirect
workflow triggered after payment
Use a test mode or low-risk test product when available.
Do not wait for the first customer to report that the checkout points nowhere, charges the wrong amount, or fails to start the post-purchase workflow.
8. Remove Placeholder Content and Sample Records
Snapshot builders often leave examples in the source account to explain how the build works.
That is useful during development. It becomes a problem when examples appear in the client account.
Search for:
sample company names
placeholder phone numbers
fake staff names
sample testimonials
temporary URLs
test email addresses
test SMS recipients
dummy products
sample pipeline opportunities
old calendar links
draft pages that should not be published
HighLevel snapshots do not transfer live contacts and conversations, but the account may still contain records created during client setup or testing after the load.
Label test records clearly. Remove them before final reporting or client access if they serve no ongoing purpose.
9. Run Test Contacts Through the Full Client Path
The best post-import check is one complete test from entry to outcome.
Create a fresh test contact using an address and phone number your team can receive.
Then run the client’s main path:
Submit the live form or survey.
Check that the contact record contains the right fields.
Confirm the correct tag was applied.
Confirm the opportunity entered the right pipeline and stage.
Check the assigned user.
Receive the internal notification.
Receive the client-facing email or SMS.
Open every link inside the message.
Book through the calendar if the path includes scheduling.
Confirm the stop condition works after booking or conversion.
Watch the workflow history instead of assuming each step fired.
If the offer has more than one lead source, run a separate test for each important source. A website form, missed call, calendar booking, payment, and imported lead may enter through different triggers.
One successful test does not prove every entry path works.
10. Set Client Permissions and Prepare the Handoff
The last check is not technical. It is access.
Clients should see what they need to use. They should not receive full control by default because it is faster for the agency.
HighLevel allows sub-account roles, module permissions, assigned-data limits, and more specific access controls. Review those settings before sending the login.
HighLevel’s sub-account permissions guide covers user roles, assigned-data restrictions, and module-level access.
For each client user, decide:
Admin or User
which modules they need
which calendars they can access
which contacts or opportunities they can see
who can edit workflows
who can change payments or integrations
who owns future account changes
Then prepare a short handoff.
The client should know what has been set up, what was tested, what still depends on them, where support starts, and what counts as a paid change.
For the larger onboarding path, connect this process to HighLevel client onboarding automations. A tested account can still stall if the client never receives a clear first step.
Keep Post-Import QA Separate From Snapshot Support Boundaries
These two topics connect, but they solve different problems.
HighLevel snapshot support boundaries define what the buyer receives, what setup is still required, how long help lasts, and when the work becomes custom implementation.
The HighLevel snapshot import checklist starts after the load.
It answers a different question:
What must the agency check before this specific client account is allowed to go live?
One protects the offer.
The other protects the launch.
An agency selling snapshots needs both.
The Final HighLevel Snapshot Import Checklist Before Launch
Before marking the account ready, confirm the following:
The expected snapshot items loaded.
Custom values show the client’s information.
Hard-coded source-account details are gone.
Calendars have the right users, hours, and connected calendars.
Forms and surveys send notifications to the right people.
Workflow triggers point to the correct account items.
Email and SMS steps use working senders.
Phone, email, domain, and A2P requirements have been reviewed.
Pipelines match the client’s sales path.
Payment providers and checkout settings belong to the client.
Placeholder content and sample records have been removed.
Test contacts passed through every major entry path.
Client users have the right permissions.
The handoff states what was tested and what happens next.
Do not treat this as admin cleanup after the real work.
This is the real work between “snapshot loaded” and “client live.”
Post-Import QA
Final Takeaway
A snapshot import is not the finish line.
It is the point where the repeatable build meets the client’s real account.
Use the snapshot to avoid rebuilding. Use the checklist to catch what the snapshot cannot decide for you.
Then launch the account only after the real lead path has been tested from start to finish.
