How to migrate telehealth platforms without losing subscribers
The technical migration is the easy part. The expensive part is card tokens, and whether your outgoing platform will release them. Here is how to find out before you commit.
Key takeaways
- Card token portability decides the cost of the whole migration. Everything else is a data transfer.
- If tokens cannot move, migrating means asking every active subscriber to re-enter payment details, and a meaningful share will not.
- Ask about token release in writing before you sign a new contract, not after.
- Sequence matters: build and test the new environment fully before moving a single patient.
- Migrating is cheapest immediately, and gets more expensive with every subscriber you add.
The only question that really matters
Patient records export. Order history exports. Storefronts get rebuilt. None of that is where migrations fail.
Migrations fail on stored payment credentials. If your current platform is the merchant of record, the tokens representing your patients' cards live in their processing account. Processors can migrate tokens between accounts, but only when the holding party agrees to release them.
If they do not, your only path is asking every active subscriber to enter their card again. Realistic response rates on that request make it, by a wide margin, the largest cost of switching, and it never appears on any invoice.
Find out before you are committed
Ask your current platform, in writing, whether they will support a token migration to a named processor, and how long it takes. Ask before you have signed anywhere else, because your leverage is highest while you are still a paying customer who has not announced they are leaving.
If the answer is no, or is vague, you now know the true cost of the switch and can decide with that number in hand rather than discovering it mid-migration.
Sequence the move so nothing overlaps badly
The failure mode is running two half-live systems at once. Avoid it by making the cutover a single event that everything else builds toward.
- Build and test fully on the new platform first: storefront, intake, eligibility rules, pharmacy routing, provider assignment. Place real test orders end to end.
- Export and import records with a reconciliation step. Count patients, active subscriptions and next-bill dates on both sides and confirm they match.
- Migrate tokens if they are portable, and verify with small test charges before relying on them.
- Cut over billing at a cycle boundary so no patient is charged twice or missed.
- Keep the old environment readable for a period. You will need to check something.
What to tell subscribers, and when
If tokens move cleanly, most patients need to be told very little: the brand is the same, the portal has changed, here is the new link. Over-communicating a change that does not affect them invites cancellations that would not otherwise have happened.
If tokens cannot move, the message is a genuine ask and should be treated as a campaign, not a notification. Give a reason, make the action take under a minute, sequence reminders, and expect to run it several times.
In both cases, make sure the statement descriptor on the new account matches what patients recognise. An unfamiliar descriptor produces both disputes and issuer declines at precisely the moment you least want them.
Migrate early or accept the cost
The arithmetic is unforgiving. If a switch costs you a percentage of your subscriber book, that cost scales with the size of the book. Migrating at 200 patients is an afternoon of annoyance. Migrating at 3,000 is a material revenue event.
Operators who know they are on the wrong platform and wait usually wait because the switch feels disruptive. It becomes more disruptive every month, not less.
Migration support at no cost, and no term to leave us later
PharmaBro provides white-glove migration support at no additional cost, including record import, reconciliation and token migration where the outgoing platform will release them.
The more useful commitment is the reverse one: because your brand owns the Stripe account from day one and there is no contract term, leaving PharmaBro is a 24-hour export, not a negotiation. We would rather keep earning the business than hold it.
Conclusion
A platform migration is a payments project wearing a data-transfer costume. Solve tokens first and the rest is logistics.
Ask the token question in writing before you sign anywhere. Sequence the cutover so the new environment is fully proven before a single patient touches it. And if you already know you are on the wrong platform, the cheapest day to move is today.
Frequently asked questions
Can I move my card tokens to a new platform?
Only if the platform holding them agrees to release them. Processors support token migration between accounts, but the holding party has to initiate it. If your brand already owns the merchant account, the question does not arise, because the tokens were never theirs to withhold.
How long does a telehealth platform migration take?
The build and test phase is typically the longest part and can run in parallel with your existing operation. The cutover itself should be a single event at a billing cycle boundary. Token migration timing depends entirely on the outgoing platform.
Will I lose patients when I migrate?
If tokens move cleanly, very few, provided you keep the descriptor recognisable and do not over-communicate. If tokens cannot move and subscribers must re-enter cards, expect meaningful attrition and plan the re-collection as a proper campaign.
References
Marcus ElleryHead of Payments and Billing
Works on the rebill engine, merchant routing and recovery logic. Spends most of his time on the unglamorous half of subscription telehealth: why a card failed, and whether it had to.