Switching dispensing providers is one of those operational decisions that looks straightforward until you're three weeks into it, mid-cycle on 600 active prescriptions, with patients asking why their medication is late. Then it feels like the most consequential mistake the clinic has made in years. It usually isn't — but only when the migration was planned properly from day one.

This is the playbook for clinics doing it for the first time. It covers when to switch, what to assess in the existing partner before triggering, how the 30-day migration unfolds, what patient communications should look like, and the regulatory boxes you have to tick whether you want to or not.

Common reasons clinics switch — service quality, pricing, tech, regulatory

Clinic owners don't switch dispensing providers for fun. The cost is real and the downside is real. They switch when one of four pressure points becomes unbearable.

Service quality. Same-day dispatch percentages slip. Clinical-check turnaround stretches. Stock-out rates climb. Patient complaints come in at a rate the clinic can't absorb. This is the most common trigger and the most defensible — service quality is measurable and the conversation with the existing partner is a productive starting point even if the switch ultimately happens.

Pricing. The admin client care fee structure that worked at 200 dispenses a month doesn't work at 1,500. Or the partner's pricing has crept up at successive renewals. Pricing-driven switches are legitimate but need careful diligence — the destination needs to be meaningfully better, not marginally cheaper, to justify the disruption.

Technology. The partner's dashboard doesn't expose the metrics the clinic actually needs. The API is missing endpoints. The EMR integration is one-directional. As the clinic professionalises, the tech debt accumulates on the partner's side and slows the clinic down.

Regulatory. The partner had a GPhC inspection finding that the clinic is uncomfortable with. Or there's a CD-register reconciliation issue that hasn't been resolved cleanly. Or the partner's MHRA posture on specials has drifted. Regulatory-driven switches are urgent and often non-negotiable.

What to assess in the existing partner before triggering

Before signing with a replacement, run the existing partner through a structured conversation. Even if the switch happens, this conversation gives you better leverage and (sometimes) the alternative answer of "the existing partner can fix this".

Three questions, in writing:

  1. What's the realistic timeline for closing the gap you care about? If they can credibly close it in 60–90 days, that's worth weighing against the migration cost.
  2. What's the commercial flexibility? Volume-based pricing review, fee structure renegotiation, additional features unlocked at no cost — there's often more room than the first conversation suggests.
  3. What's the offboarding process if we do leave? This isn't just due diligence — the offboarding terms shape your migration plan and the answer tells you whether the existing partner takes the relationship seriously.

If the answers are credible, give them the 60 days. If the answers are vague, defensive, or non-committal, start the replacement search immediately.

The 30-day migration plan — patients, data, in-flight orders, communications

A clean dispensing-provider switch unfolds in three phases over roughly 30 days. The phases overlap; they're not strictly sequential.

Phase 1 (days 1–10) — set up the new partner and validate the bridge.

  1. Sign the new partner's contract and DPA. Have your UK GDPR responsibilities documented before any patient data moves.
  2. Onboard prescribers, configure clinical SOPs, set up dispatch routing, validate API/EMR integration end-to-end.
  3. Run a small batch of low-risk dispenses through the new partner — maybe 5–10 per day for the first week. Validate the workflow, the documentation, the patient communication.
  4. Identify any operational gaps and resolve them before scaling traffic.

Phase 2 (days 11–25) — run both partners in parallel.

This is the critical phase. Most successful migrations run new and old providers in parallel for 14–30 days. New patients go to the new partner. Existing patients on active prescription cycles stay with the old partner until their next refill, at which point they transition.

In-flight prescriptions must be handled with clinical continuity — not orphaned mid-cycle. If a patient has a 90-day prescription on day 30 of that cycle, you don't try to migrate them to the new partner mid-cycle. They finish out the existing prescription at the old partner, then their next prescription goes to the new partner.

Phase 3 (days 26–30) — close out the old partner.

  1. Confirm there are no in-flight orders or pending dispenses at the old partner.
  2. Trigger the data handover — full patient records, dispense history, CD-register entries, audit trail. Patient data portability is a right under UK GDPR Article 20 and the old partner is required to comply.
  3. Receive final reconciliation statement and any outstanding admin client care fee payments.
  4. Confirm offboarding completion in writing.
Key takeaway

The migration risk is highest in Phase 2, when both partners are operating. Most clinics underinvest in the parallel-running phase, try to compress it below two weeks, and pay for that compression in patient confusion. Plan 14–21 days of overlap. It's cheaper than the alternative.

Patient communications that minimise churn

Patient communications are the part most clinics handle worst. The temptation is to tell patients as little as possible to avoid alarming them. The result is usually that they're more alarmed when the change actually happens.

The principles that work:

Clinics that handle the communications well lose under 5% of active patients through a migration. Clinics that handle them badly lose 20%+.

Data portability — what your old provider must hand over under UK GDPR

The data handover is where some migrations get ugly. It shouldn't.

Under UK GDPR Article 20, patient data portability is a right. Your old dispensing provider has a legal obligation to return patient data in a structured, commonly used, machine-readable format. They cannot withhold it because the relationship is ending. They cannot charge a fee for it (in most cases). They cannot drag the timeline beyond one calendar month, with a permitted extension of up to two further months for complex cases.

The dataset you should receive:

If the old provider stalls or claims commercial confidentiality, escalate in writing referencing Article 20. If the stall continues, the ICO complaints process is the next step — but in practice, a well-drafted letter from the clinic citing the statutory deadline usually resolves it within a week. (Our integrations page shows the kind of data structures and APIs that make portability a non-event.)

The cleanest migrations happen between providers whose offboarding terms were negotiated at signing. The ugliest happen between providers who never thought past the wedding day.

Risks during migration and how to de-risk them

Three risks dominate.

Patient confusion. The patient receives a delivery that looks slightly different and panics. Mitigation: clear advance communications (above) and a visible support route.

Clinical continuity gaps. A prescription gets stuck between providers — the old partner says it's gone, the new partner says it hasn't arrived. Mitigation: a written handover document per active patient, signed off by both pharmacy operations teams.

Regulatory exposure. A CD-register entry is missed at the seam between providers, or a DSAR lands during the transition and falls between desks. Mitigation: a single named person at the clinic owns regulatory coordination for the entire migration window. They have direct lines to both partners' superintendents.

None of these are exotic. They're all the normal failure modes of any operational transition. The clinics that get migration right are the ones that planned for these failure modes rather than hoping they wouldn't materialise.

What to do this week

If you're considering a switch:

Migration done well is invisible to patients and uneventful for the clinic team. Migration done badly is the thing that gets remembered for years. The difference is almost entirely in the 30 days of planning that precede the cut-over.