Practice Management Software Migration: What Transfers

A practice management software migration is not simply moving files from one system to another. It is a technical conversion, a configuration project and an operational change happening at the same time. Each has its own risks, decisions and opportunities for things to be quietly missed.

I have sat on both sides of this desk. Before I became a Certified SYSTEMologist, my first role as a practice manager threw me in with no experience and no formal handover. I taught myself as I went, and it was years before I completed my Diploma in Practice Management

If you are being handed a practice management software migration on top of an already full workload, I understand why it feels overwhelming. The practice still has to run. Patients still need care, accounts still need attention and the team still needs answers, while you are also expected to help move years of clinical and operational history into an unfamiliar platform.

A data conversion should not determine how the new software will operate. Start by mapping the Critical Client Flow (patient journey) before deciding what the new system needs to support.

Practice Management Software Migration, configuration and workflow redesign are different jobs

These three activities are often spoken about as if they were one project, but separating them makes the work easier to understand.

  • Migration moves available information from the old platform into the new one.
  • Configuration builds the settings, templates, fees, roles and integrations the new platform needs.
  • Workflow redesign decides how work should move through the practice and where the new system can remove manual steps or reduce risk.

A technically successful conversion can still produce a disappointing implementation when configuration and workflow redesign are treated as secondary tasks.

What generally transfers, and what usually does not

The exact scope depends on the platform you are leaving because every vendor makes different information available through its export process. Based on information confirmed directly with Xestro Support in July 2026, core patient and clinical information generally transfers.

This commonly includes patient demographics and contact information, appointments, clinical consultation notes, referrals and recalls, medications, letters, attachments and historical clinical information. Pathology and radiology results may also transfer when they are included in the source system’s export.

Practice configuration is different. Staff settings, calendars, appointment schedule and letter templates, billing items, fee schedules, bank account details and general database settings are usually rebuilt in the new platform. Financial information may be available as read-only history rather than becoming live transactional data in the new system.

There can also be exclusions that are easy to overlook: repeating appointments, information that has not been linked to a patient, and source-system fields that do not have an equivalent destination in the new platform.

That is why no general list, including this one, should replace written confirmation from your new software provider for your own conversion

Source-system quirks matter

The broad categories may be similar, but the details change according to the system you are leaving. For example, in a Genie Desktop migration to Xestro, letterhead images do not migrate because they are stored in a proprietary format. Archiving Genie documents before the final conversion helps preserve the letterhead within the archived document. Genie’s Scratchpad information also lands differently from a standard clinical consultation note.

Other platforms have different limitations involving observations, private health fund details, user-defined fields, financial history or patient forms. These are not minor technical curiosities. They affect what the team will be able to find and how confidently clinicians can rely on the new record after go-live.

The detailed system-by-system questions belong in a checklist, not in a blog article you have to remember under pressure.

 

Practice Management Software Migration

The trial conversion is a working review, not a preview

A trial conversion happens before the final capture. Its purpose is not simply to show that information appeared in the new system. It gives the practice an opportunity to check whether important information transferred, whether it landed in the expected fields and whether the result is usable in day-to-day work.

Choose a representative sample of patient records rather than reviewing only the easiest examples. Include patients with long clinical histories, scanned correspondence, recurring appointments, recalls, referrals, results and any source-system fields your clinicians use regularly.

Compare those records with the live system and document every discrepancy. Do not rely on someone remembering what looked unusual during a screen-sharing session. The review should have a named owner, written findings and clear sign-off authority.

Final capture creates a controlled changeover period

Once the trial has been reviewed, the practice agrees on the final data-capture date and go-live date. These are separate moments. The final capture takes a snapshot of the source data for conversion; the practice then begins working in the new live system once conversion is complete and access is confirmed.

Anything entered into the old system after final capture will not appear in the new one. The practical goal is therefore not to ‘eliminate a gap’ but to control the work performed during that changeover period.

Reduce the clinical and administrative load where possible. Depending on the practice and the confirmed conversion timeframe, that may mean moving consulting sessions, limiting new bookings, blocking part of the diary or closing for a short period. The conversion timeframe must be confirmed with the new software provider; it should never be assumed from another practice’s experience.

Where work must continue, create a temporary capture system. Record every new booking, payment, clinical entry, referral, result or patient change that will need to be entered into the live platform. Assign one person to maintain the register and another to verify that every item has been re-entered after go-live.

Do not make the first live day harder than it needs to be

Going live with a full appointment book forces the team to learn unfamiliar pathways under normal, or greater, clinical pressure. That increases the likelihood of mistakes, missed steps and workarounds becoming established simply because staff need to keep the day moving.

A lighter diary for the first few days creates room to ask questions, correct configuration and reinforce the intended workflows. This is not lost productivity. It is a practical change-management decision that helps the team succeed and protects patient service while new habits form.

Keep access to the old system

Even after sign-off, the old system may still be needed for verification, historical reference or information that was intentionally excluded from conversion. Confirm how long it will remain available, whether it becomes read-only, how it will be backed up and who will retain access.

This should be resolved before go-live, rather than discovered months later when someone needs an older document or financial record.

What a well-managed migration looks like

A well-managed migration does not promise that nothing unexpected will happen. It makes responsibilities, decisions and risks visible early enough to manage them.

  • The practice knows what will transfer and what must be rebuilt.
  • The trial conversion is reviewed against representative live records.
  • Sign-off is documented and completed by someone with the appropriate authority.
  • The final-capture-to-go-live period has a written temporary-record process.
  • The first live days have enough capacity for learning and correction.
  • The team knows where to raise problems without feeling that they are criticising the decision to change systems.

Get that sequence right and go-live becomes what it should be: the beginning of a genuine improvement, rather than a crisis the team is expected to absorb.

Why This Is Worth Doing Now

The most important practice management software migration decisions are made before final data capture and go-live. Once the practice is operating in the new system, missing information, incomplete configuration and unclear workflows become harder to correct because the team is already managing patients while learning unfamiliar processes.

Clarifying what will transfer, reviewing representative patient records and planning the changeover period now gives the practice time to address gaps before they become live operational problems.

Before Your Next Migration Meeting

Ask your software provider to confirm what will transfer, what must be rebuilt and how information excluded from the conversion will remain accessible. Then agree who will review the trial conversion, who has authority to approve it and how work completed between final capture and go-live will be recorded.

The Xestro Migration Checklist brings the key preparation steps, trial-conversion questions, cutover actions and source-system notes into one practical reference. It includes specific notes for Genie Desktop, VIP, Gentu, Shexie, Clinic to Cloud and Cliniko.

Migration requirements can change, so always confirm the current position for your practice with Xestro Support.

Access the Xestro Migration Checklist

Working With Denise Pacey

If reviewing your migration plan raises more questions than answers, or your practice needs help translating the technical conversion into a workable implementation plan, this is exactly the work Pace MediSystems is designed to support.

Denise works with specialist medical practices across Australia to prepare for practice management software migration, review trial-conversion outcomes, identify configuration gaps and create practical changeover plans.

Pace MediSystems works alongside your practice and software provider, helping you ask the right questions, make informed decisions and move into the new system with clarity and confidence.

About Denise Pacey

Denise Pacey is the founder of Pace MediSystems and a Certified SYSTEMologist with over two decades of experience in specialist medical practice management. She works with medical practices across Australia in three areas: practice systemisation, Xestro implementation, and coaching and mentoring.

Pace MediSystems. Systemise for Success.

Share this post: