Switch stacks without missing a refill.
Running hundreds or thousands of patients a month on another platform — or on a stack of seven vendors? Migrations are a first-class path onto Lithos, not a special request. Here is exactly how one works.
Lithos StaffLithos migrations run in three phases: parallel-run your flows in sandbox while your current stack keeps serving patients, transfer records as data while our clinicians re-establish prescriptions against each patient’s refill date, then cut over state by state — each wave proven through a full refill cycle before the next moves. Patients stay in your app and never notice.
The playbook: three phases, no big bang
- Weeks 0–1 · Parallel-run. We mirror your intake, visit, and fulfillment flows in the Lithos sandbox while your current stack keeps serving patients. Nothing moves until you have seen your own flows working end to end — including the unhappy paths.
- Week 2 · Records come across. Charts and care plans transfer into Lithos. Our clinicians review incoming patients and re-establish prescriptions as part of onboarding, so refills continue without a gap.
- Weeks 3–4 · Cut over, state by state. Turn states on at your pace — start with one market, watch it run, then roll the rest. Your patients keep using your app the whole time.
What moves — and what doesn’t
- Records move as data. Charts, care plans, and history transfer ahead of each wave — audited against a sample export before the timeline is committed, so missing fields surface before they matter.
- Prescriptions are re-established, not ported. Ported prescriptions are a compliance smell. A licensed clinician in our network reviews each incoming chart and re-signs therapy, timed to land before the patient’s next refill date.
- The patient experience doesn’t move at all. Your brand, your funnel, your UI. The infrastructure changes underneath — which is why most migrations need no patient announcement.
How we know it’s working
Refill completion rate against your pre-migration baseline is the single metric that tells the truth — a patient whose refill lands on time never knew anything changed. Through every wave we track it alongside visit turnaround and support volume per state, and the rollback option stays open until each migrated state has cleared a full refill cycle. Old contracts wind down only after that, with your complete data export in hand on the way out.
Want the operator’s-eye version — the full risk register, patient-communication rules, and what to negotiate before you start? Read How to switch telehealth infrastructure without losing patients.
Coming from a specific platform?
Provider-by-provider playbooks, including what exports look like and what maps cleanly:
Frequently asked questions
Will our patients notice anything?
That is the design goal. Patients stay in your app and your brand throughout; what changes is the infrastructure behind it. The state-by-state cutover means any issue is contained to one market while the rest of your business keeps running on your current stack.
Do prescriptions transfer automatically?
Prescriptions are not ported as data. As each patient moves, a licensed Lithos-network clinician reviews their chart and re-establishes their prescriptions — the clinically clean way to switch prescribers, timed so refills are not interrupted.
How long does a migration take?
Plan for three to four weeks from kickoff to first cutover for a typical single-category business. High-volume or multi-category businesses usually roll states over a few additional weeks — the pace is yours to set.
What happens to our data if we ever leave?
It is yours in both directions. You own all patient and operational data on Lithos and can export it via API at any time — the same posture we benefit from when you arrive.
Get the Journal by email
Our best guides on building compliant telehealth programs — a couple a week, unsubscribe any time.
From first call to first patient, in weeks.
A 15-minute intro call, sandbox credentials the same day, go-live in 3–4 weeks — new launches and existing patient bases alike.