How to Plan a Pharmacy Software Migration
Use a trial conversion to test the new system before cutover. This checklist covers data exports, reconciliation, rollback and handover.

Plan a pharmacy software migration by agreeing what data moves, rehearsing the conversion and testing a fallback before cutover. Verify conversion with record counts, sampled records and real workflows. Assign one person the go/no-go decision.
Key takeaways
- Collect an export manifest and map the fields before migration.
- Rehearse the switch with the vendors and the people using the system.
- Decide how to recover any records entered after cutover starts.
What should the migration team agree on?
Name a pharmacy decision-maker, a migration lead at each vendor and a staff lead for acceptance testing. Inventory the systems and interfaces involved. For each dataset, record the system of record, export format, import mapping, who may access it and how it will be verified. Agree how staff will retrieve historical records that remain outside the new system.
Separate product, supplier and sales data from any patient or dispensing records involved in the change. Use synthetic or appropriately prepared examples for preliminary tests and have the Designated Manager review the handling of sensitive data and continuity of service before any live rehearsal. Ontario College of Pharmacists community pharmacy resources
What belongs in the migration checklist?
| Stage | Evidence to keep | Who signs off |
|---|---|---|
| Export | File manifest, date range, record counts and read-back sample | Source vendor and data owner |
| Map | Field mappings, missing values, duplicate rules and unit conversions | Migration lead and staff lead |
| Rehearse | Timed trial, test results, unresolved records and treatment | Staff lead and migration lead |
| Reconcile | Counts by entity, open-item totals and sampled records including exceptions | Pharmacy data owner |
| Switch | Confirmed backup, final delta export, interface checks and go/no-go decision | Named pharmacy decision-maker |
| Hand over | Access list, reference files, training record and escalation contacts | Operations lead |
When should you roll back a cutover?
Write the stop conditions as observable events. A fictional migration might stop when an agreed critical workflow fails, when a dataset cannot be reconciled, or when the remaining time is shorter than the tested restoration window. Give every condition a decision owner and a deadline.
Rehearse both sides of the switch. If staff have already entered records in the new system, pause transactions and capture the changed records before restoring the prior system. Agree in advance who reconciles those changes, what can be re-entered safely and which interface queues need to stay paused until reconciliation. Where reversal cannot reliably preserve new activity, document a controlled forward-recovery option before go-live.
What should be ready for the first shift?
Give staff a short runbook with startup checks, a continuity procedure, support contact and the person who can approve changes. Assign ownership of unresolved exceptions and schedule a first-day review. Keep the same acceptance cases in use through the first operational close.
Use the pharmacy software selection scorecard to ask what each vendor will export, import and support. If data ownership or integrations are still unclear, discuss the migration scope with Wizy.
Frequently asked questions
What should you check in a sample pharmacy data export?
Check identifiers, date ranges, record counts, relationships and any in-scope attachments. Confirm how the team will retrieve the history that stays outside the new system.
Who decides whether a pharmacy software cutover can go ahead?
Name a pharmacy decision-maker before the trial. The vendors and staff lead supply evidence against the agreed checks, and the decision-maker records whether to proceed, pause or recover.
Can you roll back after staff enter records in the new system?
Only if the recovery plan accounts for those records. Pause new entries, capture the changes and reconcile them before resuming work. Rehearse forward recovery if reversal would leave records unreconciled.
