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.

By Tregovia Editorial · How we verify what we publishPublished 6 min read
Move from Cliniko to CRM Checklist
Summary

Migration checklist for allied health clinics moving from Cliniko to a CRM: patients, appointments, invoices, treatment notes, exports, forms, SMS. It covers split the export, why allied health migrations carry higher stakes than most CRM switches, sample records to test, and multi-practitioner clinics face their own complexity.

Moving from Cliniko to a CRM: Migration Checklist for Allied Health Clinics

Moving from Cliniko to a CRM is not a normal contact import. Allied health clinics hold patient records, clinical notes, practitioner schedules, invoices, forms, reminders, and sometimes integrations that support care delivery. A CRM may help with operations, but it should not be treated as a drop-in clinical system.

The first migration decision is whether the clinic is replacing Cliniko entirely or moving only the admin layer: booking, billing, reminders, intake, and follow-up.

For cost modelling before migration, read Cliniko total cost for allied health clinics. The cost comparison should not happen before clinical-record ownership is clear.

Split The Export

Use three buckets:

BucketExamplesMigration decision
CRM operationscontact details, appointments, invoices, balances, remindersUsually CRM candidate
Clinical recordstreatment notes, patient files, health detailsDo not move by default
Retention/archiverecords that must stay accessibleKeep under documented policy

This split prevents clinical records from being copied into a general CRM note field simply because the export format makes it possible.

Why Allied Health Migrations Carry Higher Stakes Than Most CRM Switches

Most CRM migrations risk operational disruption, missed appointments, confused billing, but an allied health clinic migrating away from a clinical practice-management system risks something categorically more serious: mishandling patient health information that carries legal retention obligations and professional confidentiality duties independent of any general data-protection framework. A physiotherapy clinic's treatment notes, or a psychology practice's session records, aren't just sensitive data in the abstract, they're often subject to specific statutory retention periods and access rules that a general CRM was never built to enforce.

This is why the three-bucket split (CRM operations, clinical records, retention/archive) matters more here than the equivalent categorization exercise in a typical service-business migration. Getting it wrong by casually importing clinical notes into a general CRM's free-text field doesn't just create a data-quality problem, it can create a genuine compliance gap if that system lacks the access controls, audit trails, or retention enforcement that clinical records are specifically required to have.

Sample Records To Test

Do not test with perfect data. Use:

  • Active patient with future appointment
  • Former patient with records that must be retained
  • Patient with unpaid invoice
  • Patient with multiple practitioners
  • Duplicate contact details
  • Appointment with cancellation/no-show status
  • Patient with clinical records that should not move
  • Patient with missing phone or email

The import should show what fails, what needs cleanup, and which fields should stay out.

Multi-Practitioner Clinics Face Their Own Complexity

A clinic with several practitioners sharing a patient base introduces a migration wrinkle that a single-practitioner practice doesn't face: patients frequently see more than one practitioner, either concurrently for different needs or sequentially as they transition care, which means the receiving system needs to represent multi-practitioner history accurately rather than assuming each patient belongs to exactly one provider.

A migration that flattens this into a single "assigned practitioner" field per patient loses real operational context: a practitioner picking up a patient who's also seeing a colleague needs to know that, both for continuity of care and to avoid duplicating assessments the other practitioner already completed. Testing at least one multi-practitioner patient record specifically, rather than assuming the general patient migration path handles this correctly by default, is a more realistic acceptance test than testing only single-practitioner cases.

Cutover Checklist

  1. Freeze non-essential template and workflow changes.
  2. Export a small sample.
  3. Map fields into the receiving CRM.
  4. Import sample records.
  5. Check appointment times, statuses, and practitioner context.
  6. Check invoice totals and balances.
  7. Rebuild only the forms needed for future admin work.
  8. Preserve clinical-record access separately.
  9. Tell staff exactly which system owns which workflow.
  10. Monitor the first week daily.

