How to move your coaching clients to new software without losing history

Most coaches who are unhappy with their software stay on it anyway. The reason is rarely the subscription. It is the fear of a messy move: lost history, confused athletes, a month of double work, and a few clients who use the disruption as a reason to leave.

Those risks are real, and they are manageable. This guide sets out a move that takes one training block, keeps the history you will actually use, and gives every athlete a clean start date.

First, decide what "history" you need

Coaches tend to treat all past data as equally precious. It is not. Sort it into three piles before you touch anything.

History you will use every week

• Current working loads for the main lifts or key sessions per athlete.
• Recent test results and the dates they were taken.
• Injuries, restrictions and anything a physio has said.
• The current block: what week each athlete is in and what comes next.

This is the pile that has to arrive on day one. It is usually small: a page per athlete.

History you will refer to occasionally

• Personal records and when they were set.
• Previous blocks you might reuse as templates.
• Long-term notes on how each athlete responds to volume and intensity.

This can travel later, or live in an archive you can search.

History you will never open again

Old message threads, logs from three years ago, sessions an athlete skipped in 2023. Keep a copy if you can, for your own records, then let it go. Moving it is effort that buys nothing.

Step 1: export and archive before you announce anything

Before you tell a single athlete, take a copy of everything your current platform lets you take, and save the pages you need by hand where it does not. Do this while your account is active and nothing is in flux. Store it somewhere you control, organised by athlete.

Then write the "every week" pile for each athlete into a short summary: current loads, last test, restrictions, where they are in the block. This summary is what you will work from on the new platform.

Step 2: run one block in parallel with two athletes

Pick two athletes who are reliable loggers and who will tell you plainly what they think. Move them first, for one full block, while everyone else stays where they are.

This does three things. You learn the new tool on real programming rather than a demo. You find the workflow problems (how you write a session, how you set up templates) while the stakes are low. And you get two athletes who can tell the rest of the roster what the new app is like.

Most coaching software has a free tier or a trial that covers two athletes. Use it for this.

Step 3: rebuild your templates, not your archive

The temptation is to recreate every past programme in the new tool. Resist it. Instead, rebuild the handful of templates you actually reuse: your standard sessions, your typical first block for a new athlete, your deload week.

If the new tool reads shorthand, this is mostly pasting. Write each exercise on its own line with the numbers first, and check the structure it reads back. If it reads it wrong, fix the field once and save the template. The structured prescriptions page shows how that works on Loadout.

Step 4: bring the rest of the roster over at a block boundary

Move each athlete at the start of a new block, never in the middle of one. A block boundary is a natural reset: new numbers, new structure, a reason to look at the plan with fresh eyes. Moving mid-block means two half-blocks in two places, and nobody can see the whole picture.

For each athlete:

1. Send the invite with a short note: why you are moving, the date the new block starts, and what they need to do (install the app, accept the invite, connect their watch if they have one).
2. Programme their new block in the new tool, starting from the summary you wrote in step 1.
3. Keep the old platform readable, not active. Do not post new sessions there after the switch date.

Stagger the moves over two or three weeks if your athletes' blocks end at different times. That spreads the setup work and means you are never onboarding the whole roster on one evening.

Step 5: let the watch bring the training history with it

For athletes who train with a watch, the most valuable history is often not in your coaching platform at all. It is in their watch account or their training platform: every run, ride and session they recorded, with pace and heart rate.

If your new software can connect to those accounts and import past activities, that history arrives with the athlete rather than with you. On Loadout, an athlete who connects intervals.icu, Strava or Garmin can import their past activities, a year by default, and new activities keep flowing in and completing prescribed sessions. See sessions on the watch for what that looks like.

How to tell athletes without losing any

The move itself rarely loses clients. The announcement can. A few rules:

• Lead with what changes for them. "Your runs will be on your watch and log themselves" lands better than "we are moving to a new platform".
• Give a date, not a vague "soon". Athletes plan around certainty.
• Keep it one step. One link to accept, one app to install. Anything beyond that, do for them.
• Do not change price and platform at once. If you plan to adjust prices, do it a block later, so the two do not get tangled together.
• Check in after the first week. A two-line message asking how the first sessions went catches problems before they become complaints.

What to check before you commit

Before you move anyone beyond your two pilot athletes, confirm:

• You can write a typical week as fast as you could before, or faster.
• Your athletes can log a normal session without asking you how.
• Cardio sessions reach the watch for athletes who have one.
• You can see at a glance who has and has not trained this week.
• Athletes can export their own data if they ever leave. A platform that makes leaving hard will make it hard for you too, one day.

If any of these fail, extend the pilot rather than pushing on.

FAQ

How long does it take to move a roster of 20 athletes?

Plan on one training block for the pilot and two to three weeks for everyone else, moving each athlete at their next block boundary. The setup per athlete is mostly writing their first block.

Should I import every old session into the new platform?

Usually not. Keep an archive of the old data, carry over current loads, tests and restrictions, and let watch-connected history come across through the athlete's own accounts.

What if an athlete refuses to move?

Give them a date after which you will programme only in the new tool, and offer to set it up with them. Most resistance is about effort, and removing the effort usually removes the resistance.

Run your pilot block

Loadout is free for up to two active clients with no time limit, which covers the pilot in step 2. Invite your two athletes and programme their next block: start free.