Members and MembershipsLive
Importing From Your Current System
Moving from ARBOX or another system. You export nothing, and you retype nothing.

ARBOXA copy, taken for you
Members
Memberships and plans
Class packs and balances
Attendance history
Payment history
You export nothing and you stop nothing. The old system keeps running.
Read This Before Anything Is WrittenNothing has been touched yet. This is a plan, run against a copy.
Plan| What | Comes across | Note |
|---|---|---|
| Members | 186 | With phone and email |
| Memberships | 142 | Same renewal dates |
| Class packs | 38 | Entries left and expiry, exactly |
| Attendance and payments | All | Nobody's tenure resets |
| Needs a decision | 3 | Two people share one phone number |
Approve and WriteRun both for a month, then switch on a day you pick. Running it twice makes no duplicates.
Product picture: what comes across from ARBOX, as a plan you read before anything is written. Figures are a sample.
What You Get
A Plan First, Writing Second
- 01
A Plan First
See exactly what will come across and what will not, before anything happens.
- 02
Balances Come Across Exactly
Entries left on a pack and its expiry date arrive as they are.
- 03
History, Not Only Now
Attendance and payments come across, so a member's tenure does not reset.
- 04
Run Both in Parallel
A month where both systems work, with no month of billing at risk.
- 05
You Pick the Day
Not us, and not a renewal date.

How It Works for Your Members
See it as a memberMembers Barely Notice
Their membership, their pack and what is left on it are waiting in your new app on the day you switch.
Tell Us How Your Studio Runs Today.
The first conversation is questions, not a deck.