GoHighLevel Guide

Practice Hub and GoHighLevel Sync Not Working? A 25-Minute Audit for Clinics

QuiroAds logo
Sergio Argul
November 21, 2026
•
9 min read

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.

Why a broken sync goes unnoticed

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.

Symptoms: how a broken sync shows up

If you recognise two or more of these, run the audit below this week.

What you noticeWhat it usually means
A patient gets a reminder for an appointment they cancelled or movedChanges in Practice Hub are not reaching GoHighLevel, or arrive too late
New patients from this week are not in GoHighLevelThe connection has stopped creating contacts
The reactivation list is empty, or includes people who came in last weekLast-visit data is missing or out of date
The diary in Practice Hub and the calendar in GoHighLevel do not matchAppointments are being edited in two places, or the sync is behind
Fields such as last visit, package or practitioner are empty on recent contactsThose fields are not mapped, or stopped being filled
The same patient appears twice in GoHighLevelDuplicates created by a different phone number or email
Appointment times in messages are an hour outTime zone settings differ between the two systems

The 25-minute sync audit

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.

1. Book a test appointment (5 minutes)

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.

2. Move it, then cancel it (5 minutes)

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.

3. Count active patients against contacts (5 minutes)

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.

4. Check when five contacts were last updated (5 minutes)

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.

5. List the fields that arrive (3 minutes)

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.

6. Ask who gets alerted (2 minutes)

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.

The usual causes

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:

  • The connection expired or lost its authorisation. Integrations run on a login or an authorisation granted by a person. If that person left the clinic, changed their password or lost their access, or the authorisation simply expired, the connection can stop without an obvious error.
  • Custom fields were renamed or deleted. Someone tidied up the fields in GoHighLevel, or in the connector's mapping, and the data now has nowhere to go.
  • Workflows depend on fields that are no longer filled. The sync works, but a workflow built a year ago reads a field the connector stopped writing to, so the reactivation or recall list quietly empties.
  • Duplicates by phone or email. A patient registered with a mobile number in Practice Hub and filled a Meta form with a landline or a different email. Now there are two contacts, and the history is split between them.
  • Time zones. The clinic, the GoHighLevel account and the users in it are not all set to the same time zone, so appointment times in messages are off by an hour, often only after a daylight saving change.
  • A connector that copies only a few fields, on a schedule. Nothing is broken, but the connector was only ever built to bring name, contact details and the next appointment at intervals. Changes made between runs arrive late, and the data your segments need was never there.
  • Two diaries. Appointments are being created or changed in GoHighLevel as well as Practice Hub, so the two drift apart even when the sync itself works.

What you can fix yourself, and when to get help

ProblemCan you fix it yourself?
Expired or lost authorisationUsually 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 zonesYes: set the same time zone for the clinic, the GoHighLevel account and each user.
A few duplicatesYes: merge them in GoHighLevel, keeping the contact linked to Practice Hub.
Renamed or deleted fieldsSometimes: if you know the mapping, recreate the field. If not, ask whoever built it.
Workflows reading empty fieldsPartly: you can find them, but rebuilding them around the fields you do have takes time.
Months of missed changesGet help: the data has to be brought back in without sending a wave of wrong messages.
A connector that only brings a few fieldsNo: 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.

How to stop it happening again

  1. Keep one diary. Book, move and cancel only in Practice Hub, and let GoHighLevel react. If patients change appointments from messages, the change has to end up in Practice Hub.
  2. Make the connection belong to the clinic. Authorise it with a clinic account, and write down who set it up and how to reconnect it.
  3. Get an alert when it stops. Ask whoever maintains your connector for a notification when the sync fails. If it cannot do that, the monthly check below is your alarm.
  4. Do a 15-minute check every month. Steps 1, 3 and 4 of the audit: one test appointment, last month's new patients, five recent contacts. Put it in someone's calendar on the first Monday of the month.
  5. Change fields with care. Before renaming or deleting a field in GoHighLevel, check which workflows and which parts of the mapping use it.

How we solve it: QuiroHiro

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.

Frequently asked questions

How do I know if my Practice Hub and GoHighLevel sync is working?
Book a test appointment in Practice Hub and check that it appears in GoHighLevel with the right time, practitioner and type. Then cancel it and check that the reminder stops. Finally, compare the new patients of the last 30 days in both systems: they should match almost one for one.
Why is my GoHighLevel still sending messages if the sync is broken?
Because GoHighLevel keeps the contacts and appointments it already has, and workflows keep running on them. A broken sync stops new information from arriving; it does not stop messages. That is why a failure can go unnoticed for months.
Why did a patient get a reminder for an appointment they cancelled?
Either the cancellation did not reach GoHighLevel, it arrived after the reminder was sent, or the appointment was cancelled in one system and not the other. Check the sync with a test cancellation, and make sure appointments are only changed in Practice Hub.
Why is my reactivation list empty in GoHighLevel?
Usually because the field the list depends on, such as last visit date, is not filled by your connector or stopped being filled. Open a few recent contacts and check whether that field has a value and when it was last updated.
Should I pause my workflows before reconnecting the sync?
Yes, after a long outage. Pause reminders, recalls and reactivation, reconnect, check that the data looks right, and only then switch the workflows back on. Otherwise patients can get a burst of messages about old appointments.
How often should I check the sync?
Once a month is enough for most clinics, plus any time a patient mentions a wrong reminder. The check takes about 15 minutes: one test appointment, last month's new patients and five recent contacts.
How fast should changes in Practice Hub reach GoHighLevel?
Fast enough that a reminder never goes out for an appointment that has already moved. Many connectors run on a schedule; QuiroHiro's integration checks for changes about every 30 seconds.
Who should I contact if my sync stops?
Whoever set up or maintains your connector. If nobody owns it, that is the first thing to fix: an integration nobody maintains will break again. QuiroHiro's Practice Hub integration is maintained by our team.

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)

Share this research
QuiroAds logo