Move from SimplePractice to CRM Checklist
Migration checklist for EU therapists moving from SimplePractice to a CRM: client records, appointments, billing, forms, clinical notes, exports.

Migration checklist for EU therapists moving from SimplePractice to a CRM: client records, appointments, billing, forms, clinical notes, exports. It covers split the data before export, export inventory, why this migration is riskier than a typical CRM switch, and test import sample.
Moving from SimplePractice to a CRM: Migration Checklist for EU Therapists
Moving from SimplePractice to a CRM is a high-risk migration if the practice treats every record as ordinary admin data. Therapy businesses hold clinical and operational information together: client identity, appointments, invoices, forms, notes, portal records, payment history, and sometimes telehealth or insurance-related context.
A CRM may be useful for client operations, but it is not automatically a therapy platform. The first migration decision is what should move, what should stay archived, and what must remain in a clinical system.
For cost modelling before this step, read SimplePractice total cost for EU therapists. Cost only matters after the receiving workflow is safe and realistic.
Split The Data Before Export
Create three buckets:
| Bucket | Examples | Migration decision |
|---|---|---|
| Operational data | name, email, phone, appointment, invoice, payment status | Usually CRM candidate |
| Clinical data | notes, treatment details, diagnosis context, therapy forms | Do not move by default |
| Legal/retention data | records that must be preserved | Archive or keep accessible under policy |
This split should happen before import mapping. If the practice exports everything first and sorts it later, sensitive records can spread into folders, spreadsheets, and test systems.
Export Inventory
List every source:
- Client profiles
- Contact details
- Active and inactive client status
- Future appointments
- Recurring appointments
- Cancelled or no-show appointments
- Invoices and balances
- Payment references
- Intake forms
- Consent forms
- Reminder templates
- Client portal instructions
- Clinical records and notes
- Telehealth-related records where relevant
- Insurance or claim-related records where relevant
Beside each source, add one decision: import, recreate, archive, keep in SimplePractice, or exclude.
Why This Migration Is Riskier Than A Typical CRM Switch
Most CRM migrations covered in comparable guides for other business types are primarily about not losing bookings, invoices, and reminder history. A therapy practice migration carries an additional dimension those guides do not: many EU jurisdictions impose specific statutory retention periods on clinical and therapeutic records, meaning the practice cannot simply decide, as a matter of convenience, what to keep or discard. A record that looks like ordinary case-note clutter to someone doing a quick data cleanup may actually be legally required to remain accessible for years after the client's last session.
This is the core reason the operational/clinical/legal-retention split described above needs to happen before any export, not as a cleanup step afterward. Once records are exported into a generic spreadsheet or dumped into a new CRM's freeform notes field, the clean separation between what has retention obligations and what does not becomes much harder to reconstruct, and the practice risks either losing access to something it was legally required to keep or importing sensitive clinical detail into a system never intended to hold it securely.
Test Import Sample
Use a sample that includes messy records:
- Active client with future appointment
- Former client with records that must be retained
- Client with unpaid invoice
- Duplicate contact details
- Client with missing phone number
- Client with forms but no upcoming appointment
- Client whose clinical records should not move
If the CRM import only works for clean records, the migration is not ready.
Receiving CRM Fit
The receiving CRM should pass the admin-workflow test:
- Client contact records import without clinical notes.
- Future appointments and recurring appointments are correct.
- Invoices, balances, refunds, and payment status are reconciled.
- Reminder timing is tested before messages send.
- Only future operational forms are recreated.
- Staff know where retained clinical records remain.
- Sensitive therapy records are excluded unless the receiving system is verified for that use.
Tregovia can be evaluated as the receiving system for CRM operations such as client records, scheduling, billing, reminders, intake, and follow-up. It should not be described as replacing SimplePractice clinical documentation, telehealth, prescribing, insurance, or therapy-specific workflows unless those claims are verified.
Use Tregovia pricing to model the receiving system and CRM alternatives if the practice is comparing several non-therapy CRM options.
Clients With No Future Appointment Still Need A Decision
A migration checklist naturally focuses on active clients with upcoming sessions, since they're the most visible and the most likely to notice a problem immediately. Former clients with no future appointment but an outstanding balance, or with retained records still inside a legal retention window, are easy to overlook precisely because nothing about their record demands attention on a normal day. That does not make them safe to ignore during a migration.
A practical fix is a specific pre-migration query, not "all clients," but explicitly "clients with no future appointment and an unresolved balance or an active retention obligation." This group needs its own line item in the migration plan, since it will not surface naturally in the normal test-sample walkthrough of upcoming appointments and will otherwise only be discovered later, when a former client requests their records or an unpaid balance goes unexplained.
Cutover Plan
Do not switch during a full clinical week. Use a controlled sequence:
- Freeze new template changes in the old system.
- Export the test sample.
- Import and review sample records.
- Confirm appointment time zones and statuses.
- Confirm invoice totals and unpaid balances.
- Rebuild only the forms needed for future operations.
- Preserve clinical-record access under the practice's retention policy.
- Notify staff which system owns each workflow.
- Run the final export.
- Monitor the first week daily.
The handoff note for staff should be blunt: where to book, where to invoice, where to find retained clinical records, and what not to enter into the CRM.
Migration Risks
Watch for:
- Importing clinical notes into general CRM notes
- Losing future appointments during export
- Recreating invoices without payment status
- Sending reminders from both systems
- Forgetting clients with no future appointment but active balances
- Removing access to retained records too early
- Failing to tell clients where portal or payment links changed
These are workflow risks, not just technical risks.
Therapist Migration Questions
What should therapists export before leaving SimplePractice?
Export or document client lists, contact details, appointments, invoices, payment status, forms, reminders, portal needs, and clinical records where current SimplePractice tools and legal obligations allow.
Can a CRM replace SimplePractice for therapists?
Only for CRM-style operations such as clients, appointments, billing, reminders, intake, and follow-up. It should not be assumed to replace clinical notes, telehealth, insurance, prescribing, or therapy-specific records.
Where does Tregovia fit?
Tregovia can be evaluated for clients, appointments, billing, SMS, online booking, reports, data import, refunds, optional client forms, and optional follow-up sequences.
What is the safest migration order?
Audit workflows, decide what stays clinical, export a sample, map fields, test imports, validate appointments and invoices, preserve retention obligations, then run a monitored cutover.
What should not be imported into a CRM by default?
Clinical notes, therapy documentation, diagnosis details, telehealth records, insurance records, and sensitive messages should not be imported unless the receiving system is verified for that use.
Migration Rule
The migration is ready only when the practice can explain which system owns clinical records, which system owns admin operations, and how retained records remain accessible. Without that split, moving from SimplePractice to a CRM is not a cost-saving project; it is a records-risk project.
Related articles
Commercial
Move from Cliniko to CRM Checklist
Migration checklist for allied health clinics moving from Cliniko to a CRM: patients, appointments, invoices, treatment notes, exports, forms, SMS.
Commercial
Move from Trainerize to CRM: Trainer Checklist
Migration checklist for personal trainers moving from Trainerize to a CRM: clients, programs, bookings, payments, messages, nutrition data, exports.
Commercial
Move from Glofox to CRM: Gym Checklist
Migration checklist for gyms moving from Glofox to a CRM: member exports, memberships, bookings, payments, apps, waivers, reminders, data terms.
Separate clinical records from CRM operations
Map clinical documentation, client records, appointments, billing, forms, reminders, exports, and retention before importing anything.