Switching softwarePractice ops

How to switch practice management software without losing a week

A dated cutover plan for switching practice management software: what to check in the export, when to freeze, the parallel week and the first invoice run.

If you have put off switching software, it is probably not because you are attached to the system you have. It is the stories: a Monday where nobody can find the 9am patient, reminders going out twice, a month of invoices that will not reconcile, and a front desk that quietly keeps a paper diary just in case. The move itself is rarely the hard part. The hard part is doing it while you keep seeing patients, without a gap where neither system is quite the truth.

The fix is not a better vendor promise. It is a plan with dates on it. What follows is the cutover plan we would use ourselves: five stages, each with a clear finish line, so the switch costs you a few evenings rather than a lost week.

Stage 1: get the export, and read it before you trust it

Everything starts with what your current system will give you. Ask your current vendor, in writing, what their export includes and in what format, and do it before you sign anything new. Then run a full export early, weeks before go-live rather than the night before, and open it.

Check these five things, in this order:

  1. Patients. Count the rows and compare with the count your current system shows. Spot-check names, dates of birth, phone numbers, addresses and funding details on patients you know well. Archived or discharged patients are often left out unless you ask for them, so look for an option to include them.
  2. Appointments. Check the count and the date range, then open a day you remember and confirm the 11am visit is at 11am. Time zones are the one thing that can be wrong without any total looking wrong.
  3. Invoices. Check numbers, totals, line items and paid status. Know which invoice number was your last, because your new system's sequence should carry on from it.
  4. Clinical notes. Notes are health records you are required to keep. Confirm they come out with the original date, author and full text, and find out whether they are in the main export or a separate one.
  5. Files and attachments. Referral letters, scans and imaging reports are often stored apart from the data export. Find out how to get them out, and do it before you close the old account.

If any of these is missing or partial, you want to know now, while you still have weeks rather than hours to sort it out.

Stage 2: freeze the setup, and stop the new system talking

About a week before go-live, freeze the configuration of your old system. No new services, no new templates, no price changes. Every change you make to the old system from here has to be made twice, and the second copy is the one that gets forgotten.

At the same time, make sure the new system cannot contact a single patient. This is the step people skip, and it causes the worst day of any migration. Importing real future appointments into a system with reminders switched on means real people get real texts about visits that may already have moved. Whatever you are moving to, find its equivalent of a send freeze and turn it on before the first import.

Stage 3: the parallel week, with one calendar owner

Run both systems for a week, but not as equals. Pick one system to own the calendar, which is almost always the old one, and tell the whole team. Reception keeps booking where they always have. The new system gets a fresh copy of the data, and the team uses it to practise: open patients, write test notes, raise test invoices, find where things live.

The rule that matters is that bookings are only ever made in one place. Two systems both taking bookings for the same practitioner will eventually double-book a real patient, and no overnight sync can prevent it, because a sync runs after both bookings already exist. It can only report the clash.

Use the week to settle the questions only real use exposes:

  • Are services, prices and item codes set up per funder, and do test invoices price correctly?
  • Do the note templates match how your clinicians actually write?
  • Does every staff member have a login and the right level of access?
  • Are invoice and reminder templates in your practice's name, with the right contact details?

Stage 4: go-live day

Pick a quiet time; the end of a Friday works well. Then work through it in order:

  1. Finish the day in the old system, with everything booked, noted and invoiced.
  2. Take a final export or pull, so the new system has everything up to that afternoon.
  3. Re-check the totals and the last few days of appointments, especially anything booked or moved during the parallel week.
  4. Turn patient messaging on in the new system.
  5. Stop booking in the old system, and tell the team the new one is now the only source of truth.

Keep read access to the old system for as long as your arrangement with that vendor allows. You will want to look things up in it, and a read-only habit stops anyone being tempted to book there.

Stage 5: the first invoice run

The first invoice run is where you find out whether the switch worked, so give it extra time. Before you send anything, check that invoice numbers carry on from your old sequence, that each invoice is addressed to the right payer (plan manager, insurer or patient), that item codes and GST treatment are right for each funder, and that totals match what the same visits would have cost in the old system.

Then compare money owed. Everything that was outstanding on the day you switched should be outstanding in exactly one place, and someone should know which system they are chasing it from.

How AspireOS handles the move

We built AspireOS's move-in tools around the plan above. Under Settings → Integrations & data you can import team, services, patients, contacts, cases, notes, appointments and invoices from your current practice software or any spreadsheet, with your columns matched and duplicates skipped. Practices coming from your current system can also pull patients, team, contacts, appointments, invoices and cases across with an API key from your current system, and keep a nightly pull running through the parallel week. The switching from your current system guide sets out exactly what comes across and what does not.

Testing mode holds every patient message while you set up, and held messages are never sent later, so switching it off does not release a backlog. Invoice numbers carry on from your old system. The owner can open a private sandbox copy of the practice to practise in, and a go-live checklist turns each row green as it is done. AspireAi drafts and waits for a person to confirm, for the reasons we set out here, and the pricing page shows one plan, priced per person.

If you want to see how your own practice would look before you commit to a date, book a demo and bring your questions about the move.

Built for practices like yours

AspireOS is practice management for Australian allied health, mobile or clinic-based: scheduling with travel, funding-aware billing, and AspireAi, which drafts and waits for your OK.