Set opening hours, party sizes, table rules, booking duration and any deposit or card policy.
Home
Restaurant onboarding
Bring your bookings and guest history across with care.
Start with an export from your current process, review what is ready to move and approve the information before it reaches your restaurant’s live booking operation.
01Stage export
02Review records
03Approve import
01Bookings and guest information02Consent reviewed separately03Live data approved by your team
From first review to first service
A move your whole team can follow.
Review your starting point
Identify available exports, future bookings and useful guest records.
Restaurant: share the current process. Findsy: review the proposed scope.Prepare and check the records
Map fields, identify duplicates and flag records that need a decision. Review marketing permission separately.
Restaurant: resolve uncertainties and approve the sample.Configure the restaurant
Prepare tables, opening hours, party sizes, durations and booking policies.
Restaurant and Findsy: agree the setup responsibilities.Rehearse a service
Check sample bookings and guest actions. Walk through staff roles and the service routine.
Restaurant: confirm that the workflow fits the team.Agree the changeover
Review final counts, capture changes since the export and agree when the new booking route becomes active.
Restaurant and Findsy: confirm the launch checks and timing.Review the launch
Check the first services and agree which feedback or follow-up workflows to introduce next.
Confirm training, support arrangements and any additional work in the setup scope.
01 / Start with what you have
Your current process is the starting point, not a barrier.
Bring the booking and guest information that is useful for service into one review. Findsy can help you map an export from your previous process or a working spreadsheet.
Card credentials, passwords and unclear marketing permission should not be treated as data to move into the new guest relationship.
Agree the practical details
Clear responsibilities before the first live booking.
The onboarding conversation should confirm what is included, what your team owns and what needs extra preparation.
What happens to existing bookings?
Agree the source export, date range and cutover time. Check missing fields and duplicates, review a sample, then reconcile approved records before the new booking link goes live.
Can every guest record be used for marketing?
No. Keep contact details separate from marketing permission. Review the available consent evidence; a booking history alone is not treated as permission to send promotions.
Who configures and trains the team?
Agree who owns the floor plan, service times, booking rules and staff access. Include a practice service and training responsibilities in the setup scope.
What support is available during changeover?
Confirm the contact route, coverage hours and escalation arrangements before launch. Do not assume round-the-clock support or a fixed migration deadline.
What about integrations and payment details?
List the connections you rely on and confirm compatibility individually. Existing card credentials and passwords are not part of a standard record import; agree how protected bookings will be handled.
03 / Build the service workflow
Set up the restaurant around the service you actually run.
Prepare the direct booking page and customer portal around the actions guests should be able to take.
Choose the campaigns, feedback routes and repeatable journeys you want to introduce after service is working smoothly.
Plan the right starting point
Bring your current booking process. We will help map the move.
Start with the details that matter to your restaurant: your current booking journey, table setup, guest information and the changes you want to make first.