Managed switching / A clear next chapter

Make the move.
Keep service moving.

Bring your current booking process. Build a practical changeover plan around your future reservations, your team and the first service in Findsy.

Configuration, supported imports, training and launch checks — agreed before you go live.

YOUR NEXT CHAPTERFrom the current book
to the first service.
  1. 01
    Prepare the move

    Scope, records and restaurant setup.

  2. 02
    Prove the workflow

    Reviewed imports and a team rehearsal.

  3. 03
    Launch with a plan

    Reconciliation, support and a review point.

Protect the booking book

Review and reconcile future reservations.

Prepare the people

Practise the work your team will do.

Know the next step

Agree owners, checks and support.

Your changeover roadmap

A move your whole team can follow.

Choose your starting point. Each stage has a purpose, the people involved and a check before moving on. Timing follows the scope and readiness of your restaurant.

Start with a reviewed export.

Bring a sample and the names of the systems you rely on. Supported fields, export access and compatibility are confirmed before the final migration.

  1. 01

    Plan

    Review a sample export, future reservations, guest records and separate permission evidence. Identify the public links and connections involved in your changeover.

    Who is involved
    Your launch owner + Findsy setup contact
    Ready to move on
    An agreed source list, scope, owners and changeover sequence.
  2. 02

    Configure

    Prepare the booking page, room, table combinations, availability, party sizes and durations. Review staff roles, guest actions and communication settings.

    Who is involved
    Restaurant approves the operating setup
    Ready to move on
    Your team recognises the room and has reviewed the booking rules.
  3. 03

    Migrate

    Map supported fields and review a sample. Check duplicates and gaps, reconcile future bookings and keep guest contact details separate from marketing permission.

    Who is involved
    Restaurant approves the sample and final records
    Ready to move on
    The approved future-booking list matches the agreed source.
  4. 04

    Train

    Practise a guest booking, a permitted change and a cancellation. Rehearse arrivals, walk-ins, table progress and the handover between host and manager.

    Who is involved
    Your service lead + colleagues using Findsy
    Ready to move on
    The team can run the core workflow and knows where to raise questions.
  5. 05

    Launch

    Complete the final reconciliation, confirm readiness and change the agreed public booking links. Review the guest route and the first live service with the launch owner.

    Who is involved
    Restaurant + Findsy agree the go-live checks
    Ready to move on
    A working public booking journey and a named first-service contact.
  6. 06

    Support

    Review the first services and resolve open questions. Agree when to introduce private feedback, reviewed campaigns or the next venue’s workflow.

    Who is involved
    Named restaurant owner + agreed support route
    Ready to move on
    A review record, clear next actions and the next check-in point.
A restaurant server bringing drinks to guests gathered around a table

Prepare the room. Rehearse the welcome.

Start with the service your team knows.

Review your tables and capacity, then practise a booking, an arrival and a change. Give the team a clear first-service check before changing the public link.

The table name, dining area and four-guest capacity in a Findsy table card
The room starts with the tableCurrent product view · Example data

The handover

A named owner on each side.

Bring the working details. Agree what is supported, what needs preparation and who approves each part of the move.

Your restaurant

Bring the service you run.

  • Future bookings and the source records.
  • Your room, service times and booking policies.
  • Guest records and separate permission evidence.
  • A launch owner and the team joining training.
  • The places where your public booking link appears.
With Findsy

Build the agreed setup.

  • Review supported exports and map the fields.
  • Configure the booking and service workflow.
  • Review a sample and reconcile approved records.
  • Plan rehearsal, training and changeover checks.
  • Confirm launch support and the first-service review.
The actual fillable booking switch plan from the Findsy team toolkit

Take the plan into your meeting

A working checklist, from the first question to go-live.

Review the starting point, prepare your setup, rehearse service and agree the changeover. Use the online checks and planning notes or take the worksheet to your team.

  • Grouped actions with visible progress.
  • Space for the owner, next review and open questions.
  • A branded PDF and an editable checklist.

The first service is a review point

Go live with the checks already agreed.

Before the public link changes, confirm the approved bookings, guest journey, staff readiness and support route. After the first services, review questions with the people doing the work.

  1. Before changeover

    Reconcile the final booking list. Check links, availability and permissions. Confirm the go-live owner.

  2. During the first service

    Keep a named restaurant contact available. Record questions and use the agreed route for service-blocking issues.

  3. At the review

    Resolve open actions, adjust the working setup and agree when to introduce the next workflow or venue.

Before you switch

Ask the practical questions early.

Bring your source system, future booking picture and launch priorities. Confirm the details before committing to a changeover date.

How long does switching take?

Agree the timeline after reviewing your current process, export access, future bookings, configuration and team availability. The plan sets out the stages and readiness checks; there is no single timescale for every restaurant.

What happens to existing bookings?

Agree the source, date range and final reconciliation point. Review supported fields, check a sample, resolve gaps and reconcile approved future bookings before the new public link goes live.

Can all of our guest records be used for marketing?

Contact details and marketing permission are reviewed separately. A booking history alone is not treated as permission to send promotions. Bring the available permission evidence to the import review.

Will our existing connections move with us?

List the connections you rely on and confirm compatibility individually. Supported records, ownership, access and any separate configuration are agreed before changeover.

What should we do with the old system?

Agree the final reconciliation and access to source records before changing public links. Your restaurant remains responsible for its existing supplier agreement, cancellation arrangements and record-retention decisions.

Are migration and setup included?

Your written proposal confirms the setup and migration scope, any charges, responsibilities and commercial terms before activation. Group rollouts and additional launch cover are agreed separately.

Support around service

Know when and how to reach us.

Daily support windows

Every day, 09:30–14:30 and 17:00–22:30

UK time (GMT/BST)

Service-blocking issues

Call the support number shared during onboarding for service-blocking issues.

We aim to acknowledge support requests within one hour during staffed support windows. Resolution timing depends on the issue.

Enquiries and setup

Discuss your restaurant, configuration or the right starting point.

contact@findsy.ai ↗

Additional launch cover or support outside these windows is arranged separately.

Plan your move to Findsy

Bring your current process.
Map your next step.

Use a focused conversation to explore the booking workflow and the questions your changeover needs to answer.

Book a 15-minute demo →
  1. 01

    Review your current booking process and priorities.

  2. 02

    Explore the relevant guest and team workflow.

  3. 03

    Discuss the setup, responsibilities and next checks.