Reversible migration plan
Client coaching software migration checklist
Move in controlled stages, retain a rollback point, and verify records and access before retiring the previous workflow.
1. Inventory and export
- List the records, programmes, files, messages, and account settings in scope.
- Create a dated export from the current platform and confirm that it opens.
- Record what cannot be exported and decide whether it is necessary to move.
2. Consent and data minimisation
- Confirm the lawful basis, client notices, and any consent needed for the move.
- Apply data minimisation: migrate only information needed in the new workflow.
- Remove duplicate, expired, test, and unsupported sensitive records.
3. Mapping and programme QA
- Map names, identifiers, units, dates, exercise fields, and staff roles.
- Run programme QA on representative plans, progressions, and client views.
- Check permissions with owner, coach, and least-privileged test accounts.
4. Staged invitation
- Start with staff and a small pilot group before inviting the full roster.
- Use synthetic or expressly approved test data for the first rehearsal.
- Send a staged invitation with a clear support and cutover contact.
5. Cutover and rollback
- Keep the source export and a documented rollback point until checks pass.
- Define who can stop the cutover and how clients return to the prior workflow.
- Avoid deleting the source system during the verification window.
6. Post-migration verification
- Complete post-migration verification for record counts, programmes, units, and access.
- Ask pilot users to check their own view and report discrepancies.
- Document exceptions, owners, due dates, and the final retention or deletion decision.
Trial the destination before the cutover
Use the coaching software scorecard to record the evidence behind your shortlist. If Repit remains on it, create a coach account for a staged test.
Create a coach account