If Practice Hub and GoHighLevel are connected in your clinic, the sync between them decides whether every reminder, recall and reactivation message is right. When it stops, nothing crashes: messages keep going out, built on data that is days or months old. This guide shows the symptoms to look for, a 25-minute audit you can run today with what to check in each system, the usual causes, what you can fix yourself and how to stop it happening again. It is written for the clinic owner or manager, not for a developer.
A sync failure is quiet. GoHighLevel keeps the contacts and appointments it already has, and every workflow that runs on them keeps working. Reminders go out, birthday emails go out, the inbox fills with replies. From the front desk, everything looks normal.
What has stopped is the flow of new information. Appointments booked, moved or cancelled in Practice Hub no longer reach GoHighLevel, and new patients never arrive. One clinic we spoke to found out that its sync had stopped updating four months earlier. Emails had gone out the whole time, so nobody suspected anything, but the patient data behind them had been frozen since the day it broke.
That is why the right question is not "is it on?" but "is the data in GoHighLevel the same as the data in Practice Hub, today?" The rest of this guide answers it.
If you recognise two or more of these, run the audit below this week.
| What you notice | What it usually means |
|---|---|
| A patient gets a reminder for an appointment they cancelled or moved | Changes in Practice Hub are not reaching GoHighLevel, or arrive too late |
| New patients from this week are not in GoHighLevel | The connection has stopped creating contacts |
| The reactivation list is empty, or includes people who came in last week | Last-visit data is missing or out of date |
| The diary in Practice Hub and the calendar in GoHighLevel do not match | Appointments are being edited in two places, or the sync is behind |
| Fields such as last visit, package or practitioner are empty on recent contacts | Those fields are not mapped, or stopped being filled |
| The same patient appears twice in GoHighLevel | Duplicates created by a different phone number or email |
| Appointment times in messages are an hour out | Time zone settings differ between the two systems |
You need access to both systems, a test patient you can book and cancel (yourself or a staff member) and a notepad. Do the steps in order; each one tells you something different.
In Practice Hub: book an appointment for your test patient a few days out, and note the time you saved it.
In GoHighLevel: open the test contact and check the appointment and the conversation. Note how long it took to appear, and whether the date, time, practitioner and appointment type are correct. Also check whether the confirmation message went out.
If nothing has arrived after 20 minutes, the sync is either very slow or not working. Keep going: the next steps tell you which.
In Practice Hub: move the test appointment to another day. Wait, then cancel it.
In GoHighLevel: check that the new time replaced the old one and that the cancellation stopped the reminder workflow for that appointment. A cancellation that does not stop the reminder is the symptom patients notice first.
In Practice Hub: note how many active patients you have, and how many new patients you registered in the last 30 days.
In GoHighLevel: filter the contacts that come from the integration (by the tag or source your connector uses) and count them, then count the ones created in the last 30 days. The totals will rarely match exactly, because leads and old patients complicate the picture. The new patients of the last 30 days should match almost one for one. A big gap there is the clearest sign of a stopped sync.
Pick five patients who came in this week. In GoHighLevel, open each one and look at the last visit or next appointment fields and the contact's activity. If the last change on all five is weeks old while they were in clinic three days ago, you have found roughly the date the sync stopped. Write it down: it tells you how far back the clean-up has to go.
On one of those contacts, list the patient fields that are filled from Practice Hub. Then compare them with what your workflows need: last visit date for reactivation, next appointment for recall, package or plan for care-plan follow-ups, practitioner for personalised messages. A workflow that depends on a field the connector does not fill will either never fire or fire for everyone.
Ask whoever set up the connection, or check its settings: if the sync stops, who is told, and how? If the honest answer is nobody, the next failure will be found the same way as the last one, by a patient.
Connectors are built in different ways, so the exact cause depends on the integration you use. These are the failure modes we see most often, in roughly the order we check them:
| Problem | Can you fix it yourself? |
|---|---|
| Expired or lost authorisation | Usually yes: reconnect it with an account that belongs to the clinic, not to one person. Then check what was missed while it was down. |
| Time zones | Yes: set the same time zone for the clinic, the GoHighLevel account and each user. |
| A few duplicates | Yes: merge them in GoHighLevel, keeping the contact linked to Practice Hub. |
| Renamed or deleted fields | Sometimes: if you know the mapping, recreate the field. If not, ask whoever built it. |
| Workflows reading empty fields | Partly: you can find them, but rebuilding them around the fields you do have takes time. |
| Months of missed changes | Get help: the data has to be brought back in without sending a wave of wrong messages. |
| A connector that only brings a few fields | No: that is how it was built. You need a different integration. |
Before you reconnect anything after a long outage, pause the workflows that send to patients: reminders, recalls and reactivation. When the data comes back in, those workflows can fire for every change at once, and patients get messages about appointments from months ago.
We built QuiroHiro, our platform for chiropractic clinics built on GoHighLevel, partly because of this problem. It includes our own integration with Practice Hub, built in-house and maintained by our team, and QuiroHiro is an official Practice Hub integration partner. It brings 200+ fields for each patient (appointments, visit history, packages, spend, referrals and preferred language), checks for changes about every 30 seconds, and keeps Practice Hub as the only diary: cancellations and reschedules made from a message go through Practice Hub. Because our team built it and maintains it, there is always someone responsible for keeping it working.
You can see how QuiroHiro's Practice Hub and GoHighLevel integration works, or what switching from your current GoHighLevel setup involves. For the bigger picture of what a clinic should automate and how to decide between doing it yourself and hiring help, read our guide to GoHighLevel for chiropractors.
Sources and References:
• Calls with chiropractic clinics in the UK, Australia and New Zealand that run Practice Hub and GoHighLevel (October–November 2026), described anonymously
• QuiroHiro integration work with Practice Hub and GoHighLevel (2025-2026)
Prefer to have it done for you? See our Automations for Chiropractors service for chiropractic clinics.