Operations
How to switch booking software without losing members, bookings or revenue
A practical migration plan for gyms, studios, clubs and academies: the data to take with you, a step-by-step checklist, a parallel run, the messages to send members and what to check on cutover day.
· 9 min read
Key takeaways
- To switch booking software without losing members, export everything first, import balances so nobody loses a session, pick a cutover date at the start of a billing cycle, and run both systems side by side for a short, defined period.
- The data that protects revenue is not the contact list. It is active memberships with end dates, packs with remaining credits and expiry, upcoming bookings, wallet and credit balances, and your invoice history.
- Members stay when the change costs them nothing: the same balance, the same booking times, and a clear message on WhatsApp telling them what to do and when.
- Keep e-invoicing continuous: decide which system issues invoices from cutover day, make sure the new one is onboarded with FATOORA, and issue refunds on old sales as credit notes that reference the original invoice.
- Request a full export from your current system before you give notice, and confirm in writing how long you keep access to it after the contract ends.
How do you switch booking software without losing members?
You switch booking software safely by treating it as a move of money and commitments, not a move of contacts. Every active membership, unused class credit, wallet balance and future booking is something you have already been paid for or promised. If those arrive intact in the new system, members barely notice the change. If they do not, the front desk spends weeks settling disputes and some members quietly leave.
The plan in this guide has five stages: export and check your data, set up and test the new system, run both systems in parallel for a short period, tell members in plain words, and close the old system on a fixed cutover day. It works the same for a gym, a pilates studio, a padel club or an academy.
What are the signs it is time to change your booking system?
Owners rarely switch because of one bad day. They switch when the workarounds around the system start costing more staff time than the system saves. These are the signs that come up most often.
- Staff keep a spreadsheet or notebook next to the system to track balances, freezes or family members it cannot handle.
- Members book or pay by sending messages to the front desk because the online flow is slow, English only or hard to use on a phone.
- Invoices are issued by hand or in a separate tool, and refunds do not produce a matching credit note.
- Local payment methods are missing at checkout, or payouts arrive late and are hard to reconcile.
- You cannot get a clean export of your own members, balances and booking history when you ask for it.
- Requests for a feature you need go unanswered, and support takes days to reply.
- Members see another venue’s name or offers inside the app they use to book with you.
What data should you export from your current system?
Export more than you think you need. A field you skip today is hard to recover once the old contract ends. Ask for spreadsheet files (CSV or Excel) rather than PDFs, because a PDF report cannot be imported.
| Data | Fields to include | Why it matters |
|---|---|---|
| Members and customers | Name, mobile number, email, date of birth or gender if you use them, join date, notes | The mobile number is usually how members sign in and receive messages, so it must be correct |
| Active memberships | Plan, start date, end or renewal date, price paid, freeze history, member pricing | A member who paid for a year must keep every remaining day |
| Packs and credits | Pack name, credits bought, credits remaining, purchase date, expiry date, which services the credits cover | Remaining credits are prepaid revenue; losing them is the fastest way to lose a member |
| Upcoming bookings | Date, time, court, class or coach, member, paid or unpaid, recurring series | Prevents double bookings and no-shows in the first weeks |
| Wallet and credit balances | Balance per member, origin of the balance (top-up, refund credit, gift), any expiry | This is money members expect to spend; agree with your accountant how it carries over |
| Family and linked accounts | Account holder, linked children or spouses, who pays for whom | Parents should not have to re-register each child |
| Waivers and signed forms | Signed waivers, health questionnaires, consent for minors, with the date each was signed | Keep a copy you control, even if the new system collects them again |
| Invoices and credit notes | Invoice number, date, customer, amount, VAT, linked refunds, the XML or PDF of each document | You will need the original invoice to refund a sale made before the switch |
| Payments and refunds | Transaction date, method, gateway reference, refunds and partial refunds | Lets you answer disputes and reconcile the last payout from the old system |
Ask for the export before you give notice
Request a full export while your account is active, check that it opens and that the totals look right, and ask in writing how long you keep read access after the contract ends. Some systems limit exports or remove access soon after cancellation.
How do you clean member data before importing it?
Imported data is only as good as the file you import. An hour spent cleaning the spreadsheet saves days of corrections at the front desk.
- Write every mobile number in full international format, with the country code, so messages and sign-in work.
- Merge duplicates: the same person often exists twice with a different spelling or an old number.
- Decide what to do with inactive members and expired packs: import them for history, or archive them in a file you keep.
- Add up remaining credits and wallet balances in the export and write the totals down. After the import, the same totals must appear in the new system.
- Pick a balance date and time. Balances in your file are true only up to that moment, so record any session used after it.
Step-by-step migration checklist
Work through these steps in order. Each one depends on the one before it, and skipping ahead is how balances and bookings get lost.
- Choose a cutover date, ideally at the start of a month or billing cycle and away from your busiest week or a public holiday.
- Name one owner for the migration on your side, usually the operations or front-desk manager.
- Export all the data listed above and keep the files in a shared folder you control.
- Set up the new system: courts, rooms or classes, coaches, opening hours, prices, packs, memberships and cancellation rules.
- Connect payments and invoicing, then run a small real payment and a refund to check the invoice and credit note.
- Import members, memberships and remaining balances, then compare the totals with the figures you wrote down.
- Recreate upcoming and recurring bookings in the new calendar, or import them if the new system supports it.
- Spot-check ten real members end to end: profile, balance, expiry, next booking, family links.
- Train front-desk staff and coaches on the daily tasks: bookings, check-in, payments and refunds.
- Send the member announcement, start the parallel run, and close the old system on cutover day.
Should you run both systems in parallel?
Yes, but briefly and with clear rules. A short parallel run lets you catch import mistakes while the old data is still in front of you. A long, open-ended one means two calendars, two sets of balances and double bookings. Agree a fixed end date before you start and tell staff exactly which system does what.
| Task | Current system | New system |
|---|---|---|
| New sales of packs and memberships | Stopped | All new sales |
| New bookings | Closed for dates after cutover | Open for all dates after cutover |
| Bookings already made before cutover | Honoured as booked | Copied in so the calendar is complete |
| Refunds on old sales | Issued where the original invoice lives | Only if your accountant agrees the reference |
| Reports and history | Read only, for lookups | Daily reports from cutover |
One rule for balances
Once balances are imported, a session is deducted in one place only: the new system. If a member uses a credit in the old system by mistake, correct it the same day in the new one.
How should you tell members about the new booking system?
Tell members early, tell them more than once, and lead with what stays the same. Send messages from the number members already know, on WhatsApp where they read them, with email as a backup. Keep each message short and in both Arabic and English if your members use both.
- Announcement, about two weeks before: we are moving to a new booking app on a named date; your membership, remaining sessions and upcoming bookings come with you; nothing to do yet.
- How-to message, a few days before: here is the link, sign in with the same mobile number, check that your balance is correct and tell us if anything looks wrong.
- Cutover day: from today, book and pay only in the new app; the old link no longer takes bookings; our team is on WhatsApp if you need help.
- Follow-up, a week later: a short reminder to members who have not signed in yet, ideally a personal message from the front desk.
Call or message your regulars and long-term members personally before the general announcement. They are the members you can least afford to confuse, and once they book on the new system, others follow.
How do you keep ZATCA e-invoicing continuous when you switch?
Under ZATCA’s Phase 2, the solution that issues your invoices must be onboarded with FATOORA. Simplified invoices to consumers are reported within 24 hours, and standard invoices to companies are cleared before you share them. When you change systems, the question is not only which app takes bookings, but which solution issues the invoice for each sale from cutover day.
- Decide the invoicing route for the new system before cutover, whether through your accounting system or a connected e-invoicing provider, and confirm it is onboarded with FATOORA.
- Make sure no sale is invoiced twice or not at all: every sale before the cutover time belongs to the old system, every sale after it to the new one.
- Imported pack credits and membership days were already invoiced when they were sold. Do not issue a new invoice for them in the new system.
- A refund on a sale made before the switch needs a credit note that references the original invoice. Agree with your accountant where that credit note is issued.
- Keep your exported invoice files and the old system’s records safe, and ask your adviser how long you need to keep them.
Check with your accountant
This section is practical guidance, not tax advice. Your accountant or tax adviser should confirm how carried-over balances, credits and refunds on old sales are recorded for your venue.
Cutover day checklist
Cutover day is a normal working day with a short list of extra checks. Start early and keep the old system open for lookups only.
- Stop new sales and new bookings in the old system, and replace its booking link on your website, social profiles and WhatsApp replies.
- Take a final export of balances and bookings at the cutover time and apply any changes since your import.
- Compare total remaining credits, wallet balances and active memberships with the old system one last time.
- Check that today’s and tomorrow’s bookings appear on the new calendar, with the right coach and court or room.
- Run the first real payment of the day and confirm the invoice is issued and the payment appears in reports.
- Send the cutover message to members and keep someone on WhatsApp all day to answer questions.
- At closing, review the day: bookings taken, payments, check-ins and any member who reported a wrong balance.
What should you watch in the first weeks after switching?
- Members who have not signed in yet: message them personally before their next renewal or pack expiry.
- Balance complaints: fix each one the same day and note the cause, so you can spot a pattern in the import.
- Daily sales and invoice counts: they should match payments received, with no gaps.
- Renewals: the first renewal cycle on the new system is the real test of whether members stayed.
- Staff questions: collect them in one place and answer them in a short refresher session.
Only cancel the old subscription once the parallel period has ended, the final payout from the old system has been reconciled and you hold every export you need.
How does AskFlow help venues switch?
The AskFlow team handles the migration with you, and venues typically run their first real booking day on AskFlow within a week of deciding to switch.
- A self-serve import for customers and package balances from a spreadsheet, plus team help moving memberships, remaining package credits and upcoming bookings.
- Setup of courts or classes, prices, packages, memberships, payments and WhatsApp alongside your team, followed by training for front desk, coaches and managers.
- ZATCA-compliant invoices and credit notes issued automatically, through your accounting system or on their own.
- Booking confirmations and reminders on WhatsApp through the official WhatsApp Business API, in Arabic or English.
- A booking page under your own brand and domain, family accounts, and refunds to the original payment method or as venue credit.
- Support from people in the region on WhatsApp, in Arabic and English, and no long-term lock-in.
Common questions
How do I move my gym members to new software without losing their sessions?
Export members with their active memberships, remaining pack credits and expiry dates, write down the totals, import them into the new system and check that the same totals appear. Then spot-check a few real members before you tell anyone. From cutover, deduct sessions in the new system only.
When is the best time to change booking systems?
At the start of a month or billing cycle, outside your busiest season and away from public holidays. Starting with a cycle means new memberships and renewals begin cleanly in the new system, with fewer balances to carry over.
Should I keep my current system running after I switch?
Keep it for lookups during a short, fixed parallel period, but stop new sales and new bookings in it from cutover day. Cancel the subscription only after the parallel period ends, the last payout is reconciled and you hold every export you need.
What do I tell members when we change the booking app?
Lead with what stays the same: their membership, remaining sessions and bookings move with them. Then give the date, the new link and one instruction, such as signing in with the same mobile number. Send it on WhatsApp from the number they know, repeat it on cutover day and follow up a week later.
What happens to e-invoices and refunds for sales made in my old system?
Sales made before the switch were invoiced by the old system, so do not invoice them again. A refund on one of those sales needs a credit note that references the original invoice, so keep your invoice exports and agree with your accountant where those credit notes are issued.
Does AskFlow help with data migration?
Yes. There is a self-serve import for customers and package balances, and the team handles moving customers, memberships, remaining package credits and upcoming bookings with you. Venues typically run their first real booking day within a week of deciding to switch.
Built with you
Ask for it. We build it.
Most booking software asks you to change how you run your business. We work the other way around. Your requests go straight to the team that builds Flow, and many of the features clubs use every day started as one venue’s idea.
- Features shipped in the last 3 months
- 600+
- New releases
- Weekly
Let us postpone a fixed session more than once
Show product photos on the POS
Create a discount while booking
Give each location its own contact number
Add custom fields to customer exports
Live for your venueFilter the WhatsApp inbox by location
Live for your venueShow coach utilization in reports
Live for your venueRun bookings, payments and members on your own brand.
See how clubs, studios and academies run on AskFlow, with a branded app, WhatsApp booking and e-invoicing built in.