Switch booking systems with a defined migration plan

Agree what moves, what stays in the old system and how the first live booking will be checked.

The difficult part of a switch is often responsibility rather than data volume. If an old booking changes after the new system starts, staff need to know where to update it and which record is authoritative.

Define the boundary first

List active offers, upcoming bookings, customer records, outstanding payments and historical material you need to retain. Separate items to import from records that remain in the previous system or an archive. Import support does not imply that every field, attachment or historic transaction can be moved unchanged.

Provide a representative export early. Check field mapping, duplicate handling and the meaning of statuses before agreeing a full import. Confirm who can resolve ambiguous records and how the result will be reviewed.

Launch one complete path

Configure a representative offer with dates, capacity, prices and required participant information. Connect the supported payment setup, review messages and test the customer journey on a phone. Staff should then find the resulting booking, plan it and complete the relevant report.

Use Live Preview for supported catalogue and booking drafts. Shared Pricing Modes simplify common price rules. AI-assisted setup is available with the required configuration; your team reviews its drafts before publication.

Prepare the team and the changeover

Give each role the appropriate access and a short rehearsal of its own tasks. Decide when new bookings move to the new system, how old obligations are handled and whom staff contact if an exception occurs. Avoid maintaining two competing plans without a named owner.

There is no universal one-day migration promise. Timing depends on scope, source-data quality, payment setup and the school's availability to review. Agree the actual plan before setting the launch date.

See setup and import for preparation and pricing for optional assistance. The aim is a verified first workflow that the team can maintain, then a controlled expansion.

How does this work at your school?

Bring an everyday task from your school. We’ll show you how it could work in TIDEFORCE.

Request a demo →