Operations guide · 25 September 2026
How to move coaching clients to a new platform
A migration plan for records, active programmes, payments and the client experience.
A platform switch is a client communication project as much as a data project. Clients usually care less about your software than whether their next session, remaining package, materials and messages are where they expect them to be. Design the move around those expectations.
This guide is published by Coachful, which could benefit if readers move platforms. The process is written to work in either direction. Follow the data and payment terms of both vendors and your own privacy and record-retention obligations.
The short answer
Move coaching clients in stages: inventory records and active obligations, export and protect the old data, build the new offers, pilot with one consenting client, reconcile payments and access, then give every client one clear next step. Keep the old system available until records and links have been checked.
A safe order for the move
Make a client-level inventory
For each active client, record the current programme, remaining sessions, next appointment, payment status, contract, shared files and any access that ends on a date. This becomes the reconciliation checklist.
Export and secure the history
Export contacts, notes and content in formats you can actually open. Keep a protected copy according to your retention policy. Do not assume an export includes file attachments or message history; open a sample from each category.
Rebuild one complete offer
Create the programme, booking rules, checkout, agreement and onboarding message in the new system. Buy or enrol in it with a test account to catch broken permissions before clients see it.
Pilot with one active client
Choose someone whose programme is representative and explain exactly what is moving. Verify that their next call, remaining sessions, materials and messages are visible. Collect their feedback before moving everyone else.
Move payments deliberately
Recurring subscriptions often cannot simply be copied between providers. Check whether customers must authorise a new payment method or subscription. Avoid overlapping charges and document the first renewal date in the new system.
Send one clear client instruction
Tell clients where to log in, when the change takes effect, what happens to future sessions and where to ask for help. Keep old links available during a short transition if possible, and check whether reminders still point to the old calendar.
What commonly gets lost
| Item | Check before switch-off | Client impact if missed |
|---|---|---|
| Future sessions | Calendar event and meeting link in both systems | The client arrives at the wrong link. |
| Remaining package credits | Balance reconciled against the old record | A client appears to owe money or loses a session. |
| Recurring payments | Authority, amount and next billing date confirmed | Duplicate charge or interrupted service. |
| Private notes and files | Exported, access-controlled and readable | Lost context or privacy exposure. |
| Custom domain and email | DNS, redirects and sender settings checked | Old booking links and messages stop working. |
A migration checklist should be reconciled client by client; totals alone can hide a single damaged engagement.
Worked example: a client halfway through a package
Imagine a client who bought six sessions, has attended three and has a fourth on next Tuesday’s calendar. Their old platform also holds an intake form, an agreement and two private notes. Importing only the contact record would make the new account look empty and could cause the coach to offer six sessions again or send the wrong booking link.
For this client, the migration record should show three remaining sessions, the next appointment and meeting link, the agreement status and which notes need to remain private to the coach. The coach can then invite the client to the new portal and ask them to confirm that the appointment and materials are visible. Only after that check should the old booking link be retired.
This scenario is illustrative; the exact fields and permissions depend on the two products.
Choose the migration window around the client
Avoid switching in the middle of a cohort launch or immediately before a large renewal cycle. Move new clients first if the old and new tools can run side by side. Active engagements with unusual billing or access rules should be handled individually rather than forced through a bulk import.
After the switch, inspect the first booking, first payment, first reminder and first client check-in. Ask one client to describe the experience in their own words. A dashboard reporting “import complete” only proves that a file was accepted; it does not prove the relationship survived the move.
If the reason for switching is lower cost, include the temporary double subscription and staff time in your calculation. If the reason is better client experience, check that the new login and next-action path are actually clearer. The trial checklist helps prove this before live records move.
Common questions
Can coaching subscriptions move automatically to a new platform?
Often they cannot. Payment provider and subscription terms determine what can move. Check the vendor process and obtain any customer authorisation required before creating a new recurring charge.
When should I cancel the old coaching platform?
After active clients, future sessions, access, records and billing dates have been reconciled, and after saved links or redirects have been handled. Keep an export and follow your retention policy.
The verdict
Move the work in an order clients can understand. A careful pilot, client-level reconciliation and clear communication are more valuable than a fast bulk import.