Practical operating guide
How to retire an old booking calendar without losing appointments
By ByTomorrow · Published
The new booking link works, but customers still have appointments and rescheduling links tied to the old calendar. Removing the old calendar can affect more than future availability.
Retirement needs a record of what still depends on the calendar. A replacement link alone does not move appointments, reminders or staff responsibility.
Diagnosis
Separate stopping new bookings from deleting records
Deletion can include the appointments
HighLevel's calendar restoration documentation states that deleting a calendar also deletes associated appointments. Treat deletion as a separate decision after reconciliation, not as the first step in changing the booking link.
Links survive outside the website
Old links may remain in confirmation messages, staff signatures, QR codes, reminder templates and customer bookmarks. Inventory the places you control and define what customers should see when they reach an old entry point.
External sync has its own behavior
HighLevel documents linked and conflict calendars separately and describes resyncing upcoming appointments after connection changes. Inspect the actual appointment records and external calendar results. A changed connection is not proof that every dependency migrated.
Retirement worksheet
A calendar migration checklist with a reconciliation record
Inventory existing appointments
Record old calendar identifier ___; future appointment identifiers ___; date, time and time zone ___; assigned staff ___; current status ___; recurring-series relationship ___; reminder dependencies ___. Use an authorized export or report and protect customer details.
Choose a disposition per appointment
Mark each future appointment remain on old calendar, move through a supported process, or needs review. Name the owner of every unresolved case. Do not cancel and recreate customer bookings merely to make the old calendar look empty.
Map the dependencies
List booking links, embeds, workflow triggers, reminders, confirmation and rescheduling links, staff assignments and external sync settings. For each record current target ___; intended target ___; change owner ___; test evidence ___. Keep appointment-specific links separate from links for new bookings.
Prepare the replacement
Test an allowed slot, an occupied slot, a new test booking, rescheduling and cancellation through approved test records. Verify staff ownership and any external calendar write. Remove or clearly mark test records under the agreed cleanup process.
Cut over new inquiries
At the owner-approved time, update the inventoried new-booking entry points and verify their destinations. Use the provider-supported method for stopping new bookings on the old calendar while preserving records that must remain. Confirm that behavior before applying it.
Reconcile before retirement
Match every original future appointment to its final location or documented disposition. Confirm its assigned owner and necessary customer actions. Retain the old calendar while appointments or links still depend on it. Approve any final deletion separately, with verified recovery limitations.
Use the worksheet
Put it into practice
Freeze the migration inventory
Capture the appointment and dependency list at the agreed cutover point, and define how new changes will be reconciled while migration is in progress.
Rehearse with synthetic appointments
Test the exact provider-supported procedure, including reminders and rescheduling. Do not assume an exported appointment automatically retains those relationships when imported elsewhere.
Switch entry points and inspect results
Verify controlled website links and templates, then read back the appointment records. Escalate unmatched appointments instead of declaring the migration complete.
Close with an owner sign-off
Record unresolved links, remaining appointments, retention decisions and any deletion approval. A calendar is retired only when the agreed obligations and dependencies have a verified home.
Questions
Straight answers.
No. First reconcile existing appointments and dependencies. The replacement accepting a new booking does not prove old appointments or rescheduling links survived.
No. HighLevel documents limits around calendar restoration. Verify the current behavior in your account and preserve an authorized recovery plan before a destructive change.
No. HighLevel documents a group-deletion choice that can retain calendars and appointments. Read the exact confirmation and verify what it affects before acting.
Sources and further reading
- HighLevel calendar restoration
Supports that calendar deletion affects associated appointments and restoration has documented limits.
Checked .
- HighLevel linked and conflict calendars
Supports distinct calendar connection roles and upcoming-appointment resync behavior after connection changes.
Checked .
- HighLevel calendar group deletion
Supports the distinction between deleting only a calendar group and deleting its calendars and appointments.
Checked .
Start with the future-appointment inventory
Bring the old calendar, proposed replacement and the list of unresolved dependencies to a workflow review before changing customer access.
Discuss your workflow