Why programs switch, and when it is worth it
The common triggers are economic and operational: per-patient costs that drifted from the pitch, medication economics that cap your margin, support that decays at volume, or a vendor pivoting away from your segment. The test for whether switching is worth the disruption is arithmetic plus trust: model twelve months of the margin difference at your realistic volume, subtract a real migration cost (weeks of split attention, some churn), and weigh what reference calls say about the incoming platform's operations.
Two wrong reasons to switch: a single bad month (fix the escalation path first; a switch is not a support ticket), and a sales pitch whose numbers you have not verified in writing. The diligence checklist you would run on a first platform applies double on a second one, because now you know which questions hurt.
Before anything: the exit-terms audit
Read your current agreement for five things before any vendor conversation: termination notice and windows; exclusivity or non-compete language that constrains where you can go; who owns the patient list and marketing data, in the agreement's words; what patient records you receive on exit, in what format, on what timeline, at what cost; and any wind-down obligations. What you find decides your timeline and your negotiating posture, and finding it late is how migrations become emergencies.
Patient clinical records deserve their own line: they belong to the clinical entity that delivered care, under record-retention rules, and what transfers to a new platform's clinical entity (and how patients authorize that) varies by structure and state. Get the incoming platform's clinical team to walk you through their transfer process before you commit; a platform that has done this before has a crisp answer.
The one question that predicts migration pain: 'What exactly do we receive on exit, in what format, and in how many days?' If you cannot answer it from your current agreement today, start there, not with vendor demos.
The parallel-run pattern
Cold cutovers are how you turn a platform switch into a churn event. The pattern that works runs three phases: connect (the new platform integrates behind your existing storefront and funnel while patients notice nothing), parallel-run (route a defined slice of volume, usually new patients first, through the new stack and compare economics and operations side by side for a few billing cycles), and cut over (move the book once the numbers and the support experience win, then wind down the old contract inside its notice terms).
New-patients-first matters: routing new signups to the new platform proves the whole flow (intake, visit, fill, billing, support) without touching anyone's existing care. Existing patients move later, in cohorts, each with clean continuity of their prescriptions and billing rather than one big-bang weekend.
The actual migration: prescriptions, billing, support
Prescription continuity is the part that loses patients silently. A new clinical entity generally means a new clinician relationship and new prescriptions, which takes an evaluation touch; plan it so each patient's next refill is issued by the new stack before the old one stops filling, and confirm with the incoming platform exactly how their clinicians handle transfers of care, state by state. A gap between the last old fill and the first new one is the single most common way switched programs bleed.
Billing continuity is the quiet twin: new merchant setup means cards get re-entered or re-authorized, and every re-entry is a churn opportunity. Sequence billing moves with an incentive attached and dunning ready, and keep the old subscription's cancellation aligned to the new one's first successful charge, not to a calendar date.
Support has to hold both worlds for a while: patients mid-migration will contact whichever brand surface they remember. One shared FAQ, one escalation path spanning both platforms, and your team briefed on where any given patient's care currently lives.
- Map every active patient's next-refill date before scheduling cohorts
- New patients route to the new platform first; existing patients move in cohorts
- Each cohort's new prescriptions issue before the old platform's last fill lapses
- Old subscription cancels on the new one's first successful charge
- One patient-facing FAQ and one escalation path across both stacks for the whole window
What to tell patients, and when
Patients do not care about your vendor stack; they care that care continues and nothing surprises their card. The communication that works is short, early per cohort, and concrete: what stays the same (the brand, the program, the price unless it improves), what changes (a new portal login, a re-consent or evaluation touch where required), and what they need to do, with the ask kept to one action. Silence is worse than an honest 'here is what is changing'; surprise re-intake with no warning is worst of all.
Where the switch improves something real (faster turnaround, medication included, better pricing), say so plainly without disparaging the outgoing vendor, and without promising clinical outcomes. The move is a service upgrade story, not a drama.
How EmbedCare runs switches
Switching is a first-class path on EmbedCare, and it follows exactly this playbook: connect behind your existing storefront, parallel-run a volume slice with the economics compared in writing, then cohort cutovers with prescription and billing continuity managed by the platform's clinical and payments teams. Flat product rates fixed in a signed partner agreement make the twelve-month arithmetic knowable before you commit, and the exit terms you should demand from us are the ones this guide told you to demand from everyone.
Frequently asked
- How do I switch telehealth platforms without losing patients?
- Three disciplines: audit your current agreement's exit terms first (notice, data, records, exclusivity); run the new platform in parallel (new patients first, then existing patients in cohorts) instead of a cold cutover; and manage prescription and billing continuity so each patient's next refill and next charge land on the new stack before the old one stops. Most switch churn comes from lapsed refills and failed card re-entries, not from patient loyalty to the old vendor.
- How long does switching telehealth platforms take?
- Plan in billing cycles rather than days: connecting and proving the new flow on new patients typically spans a cycle or two, and cohort moves of existing patients a few more, bounded by your old contract's notice terms. A rushed big-bang weekend is the version that loses patients; the parallel-run version costs calendar time and saves the book.
- Do we keep our patient records when we leave a platform?
- It depends on your agreement and the clinical structure: records belong to the clinical entity that delivered care under retention rules, and what you receive on exit (format, timeline, cost) is a contract term worth knowing before you announce anything. Transfers of care to a new platform's clinicians involve patient authorization steps that vary by state; ask the incoming platform's clinical team to walk their process before committing.
- Will patients have to redo intake after a switch?
- Often some clinical touch is required, because a new clinical entity generally means a new clinician relationship and new prescriptions. The difference between a churn event and a non-event is handling: warn the cohort, keep the ask to one guided action, time it before their refill needs it, and pair it with something that improved. Surprise re-intake with a lapsed refill is the failure mode.
- When is switching platforms a mistake?
- When the trigger is one bad month rather than a trend (escalate first; switching is not a support ticket), when the new vendor's numbers exist only in a pitch (get the all-in per-patient cost in writing and run references), or when your exit terms make the timing punitive and waiting a quarter changes the math. The switch case is durable economics and operations, verified the same way you should have verified the first platform.
Want pricing for your program, and the Rx menu that goes with this?
The partner overview in one email; a human follows up with pricing scoped to your program.