GymDesk
Priority mapperMembers, families, ranks, classes, billing plans, payments, waivers, and attendance history.
Migration
Switch without breaking the gym.
Move from GymDesk, Zen Planner, Mindbody, Wodify, ClubReady, spreadsheets, or a messy mix of tools into one verified operating system.
Live import
Cutover board
Families matched
Billing checked
AI ready
Not just GymDesk
Built for messy real-world migrations.
Most gyms are not moving from a perfect database. They are moving from old platforms, patched spreadsheets, payment exports, staff notes, and owner memory.
Zen Planner
Guided importContacts, programs, memberships, family links, class schedules, notes, billing state, and lead exports.
Mindbody
Data workbookClient profiles, bookings, visit history, passes, packages, stored notes, and revenue reports.
Wodify
Fitness mapperAthlete records, programs, attendance, waivers, billing exports, and coach-facing class data.
ClubReady
Ops reviewMembers, agreements, billing status, prospects, schedules, tasks, and payment exceptions.
Spreadsheets
Manual cleanseCSV member lists, rank sheets, attendance logs, direct-debit files, notes, and custom fields.
14-day path
Migration should feel controlled, not heroic.
The goal is not to dump a CSV and hope. TatamiOS gives the owner visible checkpoints before money, class operations, and family access move over.
01
Extract
Exports, reports, CSVs, API data, and owner knowledge are pulled into a migration workbook.
02
Map
Families, payers, plans, ranks, classes, trials, waivers, and payment states are matched to TatamiOS.
03
Clean
Duplicates, orphan children, expired plans, stale notes, and broken billing records are surfaced.
04
Rehearse
A test import runs before launch so owners can verify the gym makes sense inside TatamiOS.
05
Cut over
Classes, billing, staff workflows, AI reception, and owner dashboards move over with a rollback-aware plan.
Data coverage
The data that matters comes with you.
The promise is not “we imported a CSV.” The promise is that the gym opens the next day with members, families, schedules, billing, and staff workflows still making sense.
Members
Profiles, contact preferences, medical notes, emergency details, and member status.
Families
Guardians, siblings, payers, pickup permissions, household discounts, and parent logins.
Programs
Classes, schedules, waitlists, ranks, belts, trials, and capacity rules.
Billing
Plans, invoices, failed payments, discounts, GST, payer relationships, and recovery queues.
History
Attendance, notes, lead source, booking timelines, rank changes, and payment events.
Staff flow
Coach notes, reception tasks, escalation rules, owner preferences, and AI permissions.
Verification
We find the problems before launch day does.
Migration is also an audit. Broken households, stale billing, bad rank data, duplicate leads, and vague AI permissions become visible before the switch.
Family graph
Every child has the right guardian, payer, discount, and communication path.
Money
Active plans, failed cards, invoices, tax treatment, and migration balances are checked.
Classes
Programs, session times, capacity, waitlists, ranks, and coaches line up before launch.
AI readiness
The AI layer only acts on verified prices, schedules, policies, offers, and escalation rules.
Parallel run
Run a test import, compare rosters and billing, then let staff rehearse the workflows before the old system is retired.
Dry run
Owner sign-off
Staff rehearsal
Family cleanup
Make parent accounts, sibling groups, pickup permissions, and payer relationships cleaner than they were in the old platform.
Duplicates
Guardians
Discounts
AI handover
The AI layer starts with verified schedules, prices, rules, escalation paths, intro offers, and the owner’s tone.
Policies
Offers
Escalations
A better platform should make switching feel possible.
Bring the messy platform, the spreadsheet, the billing export, and the owner context. TatamiOS turns it into a launch plan.