Built around the Canadian clinic day. Plan your setup

The Flor resource library

Practice management software migration checklist

A migration is a change in working process as well as a data transfer. Start with an inventory, assign owners and agree on how the practice will confirm that the move is complete.

Inventory and minimise before moving

List active records, historical records, appointments, attachments, invoices and configuration. Identify duplicates and obsolete accounts, but do not delete records without an approved retention decision. Confirm which items can be exported and how attachments are linked to their records.

Test a small, representative sample

Use an authorised, controlled migration environment and an agreed process for sensitive data. Include different record types and edge cases. Compare counts, dates, associations, permissions and readable content. A matching row count alone does not prove that information is usable.

Plan the cutover and recovery route

Set the final change window, responsibility for reconciliation and staff training. Decide how new activity during the move will be captured. Keep a rollback or continuity plan and verify who answers urgent questions. Document acceptance before retiring the old workflow.

Reconcile a representative trial import

Choose a small authorised test dataset in an agreed migration environment. Include appointments, relationships, attachments, balances and an amended record where supported. Reconcile counts and inspect the actual content, dates and links between records. Record exceptions with an owner and an acceptance decision. A trial import that merely finishes without an error is not enough to establish a usable migration.

Example acceptance worksheet
Check in the demonstrationEvidence to record
Counts and record relationships matchDescribe the observed result using fictional data.
Attachments and amendments remain readableRecord the role, exception and any manual work required.
Exceptions resolved before cutoverAgree on pass, follow-up or unavailable before rollout.

Continue with clinical notes and documentation workflows and practice billing and payment workflows to test the connected steps. The interactive Flor demo provides fictional examples for the discussion.

A therapy practice workflow: six connected steps
  1. Enquiry & intakeIdentify the service, recipient and forms that need review.
  2. Schedule the visitMatch practitioner availability, room and appointment type.
  3. Document careReview notes, care plans and the next clinical task.
  4. Invoice & reconcileCheck charges, receipts and balances in CAD.
  5. Follow upTrack the administrative conversation and assigned forms.
  6. Review the practiceUse agreed definitions to assess workload and outstanding work.

Evaluation map, not a guarantee of feature availability. Confirm your required workflow in a guided demonstration.

Questions for a Canadian clinic

Build the evaluation around your province, disciplines and funding arrangements. Ask for quotes in CAD and inspect the receipt fields your clinic requires. Where guardians or third-party recipients are involved, separate the client record, relationship and access decision. Confirm any payer connection individually.

Privacy obligations depend on the circumstances; federal and provincial rules can interact. The Office of the Privacy Commissioner of Canada explains the provincial context. Use that guidance to frame a service-specific review, without assuming that a Canadian domain establishes data residency.

A few common questions

Can I email patient data to the Flor team?

Do not send patient information through ordinary product enquiries. A migration process and appropriate controls must be agreed before any transfer.

Prepared for clinic owners in Canada. Updated . These guides support product evaluation and do not replace professional or legal advice.

Keep exploring.

A good place to begin

Bring your clinic
workflow into focus.

Tell us about your practice. We’ll help you explore whether Flor fits.

Let’s talk about your practice ↗