The part coaches worry about when they change platforms is the data — the programs, the templates, the two years of check-in history. That part is tedious and it is solvable. The part that actually costs money is the clients. Every one of them has to find a new app, make a new login, work out where the check-in form went, and re-enter a card. Each of those steps is a place where somebody puts their phone down and does not pick it back up, and the client who quietly stops logging in week one is usually gone by week six.
So this is not a data-migration guide. It is about protecting the roster through a change that, from the client's side, is extra work you have asked them to do for reasons that are yours.
First, decide whether to switch at all
Most switching advice assumes you have already decided. Worth checking, because a migration costs ten to thirty hours of rebuilding, a month of double subscription, and a slice of your roster.
- The platform is missing something you sell every day — nutrition, payments, forms — and you are paying for it elsewhere or doing it by hand.
- The bill has grown past what the tool does for you, usually through add-ons stacked on a tier that looked cheap.
- Something is broken for your clients specifically: the app, the notifications, the logging.
- You are about to grow into a tier that changes the economics.
- You have not learnt the platform you are on. Two weeks with the help docs is cheaper than a migration and often ends it.
- A competitor's marketing page looks better than the tool you use every day.
- One feature you would use monthly. Work out what that feature is worth per month before you trade a whole roster for it.
The sunk-cost trap runs both ways. The obvious version is staying because of the year you spent building templates; those hours are gone either way, and the only question is the next twelve months. The version nobody warns you about is pushing the move through in a bad month because you have already decided to leave, and that cost is paid in clients.
Count the real cost before you commit
Do it as a number, not a feeling.
| Cost | Typical | How to check yours |
|---|---|---|
| Rebuilding programs and templates | 10-30 hours | Time yourself rebuilding one block, multiply |
| Rebuilding check-in forms and packages | 2-4 hours | Count the forms you actually use |
| Overlap month on both platforms | One extra subscription | Both plan prices, added |
| Clients lost to the change | 2-10% of the roster | Your monthly revenue per client, times that |
| Your own re-learning | A slower fortnight | Assume every task takes twice as long |
At 30 clients on $250 a month, losing 5% costs $375 a month, permanently — usually a bigger number than the software saving that started the conversation. That is not an argument against switching. It means the saving has to beat a year of that, and it means timing, notice and waves are where the money is, not the export.
Timing matters here too. If you are mid-way through an annual subscription, you have already paid for the rest of the term. Annual billing is normal in this category — Trainerize's annual saves 10%, Everfit's 16% and Kahunas' 25%, as of September 2026 — so a switch in month three of an annual plan means paying twice for nine months. Waiting until renewal is often the whole plan.
Time it between program blocks, not mid-block
The single biggest lever, and it costs nothing.
A client in week four of an eight-week block has a workout on Thursday they expect to find where they found Tuesday's, and moving them interrupts something that was working. A client who finished a block on Sunday is already expecting change, so a new app arrives as part of a fresh start.
Line the switch up with a natural boundary:
- The end of a program block, ideally for most of the roster at once.
- The start of a month, so billing periods do not get split awkwardly.
- Not December, not the first fortnight of January, and not the week you are on holiday.
If your clients are all on different block schedules, move each person at their own boundary rather than forcing everyone through yours.
Rebuild before you invite a single client
They log in on day one, find nothing, and decide the new thing is worse than the old thing. That impression is hard to reverse.
Before anyone gets an invite, have the following built and tested on the new platform:
- Your three most-used program templates. Not all forty. Three, rebuilt properly.
- The check-in form you send every week, with the same questions in the same order so clients are not re-learning the form and the app at once.
- Your packages and prices, set up but not yet live.
- One test client — a friend, a family member, or a second account of your own — taken through the entire flow: invite, signup, first workout, first check-in, first payment.
The test account is the step most coaches skip and the one that catches everything — the invite landing in spam, a permission prompt nobody was warned about, a form that looks fine on your laptop and truncated on a phone. Find those with one account, not with 30 clients.
Rebuild the rest of the library later, once people are actually on the platform. Waiting for perfect parity is why migrations stall for six months. Where you rebuild matters too: coaches who have moved to Fitsly tell us most of week one got done from the coach app on the phone, between sessions.
Export what you can and accept what you cannot
Some of your history will move and some will not, and knowing which stops you promising clients something you cannot deliver. Check what your current platform's export actually produces before you plan around it — it varies by platform and by plan — then sort your data into three piles:
Worth moving. Client contact details, current programs, your templates and exercise library, active packages and prices. This is the working set. Most of it you will rebuild rather than import, because the file formats rarely line up.
Worth archiving. Historical check-ins, old progress photos, past measurements, message history. Export it into a dated folder in cloud storage. You need it far less often than you expect, and when a client asks what they lifted last winter, a folder answers that fine.
Let it go. Chat threads, streaks, logged workouts from two years ago, in-app activity history. These almost never survive a platform change, and rebuilding them by hand is not a good use of the hours you have.
Tell clients this before they find out themselves. "Your history from the old app won't come across, so screenshot anything you want to keep" prevents a bad conversation in week two. Ask them to save their own before-photos, which are the ones people are attached to.
Tell clients what is happening, and when
A week of notice is the minimum. Two is better. Anything less and the first your client hears of it is an invite email from a company they have never heard of, which looks exactly like a phishing attempt and gets deleted.
Say four things: what is changing, when, what they have to do, and why it is better for them — not better for you, since nobody is switching apps to help your admin. A week out:
Hi Sam — a heads-up that I'm moving my coaching over to a new app from Monday the 6th. You'll get an invite email from me that day with a link to set up your login. It takes about five minutes, and your program for the next block will be waiting in there.
Why: your check-ins, program and food logging will all be in one place instead of three, and messaging me won't mean a separate app.
Your training history in the old app won't come across, so if there's anything you want to keep, screenshot it this week. Nothing changes about your payments right now — I'll let you know separately before that moves.
Any trouble getting in, message me and I'll walk you through it.
Send a short second message on the day, with the link. Then a third to anyone who has not logged in by day three — that is the one that saves clients, because non-response is not refusal, it is usually an unread email.
Give them a deadline that is real but not aggressive. "Everyone across by the 20th" works. "Do it today" does not, and open-ended does not either.
Move in waves, not all at once
Inviting 40 people on the same morning means 40 people hitting the same problem at once, and you answering the same question 40 times while working out whether it is you or the app.
Waves of five to ten, two or three days apart:
The first group always surfaces something you could not have predicted, and finding it with five people rather than forty is the whole reason to stage it.
Keep a simple list — name, invited, logged in, first workout done, first check-in submitted, payment moved — and work it every day. The people who stall do not tell you they have stalled.
What a six-week migration looks like
Week by week, for a roster of about thirty. Compress it if you have ten clients; do not compress it if you have eighty.
| Week | What you do | What the client sees |
|---|---|---|
| 1 | Rebuild three program templates, the weekly check-in form and your packages. Run a test account end to end. | Nothing. Normal coaching on the old platform. |
| 2 | Set the date. Send the notice message. Prepare the invite and the two follow-ups. | A message: what's changing, when, what they'll need to do. |
| 3 | Invite wave 1 — five reliable clients. Fix whatever they trip over. | An invite, a signup, their next block already loaded. |
| 4 | Invite wave 2, the bulk of the roster. Chase anyone not logged in by day three. | An invite and one personal nudge if they stall. |
| 5 | Invite wave 3 by phone. Everyone's first check-in runs on the new platform. | A check-in that works, in the new app. |
| 6 | Move payments on each client's renewal date. Cancel the old subscription. | One message about billing, then a normal charge. |
The two weeks people cut are 1 and 2, and they are the two that decide how the other four go.
Run both platforms briefly, and put an end date on it
For a few weeks you will have clients on both, which is the safe way to do it. What is not safe is letting it drift: two live platforms means two places to check and two places to answer messages, and the clients still on the old one get the worse half of your attention.
Set the end date before you start, tell clients what it is, and hold it. Three to four weeks is enough for a roster of thirty. Downgrade or cancel the old plan the week after that — put a reminder in your calendar, because an unused subscription can run for months before you notice.
Check the new platform's trial length before you plan the overlap. As of September 2026, Fitsly and TrueCoach run 14-day trials, Hevy Coach 30 days, PT Distinction a month, and Everfit and Trainerize both have free tiers you can sit on while you rebuild. Two weeks covers rebuilding templates and one check-in cycle, not a whole roster, so expect to pay for at least one real month on both. On Fitsly every feature is open for the 14 days, so the test account runs the real flow.
During the overlap, be strict about one thing: new work only happens on the new platform. The moment you write a program on the old one because it is faster, the migration has stopped.
The payment cutover is where it actually goes wrong
A failed cutover either charges a client twice or stops charging them at all, and only one of those shows up on your dashboard.
The order matters:
- Cancel nothing until the new subscription exists. Set the new one up first, confirmed and dated, then cancel the old.
- Move people on their renewal date, not in the middle of a paid period. It avoids pro-rata maths and awkward part-refunds.
- Tell them separately from the app move. A single message that says "new app and re-enter your card" gets read as a scam. Move the app first, payments a fortnight later, once they are comfortable that the new thing is real.
- Watch the first billing cycle client by client. This is the one week where you check every payment against your list rather than trusting a total.
- Have the failed-payment message ready before you need it, because you will need it two or three times.
Card details do not transfer between platforms — clients re-enter them, and that is your highest drop-off moment in the entire migration. Some of it you can remove: if the new platform sells packages through a public checkout link, you send a link and they buy, rather than asking them to find a billing screen inside a new app. That is what packages and payments are for on Fitsly — recurring billing, minimum commitments and failed-payment retries handled by the platform rather than by you chasing texts.
Watch for anyone on an old grandfathered price. Rebuild that price deliberately, or you will raise it by accident.
After the move, watch the quiet ones
Two weeks after the last wave, run the list again and find anyone who has not logged a workout, not submitted a check-in, or not opened the app. Message them personally, and ask about training rather than about software:
Haven't seen anything logged this week — how's the block going? Also, did the new app set up alright for you? Happy to jump on a call for five minutes if it didn't.
Most of the answers will be "I got stuck at the login and forgot". That is a five-minute fix and a saved client, and it is only fixable if you look. Post-migration attrition shows up in the numbers about six weeks later, which is far too late to do anything about it — the same lag that makes client churn hard to read at any other time.
Use the first check-in cycle on the new platform to show the client what they got out of the change. If the form is faster to fill in, say so; if your reply is better because the data is in one place, make the reply show it — the wording that gets responses is in how to write check-in messages clients reply to.
Update the front of your business too. Your signup links, sales page, welcome email and onboarding sequence all still point at the old platform, and a new client landing there three months after you left is a bad first day.
