Switch platforms without missing a refill
Running hundreds or thousands of patients a month on another platform, or on a stack of vendors? Migrations are a first-class path onto Lithos: parallel-run first, move records, then cut over state by state.
- TXTexasparallel
- FLFloridaparallel
- CACaliforniaparallel
- NYNew Yorkparallel
- OHOhioparallel
Three phases, no big bang
Parallel-run in the sandbox
We mirror your intake, visit and fulfillment flows in the sandbox while your current stack keeps serving patients. Nothing moves until you’ve seen your own flows work end to end, including the unhappy paths.
Records come across
Charts and care plans transfer into Lithos. Our licensed providers review incoming patients and re-establish prescriptions as part of onboarding, so refills continue without a gap.
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 changes, and what doesn’t
| Item | How it moves | What patients see |
|---|---|---|
| Charts and history | Transferred as data ahead of each wave, checked against a sample export before dates are set | Nothing |
| Prescriptions | Re-established by a licensed provider after chart review, not ported | Their next refill arrives on time |
| Patient experience | Doesn’t move: your brand, your funnel, your app | Nothing |
| Pharmacy | Routed to your pharmacy partners or ours, state by state | Shipping updates as before |
Three numbers, watched through every wave
Refill completion
Tracked against your pre-migration baseline. A patient whose refill lands on time never knew anything changed.
Visit turnaround
Tracked per state through every wave, so a slow market shows up before patients feel it.
Support volume
Tickets per state, before and after. Rollback stays open until each state clears a full refill cycle.
Playbooks by platform
What exports look like, what maps cleanly, and what to line up before you start.
Will our patients notice anything?
That’s the design goal. Patients stay in your app and your brand throughout; what changes is the infrastructure behind it. Cutting over state by state contains any issue to one market.
Do prescriptions transfer automatically?
No. Prescriptions aren’t ported as data. As each patient moves, a licensed provider reviews their chart and re-establishes the prescription, timed so refills aren’t interrupted.
How long does a migration take?
Weeks, not a year. Most teams cut over their first state soon after kickoff, then roll the rest at their own pace. Your refill calendar sets the tempo, and we commit to dates on the first call.
What happens to our data if we ever leave?
It’s yours in both directions. You own all patient and operational data on Lithos and can export it through the API at any time.
For the full risk register (refill gaps, prior-auth continuity, patient communications), read our switching guide.
Plan your migration
Book a call and we’ll map your states, waves and dates with you. You can start parallel-running in the sandbox right away. On the call:
- Your patient map and refill calendar
- Data export and record transfer
- A cutover plan with dates