Migration guide
Switch from Skedda when the calendar stops being the whole business
Venues usually leave Skedda not because scheduling broke, but because everything around it multiplied: a spreadsheet for members, a second app for payments, paper for GST. Moving to a venue OS collapses the stack. The migration is light — Skedda holds bookings, not deep business data, so there's less to move than you'd think.
The 48-hour migration path
- Hours 0–4: model courts in Cuetronix with sport pricing — peak/off-peak hours, doubles/singles rates, member overlays.
- Hours 4–12: import your customer/member list (CSV); recreate membership plans and coaching batch blocks.
- Hours 12–24: connect Razorpay, publish your branded booking page, live-test a UPI booking.
- Hours 24–48: honor existing future bookings by keying them into the new grid (Skedda exports bookings to CSV), parallel-run a day, cut over.
What collapses into one system
- The member spreadsheet → CRM profiles with membership status and history.
- The separate payment link → UPI checkout inside the booking flow, webhook-confirmed.
- The manual invoice → GST-ready receipts, automatically.
- The pro-shop notebook → POS on the same ticket as the court.
FAQ
Can I move my existing bookings from Skedda?
Yes — export bookings to CSV from Skedda and key future reservations into your Cuetronix grid during setup. Most venues have a manageable forward book and complete this in an hour or two.
How long does the switch take?
About 48 hours including setup, member import, Razorpay connection and a one-day parallel run — comfortably inside the 14-day free trial.