A checklist for moving booking software

A practical acceptance checklist for customers, services, future appointments and the booking links already in circulation.

6 min readYouzse TeamUpdated

Choose a person responsible for the move, a working date and a clear definition of success. Obtain the files you need while the old account is accessible. Test a representative sample, reconcile future appointments and decide which system owns new bookings and reminders before changing the public booking link.

Start with an inventory of records and settings

List customers, services, staff, future appointments, unpaid invoices and any business-specific records you need. Keep account settings on a separate list: working hours, breaks, deposits, communication preferences, access roles and booking rules may need to be configured again.

Record each file’s source, date, contents and intended destination. A contact export is not evidence that appointment history, invoices or preferences were included. Keep an unchanged original and work from a copy when correcting column names or values.

Choose samples that can reveal a mistake

SampleAcceptance check
Customer with more than one contact fieldThe intended email and phone values reach the right fields.
Service with a nonstandard durationThe booking menu reserves the actual service and reset time.
Appointment with a named staff memberThe customer, person, service, date, time and duration match.
Cancelled or completed appointmentIt is not treated as a new confirmed future booking.
Invoice with a partial payment, if supportedIts identity, total, remaining balance and collection responsibility agree.
Business-specific recordThe vehicle, class, pass or other record has a verified setup path rather than an assumed import.

Check dates, amounts and omitted fields in the preview

Spell out an example date so you can distinguish day-first and month-first files. Compare the appointment as it appears in the business time zone with the original diary. For an amount, confirm the currency and whether the file uses whole currency units or minor units before approving a mapping.

Keep a list of columns that are ignored or have no destination. Decide whether each one is unnecessary, belongs in an archive or needs another supported process. A file being accepted does not establish that every piece of information has moved.

Reconcile the forward diary

  • Compare confirmed appointments for the next working period one by one.
  • Check staff hours, leave, breaks and blocked time before opening availability.
  • Match each appointment to its customer, service, person, start time and duration.
  • Check deposits or balances separately and agree where any remaining payment will be collected.
  • Record changes made after the export so they can be reconciled before launch.
  • Name the authoritative diary and the person responsible for recording changes during the move.

Give each reminder and payment one owner

Before turning on new messages, inspect the confirmations and reminders already scheduled in the old system. Decide which system will send each upcoming message, and test the new message with a controlled booking. Check the booking link, contact method and actual appointment details.

Treat saved cards, subscriptions, deposits, invoices and credit balances as separate questions. A customer row or invoice export does not establish that its payment method or obligation has transferred. Ask the providers what is supported and reconcile the actual records before relying on the new collection process.

List the website buttons, social profiles, email signatures, printed cards and QR codes that point to the old booking page. Test the replacement on a phone while signed out of the staff account. Check that it opens the correct business, service menu and location.

Keep a customer-facing explanation of how to book and how to ask about an existing appointment. A new booking link does not change a reservation someone already made, so confirm what will happen to those appointments rather than leaving the customer to guess.

Agree when the move is complete

  • The sample records pass their acceptance checks and unresolved items have an owner.
  • Staff can find the next working day without relying on the person who performed the import.
  • A customer can book, receive a correct confirmation and request a change through a monitored route.
  • Messages and payments have a documented owner during the handover.
  • Required exports and archives remain accessible to the right people.
  • The public booking links have been checked and the old booking route is handled deliberately.

Using this checklist for a Youzse move

Youzse has named import profiles for some sources and manual column mapping for others. Check the guide for your actual source and the file you have, including records that need a separate setup process. Use a preview to validate the mapping rather than treating the source name as proof that every field will be understood.

The checklist can be used internationally. Product availability, supported currencies and local payment arrangements remain separate acceptance checks; confirm that the destination can serve your business before committing to a move.

Agree what happens if the cutover check fails

Issue foundDecision to record
Wrong future appointmentKeep new availability closed while the source and imported record are compared.
Missing fieldIdentify the required supported correction or archive before proceeding.
Duplicate messagePause the relevant sending route and give the next message one owner.
New work during cutoverKeep a change log so accepted bookings and receipts can be reconciled.

Keep one authoritative diary during a delayed launch

If a sample appointment arrives under the wrong staff member, importing the same file again may create another problem rather than fix the mapping. Record the mismatch, preserve the original export and confirm the supported correction process before trying again.

Name the diary staff should use while the move is paused, and record new bookings, edits and payments made since the export. Reconcile those changes before releasing the replacement. A rollback plan is an agreed operating procedure, not an assumption that the provider can undo every import with one action.

Clear answers before you switch

The details that usually slow down a move: setup, pricing, bookings, records and how Youzse fits into your day.

Inventory the records you need, including customers, services, future appointments and any unpaid invoices or business-specific history. Confirm what the actual files contain and keep settings, payment arrangements and archived records on separate checklists.

We value your privacy

Cookies keep Youzse running, improve the platform and help deliver relevant content. Read our privacy policy and cookie policy.