How do I move client onboarding from Google Forms and DMs into GoHighLevel?

Save first, change nothing in the originals, and archive rather than delete. Before you touch GoHighLevel, export:

• Google Form response sheets, as CSV.
• Your client list with start dates, plan and payment status.
• Your Stripe customer and subscription list.
• Your DM lead list: handle, phone, status and the date of the last message.
• Any DM threads where you agreed custom pricing or made a commitment.
• Existing contracts and program files.
• If your coaching app is changing too: videos, files, exercises and meals. Some coaching apps have no import, so check yours and plan to rebuild by hand if it cannot import.

Check the row count of every export against the source, and keep the original untouched.

• Build your pipeline, stages and custom fields first. HighLevel's import maps to fields and stages that already exist; it does not create pipelines for you.
• Tag every existing client in the CSV, and exclude that tag from your welcome and nurture workflows.
• Leave the import screen's option to add contacts to a workflow switched off.
• Use one phone format. HighLevel recommends E.164, for example +16475550123.
• Run a small test batch first. HighLevel says completed imports have no one click undo.
• To place people in pipeline stages, use HighLevel's opportunities import with a stage column, or set stages by hand for a short list.
• Carry your consent records across. Under Canada's anti spam law (CASL) the sender has to be able to prove consent, so keep how and when each person agreed to hear from you. This is general information, not legal advice.

• Moving active clients mid program before the new flow is tested.
• Cutting over with no dummy client test.
• Rebuilding every old long form instead of cutting it down.
• Leaving the old form live, so leads land in two places.
• Not tagging existing clients, so automations message people who joined months ago.
• Tag sprawl and typos in the data model.
• Putting nurture and reminders in one workflow, so messages collide.
• Importing contacts with no record of consent.

Adam sees these in his own builds and cleanup work. None of them is about the software. They are about order.

Coaches with no stable offer or no regular leads, coaches in the middle of a launch, and coaches with nobody who owns the pipeline day to day. Fix those first; the switch will still be there.

If CoachStack does it: The build runs inside your own GoHighLevel account over a 60 day window: discovery days 1 to 3, architecture days 4 to 8, build days 9 to 21, QA days 22 to 28, and handoff days 29 to 60, followed by a 30 day support window. First workflows go live in weeks 1 to 3. If you do it yourself, the honest answer is that it depends on your spare hours, which is why the order above matters more than the speed.