Migration run by the engineers who built the platform.
From Mindbody, Zen Planner, Glofox, Vagaro, MomoYoga, YOGO, Holdsport and most of the rest. Members, memberships, class history and remaining punch-card balances move across with billing dates intact. Typical timeline: one working week.
What every studio asks first
Five questions, five direct answers
Switching booking systems goes badly when the migration team is a separate vendor with no engineering depth. Here is how we avoid that.
Will I lose data?
Members, memberships, class history, attendance records, punch-card balances, gift cards, instructor records — every record imported. Anything the source system cannot export, we flag up front before you commit.
Will my members notice?
They receive one email with a new login URL. Punch cards, active memberships and class history carry across with the same balances and renewal dates.
How long does it take?
Typically 5–7 working days, depending on the source system. We commit to a date on the first call after looking at your specific export.
What does it cost?
Nothing. Migration is included on every paid plan — no separate setup fee, no professional-services bill, no per-record charge.
What if it does not work?
Cut-over only happens when both systems show the same data and you have signed off. Until that point you stay on your current system, and if migration cannot complete to your satisfaction you do not pay for the platform.
Systems we migrate from
The ones we have done most often. Yours not on the list? Most likely we can still handle it — ask.
Side-by-side comparisons: Mindbody, Zen Planner, Pike13.
The process
Five steps, about a week
- 1
Scoping call or email
A 30-minute call, or an email exchange if you prefer. We look at the exports your current system produces and confirm precisely what will and will not transfer.
- 2
Export from your current system
CSV or API export from wherever you are today. We walk you through it step by step — most studios complete it in an hour.
- 3
We import, you review
Everything loads into a test studio. You log in, click around, check that members, memberships and history look right.
- 4
Soft launch — both systems in parallel
For about a week, your old system and Class Booking run side by side. New bookings happen on Class Booking. The old system stays as a read-only backup.
- 5
Cut-over
Your members get an email with the new login URL. You cancel the old subscription. Done.
During the switch
Both systems run in parallel until cut-over
Nothing gets switched off until both systems show identical data and you have signed off. We are on the call with you while you verify it — bookings, balances, member records, payment history, the lot. Anything that looks off is fixed before the cut-over email reaches a single member.
The objective is an uneventful Monday morning.
A few practical things
Details that come up on every migration. We handle them.
Existing Stripe customer
We keep your Stripe account. No new one needed — billing history, customer records and payment methods stay where they are.
Existing custom domain
We move it without downtime. A DNS change takes about an hour to propagate, and members never see a broken page.
Email branding
We set up DKIM and SPF so emails to your members come from your own domain — not from us — before cut-over day.
No lock-in, on the way in or on the way out.
If migration cannot complete to your satisfaction, you do not pay for the platform. If you ever leave, full GDPR data export is available at any time — members, bookings, payments, settings — in JSON. That commitment applies to every customer on every plan.
Tell us your current system
A 30-minute call or an email exchange, whichever fits. We map your specific export and give you a concrete cut-over date — before you commit to anything.