UnitAlloy

Migration · Appointments

Move Calendars Without Losing Active Appointments

Calendar migration isn't only configuration. Booked appointments, staff availability, buffers, reminders, cancellations and booking URLs all have to keep working the day you switch.

Plan Your Calendar Migration
  1. 1Source calendar
  2. 2Calendar mapping
  3. 3Staff mapping
  4. 4Service mapping
  5. 5Active appointment migration
  6. 6Sync validation
  7. 7Cutover

Active appointments are the risk

One booking carries six dependencies.

Settings can be rebuilt. A customer who arrives at the wrong location, at the wrong hour, with no reminder, is the real failure.

  1. Existing booking
  2. Customer
  3. Assigned staff
  4. Location
  5. Timezone
  6. Reminder
  7. New calendar

Cutover options

Three ways to switch. Each has a trade-off.

The right choice depends on booking volume, how far ahead customers book and how many locations switch at once.

Hard cutoverSwitch every booking link on one date.Fast, but any mapping error affects all locations at once.
Parallel runBoth calendars live for a short window.Safer, but double-booking risk if availability isn't synced.
Future bookings onlyNew bookings go to GHL; old ones finish in the source.Clean, but two systems to check until the backlog clears.

Validate before switching links

Booking links change last.

Website buttons, emails and ads keep pointing at the old calendar until every check passes. How calendars should be structured after the move is on GoHighLevel calendars; the wider plan on GoHighLevel migration.

  • Staff availability
  • Timezone
  • Reminders
  • Calendar ownership
  • Booking links
  • External sync

Next step

Plan your calendar migration.

Tell us which booking tool you use today, how far ahead customers book and how many calendars each location runs.

Plan Your Calendar Migration