GoHighLevel Client Onboarding Checklist
The order I work through when a new client sub-account goes live, with the Help Center article behind every step. Tick items as you go; progress stays in this browser. Print it or download the PDF. No email needed.
15 stages, 49 steps. Work top to bottom: each stage depends on the ones before it.
- Create the sub-account (with a snapshot if you have one)
- Business profile
- Users and permissions
- Phone number and A2P
- Email sending domain (LC Email)
- Calendars
- Pipelines
- Forms
- Conversation AI basics
- Integrations: Google Business Profile and Facebook
- Payments and Stripe
- Domains
- Workflows
- Reporting
- Client handover and training
1 Create the sub-account (with a snapshot if you have one) 0/4
- Source: Create New Sub-Account Using a Snapshot
- Source: Load a Snapshot Into an Existing Sub-Account
- Source: Snapshots Overview
- Source: Create New Sub-Account Using a Snapshot
Want a written record of what the snapshot loaded? Snapshot Atlas, my own Chrome extension, documents a sub-account's workflows, funnels, pipelines, forms and AI agents.
2 Business profile 0/5
3 Users and permissions 0/3
4 Phone number and A2P 0/3
- Source: How to Purchase and Set Up a Phone Number
- Source: Identity Verification for Phone Number Purchases (US/CA/PR)
- Source: What is A2P 10DLC: Brand and Campaign Registration
See also: A2P registration checklist
5 Email sending domain (LC Email) 0/3
6 Calendars 0/4
7 Pipelines 0/3
8 Forms 0/4
9 Conversation AI basics 0/3
- Source: Guided Form Based Setup for Conversation AI
- Source: How to Create and Set Up a Conversation AI Bot
- Source: How to Create and Set Up a Conversation AI Bot
See also: HighLevel AI plan calculator
10 Integrations: Google Business Profile and Facebook 0/3
11 Payments and Stripe 0/3
12 Domains 0/3
13 Workflows 0/3
- Source: Getting Started with Workflows
- Source: Missed Call Text Back: Overview & Setup
- Source: Getting Started with Workflows
See also: Missed call text back calculator, Workflow triggers and actions list
14 Reporting 0/2
15 Client handover and training 0/3
Why this order
- Identity first. The business profile, A2P, Persona verification and Stripe all ask for the same legal details. Entering them once, correctly, avoids mismatches later.
- Slow steps early. A2P review and DNS changes for email and domains depend on other people and systems, so start them before the build work.
- Build, then automate. Calendars, pipelines and forms are what workflows trigger on, so they come before workflows.
- Hand over last. The client logs in to a finished account, with permissions set and a dashboard that answers their questions.
Tools that help along the way: the A2P registration checklist, the usage cost calculator for the client's SMS, call and email costs, the missed call text back calculator, the AI plan calculator and the profit calculator. If you document client accounts, Snapshot Atlas (my own product) exports a sub-account's setup to Excel, JSON and HTML.
Estimates, not guarantees. This is the order I recommend, not an official HighLevel process. Menus and features change, and some depend on your plan, so check the linked Help Center article if a screen looks different.
FAQ
What order should I set up a new GoHighLevel client in?
Create the sub-account (from a snapshot if you have one), then the business profile, users and permissions, phone number and A2P, the email sending domain, calendars, pipelines, forms, Conversation AI, Google Business Profile and Facebook, Stripe, domains, workflows, reporting, and finally the client handover. Identity and compliance details go first because A2P, email and payments all depend on them.
Does a snapshot set up everything for a new client?
No. HighLevel says snapshots copy configuration such as workflows, funnels, calendars, forms, pipelines and custom fields, but not contacts, conversations, Stripe connections or integrations and other third-party connections. Funnels and websites arrive as drafts until a domain is connected and they are published.
Do I need A2P registration before onboarding is finished?
If the client will text US contacts from a local number, yes. Register the A2P brand and campaign in the Trust Center and link the number to the approved campaign before any SMS workflow goes live. The A2P registration checklist on this site covers each step.
Should the client connect their own Stripe account?
Yes, in most cases the Stripe account should belong to the client, because the money from their customers lands there. Each sub-account connects to one Stripe account at a time, under Payments, Integrations, and payments made in Stripe before the connection are not imported.
What permissions should client users get?
Set the sub-account Feature Permissions first, because a user can never have more access than the sub-account. Then add each person in Settings, Users as Admin or User, set module permissions, and use Only Assigned Data for anyone who should only see their own contacts and opportunities.
Does this checklist save my progress?
Yes, in this browser only, using local storage. Nothing is sent to GHL Weekly. Use a separate browser profile per client, or print or download the PDF for each one, if you onboard several clients at once.
Sources
Checked against HighLevel docs on 30 Oct 2026. Every link below was opened that day. How I check facts is on the editorial standards page.
- HighLevel Help Center: Create New Sub-Account Using a Snapshot help.gohighlevel.com
- HighLevel Help Center: Load a Snapshot Into an Existing Sub-Account help.gohighlevel.com
- HighLevel Help Center: Snapshots Overview help.gohighlevel.com
- HighLevel Help Center: Business Profile Settings help.gohighlevel.com
- HighLevel Help Center: Business Physical Address & Time Zone help.gohighlevel.com
- HighLevel Help Center: Business Information: Type & Registration help.gohighlevel.com
- HighLevel Help Center: Manage Feature Permissions for Subaccounts help.gohighlevel.com
- HighLevel Help Center: Manage Sub-Account User Roles & Permissions help.gohighlevel.com
- HighLevel Help Center: How to Purchase and Set Up a Phone Number help.gohighlevel.com
- HighLevel Help Center: Identity Verification for Phone Number Purchases (US/CA/PR) help.gohighlevel.com
- HighLevel Help Center: What is A2P 10DLC: Brand and Campaign Registration help.gohighlevel.com
- HighLevel Help Center: How to Set Up a Dedicated Sending Domain (LC Email) help.gohighlevel.com
- HighLevel Help Center: Email Sending Guide: Email Best Practices & Email Warm Up help.gohighlevel.com
- HighLevel Help Center: How to Set Up a Booking Calendar help.gohighlevel.com
- HighLevel Help Center: Calendar Availability: Weekly Working Hours & Date-Specific Hours help.gohighlevel.com
- HighLevel Help Center: How to Create Pipelines help.gohighlevel.com
- HighLevel Help Center: How to Create a Contact Form help.gohighlevel.com
- HighLevel Help Center: HighLevel A2P Opt-In Compliance help.gohighlevel.com
- HighLevel Help Center: Guided Form Based Setup for Conversation AI help.gohighlevel.com
- HighLevel Help Center: How to Create and Set Up a Conversation AI Bot help.gohighlevel.com
- HighLevel Help Center: Integrate Google Business Profile with HighLevel help.gohighlevel.com
- HighLevel Help Center: Step-by-Step Guide to Facebook Integration help.gohighlevel.com
- HighLevel Help Center: Connect Stripe to HighLevel help.gohighlevel.com
- HighLevel Help Center: How to Set Up Root Domain/Subdomain for Funnels/Websites help.gohighlevel.com
- HighLevel Help Center: Getting Started with Workflows help.gohighlevel.com
- HighLevel Help Center: Missed Call Text Back: Overview & Setup help.gohighlevel.com
- HighLevel Help Center: Subaccount Dashboard Page: View or Edit help.gohighlevel.com
- HighLevel Help Center: How to Promote and Customize Your Whitelabel Mobile App help.gohighlevel.com
- HighLevel Help Center: SubAccount Launchpad help.gohighlevel.com