Do not switch on a Friday or before a fully booked week. Migration errors are easier to correct when the clinic has operational breathing room.

Receiving CRM Fit

The receiving CRM should pass the admin-workflow test:

  • Contact records import without clinical notes.
  • Future appointments and practitioner context are correct.
  • Invoices, balances, refunds, and reports reconcile.
  • SMS reminders are tested before they send.
  • Future operational forms are recreated only where needed.
  • Retained clinical records remain accessible under policy.
  • Staff know which system owns each workflow.

Tregovia can be evaluated for CRM operations around clients, appointments, billing, SMS, online booking, reports, data import, forms, and follow-up. It should not be described as replacing Cliniko's clinical notes, treatment records, patient privacy workflow, or allied-health practice-management depth unless those workflows are verified directly.

Use Tregovia pricing to model the receiving CRM and CRM alternatives if the clinic is comparing broader systems rather than clinical practice-management tools.

Referral Sources Deserve Their Own Tracking

Allied health clinics commonly receive patients through GP referrals, insurance panels, or specialist recommendations, and losing track of referral source during a migration has consequences beyond marketing attribution. Clinics often need to report referral relationships back to referring providers or maintain records for insurance and billing purposes, which makes referral source a genuinely operational field, not just a nice-to-have for understanding where new patients come from.

Confirming that referral source data transfers correctly, and that it's structured well enough to actually query later, is worth its own explicit check during migration testing rather than assuming it will simply follow along with the rest of the patient record.

Migration Mistakes

Common failures:

  • Importing treatment notes into general notes
  • Losing practitioner context on appointments
  • Recreating invoices without balance status
  • Forgetting recurring reminders
  • Letting both systems send SMS
  • Closing Cliniko access before retained records are safely handled
  • Failing to tell patients where booking or payment links changed

The staff handoff should be short: book here, invoice here, find retained clinical records there, and do not enter clinical notes into the CRM unless approved.

Cliniko Migration Questions

What should clinics export before leaving Cliniko?

Export or document patient lists, contact details, appointments, invoices, payment status, reminders, forms, files, and clinical records where current Cliniko tools and clinic obligations allow.

Can a CRM replace Cliniko?

Only for CRM-style operations such as clients, appointments, billing, reminders, intake, and follow-up. It should not be assumed to replace clinical notes, treatment records, patient privacy workflows, or allied-health practice-management depth.

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, separate clinical records from CRM data, export a sample, map fields, test imports, validate appointments and invoices, preserve retention obligations, and run a monitored cutover.

What should not move into a CRM by default?

Treatment notes, clinical files, sensitive patient history, health-specific forms, and clinical communication should not move unless the receiving system is verified for that use.

Migration Rule

The migration is ready only when the clinic can explain what moves, what stays clinical, who can access retained records, and how the first week will be checked. Without that separation, switching from Cliniko to a CRM creates more risk than savings.

FAQ

What should clinics export before leaving Cliniko?

Export or document patient lists, contact details, appointments, invoices, payment status, reminders, forms, files, and clinical records where current Cliniko tools and clinic obligations allow.

Can a CRM replace Cliniko?

Only for CRM-style operations such as clients, appointments, billing, reminders, intake, and follow-up. It should not be assumed to replace clinical notes, treatment records, patient privacy workflows, or allied-health practice-management depth.

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, separate clinical records from CRM data, export a sample, map fields, test imports, validate appointments and invoices, preserve retention obligations, and run a monitored cutover.

What should not move into a CRM by default?

Treatment notes, clinical files, sensitive patient history, health-specific forms, and clinical communication should not move unless the receiving system is verified for that use.

Export or document patient lists, contact details, appointments, invoices, payment status, reminders, forms, files, and clinical records where current Cliniko tools and clinic obligations allow.

14-day free trial

Separate clinical records from CRM operations

Map patients, appointments, billing, reminders, forms, treatment records, exports, and retention before importing clinic data.