A clinic software migration is complete when your team can find the right patient, continue the next visit and explain what happened before the switch. A successful file upload is only one part of that result.
Start with an inventory of the information your clinic uses. Then agree how each category will be transferred, checked or retained. This checklist is a planning framework for a GP practice changing systems; the supported transfer method depends on the source software and the receiving system.
1. Name the owners and define the changeover
Assign a clinic lead who can approve the working process and a data lead who can answer questions about exports. Include a doctor, reception and dispensing staff in acceptance checks. Agree who at each vendor will resolve a missing field, rejected record or opening-balance discrepancy.
- Record the proposed changeover date, the final export window and the person who can postpone the switch.
- Define the last point at which staff enter new information into the old system.
- Agree a documented procedure for visits that span the changeover and information received after the final export.
- Keep a decision log with the outstanding question, owner, agreed answer and verification evidence.
2. Separate the data into useful categories
- Patient identity and contact details: names, phone numbers, identifiers, custom fields and potential duplicates.
- Clinical history: dated visits, clinician attribution, notes, diagnoses, prescriptions and investigation entries.
- Documents and files: attachments, labels, certificates or other material that needs its patient and visit context.
- Catalogue and stock: medicine identity, units, batches, expiry, quantity, cost, selling price and opening balances by location.
- Future work: appointments, practitioner schedules and any follow-up task the team must continue.
- Money: unpaid bills, deposits, refunds, panel references and the basis of the opening financial position.
For each category, record the source, export format, destination and acceptance check. Do not let “patient data imported” stand in for agreement on all six. A contact record may transfer correctly while its earlier consultation documents remain in a separate archive.
3. Inspect a sample before committing the full transfer
Ask for a representative sample through an agreed secure route. Include the awkward cases: two people sharing a family phone, a duplicate record, an amended visit, a patient with attachments and a partially paid bill. Use synthetic examples for early demonstrations; use authorised clinic data only within the agreed migration process.
Check meaning as well as file structure. Identify the date format, time zone, stock unit and whether blank means unknown or zero. Preserve source identifiers where the receiving process supports them, so a reviewer can trace a question back to the original record.
- Compare total exported records with accepted, rejected and deliberately excluded records.
- Review possible duplicates before merging; a matching phone number alone may not establish that two records belong to one patient.
- Open sample records as the staff member who will use them, not only through an administrator account.
- Record transformations such as renamed fields or mapped medicine codes, and approve the result.
4. Confirm what Watson can import
Watson supports contact import workflows that include CSV and vCard sources, field mapping, preview classifications and selection before committing. The review can distinguish new contacts, enrichment of existing contacts, duplicates, invalid entries and records needing attention. Supported custom CSV fields can be mapped as part of that process.
That contact workflow does not establish a universal import for clinical histories, documents, future appointments or financial balances. Those categories need a source-specific assessment and an agreed destination or historical-access method.
Opening stock is a separate process. Watson can record imported opening balances and hold quantities that lack confirmed expiry information for a later release step. An imported quantity or nearest-expiry date does not reconstruct the physical batches on your shelves. The dispensing team should verify the actual stock and expiry information before release.
Review the supported scope with the team through Switching to Watson and the Pharmacy and inventory workflow.
5. Decide how historical information stays available
Some history may remain in the previous system or an agreed archive. Establish how an authorised clinician will find it during a visit, what identifying information links it to the new record and how long that access is available under the clinic’s requirements and vendor agreement.
Resolve access and export arrangements before ending the old subscription. Check whether the archive is searchable, whether attachments open and whether access depends on a licence or vendor account. Do not assume that keeping a spreadsheet provides the same working context as keeping the original visit.
Confirm clinical data scope, access, retention, export and deletion arrangements in the applicable terms. Watson’s security and patient data page lists the matters to settle during evaluation; the agreement should explicitly cover the clinical functions being enabled.
6. Rehearse the first clinic day
- Reception finds a returning patient and registers a new walk-in. A booked patient checks in once.
- The doctor opens the intended visit and can reach the agreed historical information.
- Dispensing staff review a prescription, select usable stock and confirm supply.
- The cashier reviews the bill, records collection and opens the resulting document.
- The clinic lead checks incomplete visits, unpaid amounts and any import exceptions with their assigned owners.
Include the people covering different shifts or branches. Test the actual computers, label or receipt arrangements, permissions and patient communication channels planned for the changeover. Record any manual step in the staff instructions.
7. Approve the switch and reconcile afterwards
Set explicit acceptance conditions: critical records verified, stock and balances agreed, staff able to perform their work, and a usable historical-access path. Decide in advance which unresolved issue would postpone the switch. Keep a clinic-approved continuity procedure available if a device, connection or workflow is unavailable.
After the switch, reconcile the first day’s visits, collections and stock movements. Log discrepancies with the source reference and the action taken. Avoid reopening uncontrolled entry in both systems, which makes it harder to identify the authoritative record.
Keep the migration decision log, accepted totals and unresolved exceptions with the clinic’s handover records. That gives the team a clear answer when someone asks where a piece of information went or who approved a change.