The migration process
A typical migration runs about four weeks. Most of it is preparation; the actual switch is a single day.
Week 1 — Setup
Your gym is created and configured: profile, timezone, locations, staff, and Stripe connection. Nothing is live to members yet.
Week 2 — Data
Your member roster is imported, your plans are mapped, your class schedule is built, and historical waivers are brought across.
Week 3 — Payments
Payment methods are migrated. This is the step that determines whether members re-enter cards — see Move payment methods.
Week 4 — Go live
Cutover, member communication, and app rollout.
What’s protected during cutover
While a migration is running, Avex suppresses billing notifications — subscription changes, failed payments, refunds, and disputes are logged to the migration record instead of firing member-facing messages.
This prevents the classic migration disaster: rebuilding 400 subscriptions at once, your billing system interpreting it as 400 failures, and 400 members receiving dunning texts on the same afternoon.
What you keep
| Data | Comes across |
|---|---|
| Member records and contact details | Yes |
| Membership plans and pricing | Yes, via mapping |
| Payment methods | Yes, if your current processor is Stripe |
| Signed waivers | Yes, bulk imported |
| Workout history | Yes |
| Lift and PR history | Yes |
| Class schedule | Rebuilt |