# Migrating Practice Management Software: How to Switch Systems Without Losing Patients Publisher: Virtual Consultant Online Author: Virtual Consultant Online Published: 2026-10-07 Updated: 0001-01-01 Canonical URL: https://virtualconsultant.online/blog/migrating-practice-management-software-orthodontic-switch Citation metadata: https://virtualconsultant.online/citation.json?url=https%3A%2F%2Fvirtualconsultant.online%2Fblog%2Fmigrating-practice-management-software-orthodontic-switch Changing practice management software is one of the highest-stakes IT projects an orthodontic practice undertakes. The new system may promise better scheduling, reporting or patient communication, but the risk sits in the move itself: patient records, radiographs, photographs, consent forms, appointment histories and financial ledgers that must arrive complete, accurate and secure, while patients mid-treatment keep turning up for adjustments. This guide explains how to plan a migration so that no patient is lost, no record goes missing and no regulator or patient has cause for concern, from the first scoping decision to switching off the old system. Key takeaway A software migration is a records and governance project first and an IT project second. Decide in advance what counts as the patient record, who is accountable for each data category, how you will prove nothing was lost, and what happens to patients who are partway through treatment on cutover day. If you only want better enquiry, quote and follow-up workflow, a layer around your existing system may deliver more value with far less risk than a full replacement. ## Should you migrate at all, or add a workflow layer? Before planning a migration, check that migration is what you need. Practices often change systems because of a single weak area, such as enquiry tracking, quote follow-up or reporting, while the core of the existing system, scheduling and clinical records, works reliably. Replacing everything to fix one gap exposes every patient record to risk. Replace the system when The core records and scheduling system is the problem. It cannot meet your security, access or audit needs It is unsupported or being withdrawn by the vendor Staff cannot get reliable data out of it You are consolidating several sites onto one platform Add a workflow layer when The records system is sound but the commercial workflow is thin. Enquiries and quotes are tracked in spreadsheets or inboxes Follow-up depends on individuals remembering You lack reporting on conversion and accepted cases Retraining every team role would cost more than the gain A workflow layer sits around your existing records and scheduling system and adds enquiry capture, photo intake, quote status, follow-up reminders and conversion reporting. That is the approach described on our practice management software alternative page , and it changes far fewer things at once than a full replacement. If you decide a full migration is right, the rest of this guide applies. ## What counts as the patient record that must be migrated? The patient record is wider than most migration project plans assume. GDC standard 4.1.1 states that radiographs, consent forms, photographs, models, audio or visual recordings of consultations, laboratory prescriptions, statements of conformity and referral letters all form part of patient records where they are available. Standard 4.1.3 adds that you must meet your responsibilities under current legislation and follow national advice on retaining, storing and disposing of patient records. 4.1.1 GDC standard listing what forms part of the patient record, from radiographs to referral letters 4.1.3 GDC standard requiring you to follow legislation and national advice on retaining, storing and disposing of records Reg. 17 CQC regulation on good governance, including securely maintaining accurate, complete and detailed records Practices in England regulated by the Care Quality Commission also have to meet Regulation 17 on good governance, under which providers must securely maintain accurate, complete and detailed records for each person using the service. A migration that drops a radiograph or corrupts a consent form is therefore a regulatory problem as well as a clinical one. Data category Examples Common migration risk Demographics and contacts Names, dates of birth, addresses, guardians, preferred contact method Duplicate patients, truncated fields, lost communication preferences Clinical notes Examination findings, treatment plans, appointment notes Notes flattened into one field and losing dates or authorship Images and radiographs Intraoral and extraoral photographs, OPGs, cephalometric images, scans Files left in the old image archive or renamed so they no longer match the patient Consent and correspondence Signed consent forms, referral letters, treatment agreements Scanned documents not attached to the correct patient or case Appointments and recalls Past visits, booked appointments, review and retention recalls Future appointments not carried across, recall intervals reset Financial records Payment plans, deposits, ledger balances, invoices Balances that do not reconcile; instalment schedules restarted Contract and activity data NHS contract activity information where relevant Reporting continuity broken across the cutover date ## How do you protect patients' data during the move? Data protection law applies throughout, and migration is a period of heightened risk. The ICO's security guidance expects you to put in place appropriate technical and organisational measures to protect personal data, and for health data the bar is high. Your obligations are simplest to meet if you plan them as part of the project rather than at the end. Carry out a DPIA for the new system. A new system holding large volumes of special category data is a classic reason to document the risks and controls before you go live. Review the vendor contract. Confirm who is controller and who is processor, where data will be stored, what sub-processors are involved and what happens to your data if you leave. Encrypt every transfer. Extracts should move over secure channels and not through email attachments or personal storage. Limit who can see the extract. Only named people should handle export files, and test data should be anonymised wherever possible. Keep an audit trail. Record what was exported, when, by whom, where it went and when copies were deleted. Do not forget patients' rights. Individuals can ask for a copy of their records at any time, including during a migration, and the ICO's guidance on the right of access sets the time limit for responding. Make sure the team knows where to retrieve a record while data sits partly in each system. ## What is a realistic migration plan? A good plan moves in phases, each with an owner and an output. Exact durations depend on your data volume and vendor, so ask the supplier for a written timetable and treat any vendor claim of a trivial switch with caution. Phase What happens Who owns it Output 1. Scope Decide what must move, what will be archived and what will be left behind; set success criteria. Practice owner and manager Migration scope and risk register 2. Due diligence Assess the new vendor's security, support, data export and import capability. Practice manager with a data protection lead Vendor assessment, DPIA and contract 3. Data audit Find duplicates, incomplete records and files stored outside the system. Practice manager and clinicians Cleaned data set and exception list 4. Mapping Map every old field to a field in the new system and agree how gaps are handled. Vendor with practice lead Signed-off mapping document 5. Test migration Import a sample into a test environment and compare it with the source. Vendor, clinicians and reception Reconciliation report and fixes 6. Training Train each role on the new workflows before go-live. Practice manager and vendor Role-based training record 7. Cutover Freeze the old system, run the final migration and verify before reopening. Named cutover lead Verified live system and fallback plan 8. Aftercare Reconcile, resolve exceptions and keep the old data accessible read-only. Practice manager Reconciliation sign-off Add enquiry and quote workflow without replacing your records system If your gap is lead tracking, quote status and follow-up rather than clinical records, a workflow layer avoids a migration altogether. Try the patient journey to see how enquiries and quotes are captured. Try the quote journey → ## How do you keep patients in treatment safe through cutover? Patients mid-treatment are the people most exposed to a migration. A fixed appliance patient who is due for a review, a retention patient due a check, or a family waiting on a debond date depends on the next appointment being where the practice expects it to be. Build specific protections for them. Export a treatment-in-progress list before the freeze. Include the next planned appointment, current stage, appliance and any outstanding actions. Verify every booked appointment after import. Compare a printed list from the old system with the new calendar line by line. Plan the cutover for a quiet clinical period. Use your own appointment data to find it, rather than a generic assumption. Prepare a fallback. Keep a read-only copy of the old system, and a paper process for emergencies during the first days. Tell patients early and plainly. A short message explaining that systems are changing, that appointments are unaffected and who to contact if something looks wrong prevents confusion. Patient communication preferences and consents travel with the data. If marketing consent, reminder preferences or contact restrictions do not migrate, you may message people who opted out or fail to remind people who opted in. Treat them as data categories in their own right during mapping. Important Do not retire the old system until you have reconciled the new one against it and agreed how long the old data must be kept. Records you are required to retain do not disappear because you changed software. Keep the legacy data accessible, secured and read-only for the period your national retention guidance requires, then delete it securely and record that you did. ## How do you check that nothing was lost? Trust the migration only after you have tested it. Reconciliation means comparing counts and samples between the old and new systems, and it should be done by people who know the data, not only by the vendor. Agree the tests in advance and keep the evidence. Check Method Pass criterion Patient counts Compare total active and archived patients in both systems. Numbers match, with every difference explained. Appointment integrity Check all future appointments for a sample week plus all treatment-in-progress patients. No missing, duplicated or moved appointments. Image and radiograph linkage Open images for a random sample of patients across several years. Every sampled image opens and matches the right patient. Consent and letters Check that signed forms and referral letters are attached to the correct cases. No orphaned documents. Financial reconciliation Compare ledger totals and a sample of instalment schedules. Balances agree to the pound; schedules continue correctly. Permissions and audit Test that each role sees only what it should and that actions are logged. No over-broad access; audit trail works. ## What should you ask a vendor before you sign? The migration is only as good as the supplier's export and import capability, and the contract should reflect that. Ask the questions below in writing and keep the answers with the project file. Which data formats can you export from the old system and import to the new one, and what is not supported? Will you perform a test migration with our data before we commit, and who signs off the results? Where is our data stored and processed, and which sub-processors have access? What happens to our data, and how quickly, if we end the contract? How are audit trails, user permissions and backups handled? What support is available on and after cutover day, and at what hours? What costs are not included, such as data cleansing, extra imports or training? Our software onboarding guide covers how to structure the first 30 days after go-live, and the procurement checklist sets out the wider questions to ask before you buy. For the people side of the change, see our guide to training your team for remote consultations , which applies the same role-based approach. ## How do you reduce risk by changing less at once? The safest migrations change as little as possible. If your records system is reliable, keep it, and add the commercial and communication workflow around it. Virtual Consultant Online is designed to work in this way: it handles enquiry capture, guided photo intake, indicative quotes, follow-up reminders and reporting on accepted patients, and includes patient import tooling for getting existing contacts in. It does not replace charting, imaging archives or contract ledgers, so your clinical record stays where it is. You can see how the pieces fit on the orthodontist software overview . Improve your workflow without risking your records Add enquiry capture, quote tracking and follow-up around the systems you already trust, or talk through what a safe migration would involve. See how it works for clinicians → ## FAQs ### How long does it take to migrate orthodontic practice management software? It depends on the volume and quality of your data, the vendor's import capability and how much testing you do, so ask the supplier for a written timetable based on your own data. Allow for a data audit, a test migration, training and a post-go-live reconciliation, not just the cutover itself. ### What counts as a patient record when switching software? Under GDC standard 4.1.1, patient records include radiographs, consent forms, photographs, models, audio or visual recordings of consultations, laboratory prescriptions, statements of conformity and referral letters where available. A migration plan should cover all of them, not just notes and demographics. ### Do we need a DPIA when changing practice management system? Often yes. Moving large volumes of special category health data into a new system is a typical trigger for a data protection impact assessment, which records the risks and the controls you put in place. Carry it out before go-live and review the vendor contract at the same time. ### How do we protect patients in the middle of treatment during a switch? Export a list of every patient in treatment with their next appointment and current stage before the freeze, verify each booked appointment after import, and keep a read-only copy of the old system and a fallback process for the first days. Tell patients early that appointments are unaffected. ### How long must we keep the old system's data after migrating? Records you are required to retain remain subject to retention rules after you change software. GDC standard 4.1.3 requires you to follow legislation and national advice on retaining, storing and disposing of records, so keep legacy data secure and accessible until the relevant period ends, then delete it securely and document that. ### Is a workflow layer an alternative to replacing our practice management system? It can be, if your records and scheduling system works but enquiry tracking, quote follow-up and conversion reporting are weak. A workflow layer adds those functions around your existing system and avoids moving clinical records, which removes most of the migration risk. ### Will my orthodontic appointments be affected if my practice changes software? A well-planned switch should not affect your appointments, and the practice should check your next booking after the move. If you receive a message about the change or notice a missing appointment, contact the practice directly. ### Can I still ask for a copy of my records while my practice changes its system? Yes. You have a right to access your personal data, including your dental records, at any time, and the practice must respond within the legal time limit even during a software migration. ### How long does it take to migrate orthodontic practice management software? It depends on the volume and quality of your data, the vendor's import capability and how much testing you do, so ask the supplier for a written timetable based on your own data. Allow for a data audit, a test migration, training and a post-go-live reconciliation, not just the cutover itself. ### What counts as a patient record when switching software? Under GDC standard 4.1.1, patient records include radiographs, consent forms, photographs, models, audio or visual recordings of consultations, laboratory prescriptions, statements of conformity and referral letters where available. A migration plan should cover all of them, not just notes and demographics. ### Do we need a DPIA when changing practice management system? Often yes. Moving large volumes of special category health data into a new system is a typical trigger for a data protection impact assessment, which records the risks and the controls you put in place. Carry it out before go-live and review the vendor contract at the same time. ### How do we protect patients in the middle of treatment during a switch? Export a list of every patient in treatment with their next appointment and current stage before the freeze, verify each booked appointment after import, and keep a read-only copy of the old system and a fallback process for the first days. Tell patients early that appointments are unaffected. ### How long must we keep the old system's data after migrating? Records you are required to retain remain subject to retention rules after you change software. GDC standard 4.1.3 requires you to follow legislation and national advice on retaining, storing and disposing of records, so keep legacy data secure and accessible until the relevant period ends, then delete it securely and document that. ### Is a workflow layer an alternative to replacing our practice management system? It can be, if your records and scheduling system works but enquiry tracking, quote follow-up and conversion reporting are weak. A workflow layer adds those functions around your existing system and avoids moving clinical records, which removes most of the migration risk. ### Will my orthodontic appointments be affected if my practice changes software? A well-planned switch should not affect your appointments, and the practice should check your next booking after the move. If you receive a message about the change or notice a missing appointment, contact the practice directly. ### Can I still ask for a copy of my records while my practice changes its system? Yes. You have a right to access your personal data, including your dental records, at any time, and the practice must respond within the legal time limit even during a software migration. ## References - General Dental Council: Standards for the Dental Team, Principle 4 (maintain and protect patients' information) (https://standards.gdc-uk.org/pages/principle4/principle4) - GDC standards 4.1 and 4.2 on keeping complete and accurate patient records, what forms part of the record, retention and confidentiality. - Care Quality Commission: Regulation 17, Good governance (https://www.cqc.org.uk/guidance-regulation/providers/regulations-service-providers-and-managers/health-social-care-act/regulation-17) - CQC guidance on the good governance regulation, including the requirement to securely maintain accurate, complete and detailed records for each person using the service. - Information Commissioner's Office: A guide to data security (https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/security/a-guide-to-data-security/) - ICO guidance on appropriate technical and organisational security measures for personal data under UK GDPR. - Information Commissioner's Office: Right of access (https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/individual-rights/right-of-access/) - ICO guidance on individuals' right to obtain a copy of their personal data and the time limit for responding. - General Dental Council: Standards for the Dental Team, Principle 4 (maintain and protect patients' information) (https://standards.gdc-uk.org/pages/principle4/principle4) - GDC standards 4.1 and 4.2 on keeping complete and accurate patient records, what forms part of the record, retention and confidentiality. - Care Quality Commission: Regulation 17, Good governance (https://www.cqc.org.uk/guidance-regulation/providers/regulations-service-providers-and-managers/health-social-care-act/regulation-17) - CQC guidance on the good governance regulation, including the requirement to securely maintain accurate, complete and detailed records for each person using the service. - Information Commissioner's Office: A guide to data security (https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/security/a-guide-to-data-security/) - ICO guidance on appropriate technical and organisational security measures for personal data under UK GDPR. - Information Commissioner's Office: Right of access (https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/individual-rights/right-of-access/) - ICO guidance on individuals' right to obtain a copy of their personal data and the time limit for responding.