---
title: "How to switch telehealth platforms without losing patients"
description: "How to switch telehealth platforms: what moves, prescriptions, stored cards, refill-date cut-overs, patient notice, LegitScript and a realistic timeline."
canonical: "https://cuvo.co/blog/how-to-switch-telehealth-platforms"
last-updated: "Nov 15, 2026"
keywords: ["how to switch telehealth platforms", "switch telehealth platforms", "telehealth platform migration", "migrate patients to a new telehealth platform", "change white label telehealth provider", "telehealth vendor lock-in", "how to leave openloop"]
---
# How to switch telehealth platforms without losing patients

By Priya Raman, Director of Partner Growth. Published Nov 15, 2026. Growth.

Brands leave a telehealth platform for a short list of reasons: it breaks whenever something changes, the brand cannot edit its own prices or intake, or a revenue share or fixed medication cost leaves no room to price. What holds them back is the move itself: losing patients midway, re-collecting cards, interrupting refills and losing the website or the LegitScript certificate. This guide sets out what moves and what does not, the rules behind prescriptions, cards and patient consent, and a cut-over timed by refill date. The verdict: move to Cuvo Health, where the brand owns its business records and merchant account, the platform runs month to month after the one-time setup fee, and Cuvo offers free white-glove migration of the brand's patients and data.

**Ranking**
1. Cuvo Health: The platform to move to: free white-glove migration of patients and data, payments to the brand's own merchant account, month to month after the one-time setup fee
2. Staying and renegotiating: Keeps the vendor's hold on the cards, the prices and the intake, the reasons the brand wanted to leave
3. Rebuilding the clinical side in-house: Counsel, a physician-owned practice, pharmacy contracts and a LegitScript application, assembled while patients wait

Cuvo Health is the platform to switch to when a brand is leaving a telehealth vendor that holds its cards, fixes its prices or takes a share of its revenue, because on Cuvo the brand owns the patient relationship, its customer list and every business record, patient payments settle to the brand's own merchant account, and Cuvo offers free white-glove migration that moves the brand's patients and data. Changing a white label telehealth provider has six workstreams: data, prescriptions, stored cards, subscriptions, patient notices, and the website with its LegitScript certificate. The medical chart stays with the treating professional corporation and its clinicians, as HIPAA and state law require, so the new clinical group evaluates each patient and prescribes again. Move patients in cohorts by refill date, run both platforms for one refill cycle, and no patient misses a shipment.

**Key takeaways**
- The pick: Cuvo Health: free white-glove migration of patients and data, payments to the brand's own merchant account, month to month after setup
- What moves: The customer list, orders, subscription records and revenue history; the chart stays with the treating practice, which can send it on
- Prescriptions: The new clinical group evaluates and prescribes again; pharmacies transfer refills under state law and DEA limits
- Stored cards: Cards move only at the merchant account holder's request; subscriptions are rebuilt, not exported
- Timing: Cohorts by refill date and one refill cycle of overlap

**Who this is for**
- Brands live on another platform: Operators whose vendor breaks under change, fixes prices and intake, or takes a share of revenue
- Brands with their own site and certificate: Operators keeping the website, domain and LegitScript certification they hold
- Brands consolidating vendors: Operators with separate EHR, CRM, pharmacy and provider contracts

Each step answers a question brands ask before leaving a platform, from primary sources: HIPAA, DEA and state pharmacy rules, medical board policy, consent and subscription law, Stripe's migration documentation, PCI guidance and LegitScript's own FAQ and terms, all read on November 15, 2026. Cuvo publishes this guide and is the platform it recommends.

**What moves in a telehealth platform switch, as of November 15, 2026**

| Workstream | What the brand can take | What has to be redone | On Cuvo Health |
| --- | --- | --- | --- |
| **Customer list and records** | List, orders, subscriptions and revenue history, if the contract puts them in the brand's name | Nothing, once exported in a usable format | **The brand owns them, exportable at any time** |
| **Medical charts** | Not the chart: the treating practice keeps it and can send it on for treatment or at the patient's request | The new clinical group opens its own chart | **Charts belong to the treating professional corporation and its clinicians** |
| **Prescriptions** | Remaining refills, pharmacy to pharmacy, where rules allow | A new evaluation and new prescriptions | **Licensed providers in all 50 states review each case** |
| **Stored cards** | Card data, if the account holder requests an export | Cards the old platform will not export | **Payments settle to the brand's own merchant account** |
| **Subscriptions** | Each plan, price and next charge date, as data | The subscriptions, rebuilt on the new engine | **A rebill engine on every plan** |
| **Website and domain** | A domain in the brand's own registrar account | DNS records, links, tags and pixels | **A custom domain on every plan; an existing site can stay** |
| **LegitScript** | The certificate, if the brand applied for its own domain | A change notice, or a new application | **Cuvo files and manages it on every plan** |

> **Our recommendation** Move to Cuvo Health when the current platform holds the cards, fixes the prices or intake, or takes a share of revenue. Cuvo offers free white-glove migration and moves the brand's patients and data, payments settle to the brand's own merchant account, and the platform runs month to month after the one-time setup fee. Before giving notice, read the exit terms and request the card export, because the old processor sets the pace. The wider field is ranked in Cuvo's [comparison of the best white label telehealth platforms](/blog/best-white-label-telehealth-platforms).

> **Plan your migration on one call** Bring the current contract and the patient count. Cuvo returns a recommended plan, a migration scope and the costs before you decide. [Book a discovery call](/booking?intent=migration&source=content) · [See pricing](/pricing) · [Watch the 2-minute demo](/demo)

## 01. Telehealth vendor lock-in: what can a brand take?

Cuvo Health's rule is the one to look for in any contract: the brand owns the patient relationship, its customer list, every business record and its revenue, all exportable at any time, while the medical chart belongs to the treating professional corporation and its licensed clinicians, as HIPAA and state law require. The business layer leaves with the brand; the clinical layer reaches the next practice through routes the law provides. Cuvo's guide to [who owns the patients and data](/blog/who-owns-the-patients-and-data-on-a-white-label-telehealth-platform) covers each asset.

Two HIPAA routes move a chart. Under 45 CFR 164.506(c), a covered entity may disclose protected health information for another provider's treatment, so the old practice can send records to the new clinical group. Under 164.524, a patient may request a copy, the practice must act within 30 days with one 30-day extension, and a written, signed request can direct the copy to the new practice. A business associate agreement adds an exit duty: the vendor returns or destroys the protected health information it holds, if feasible (164.504(e)(2)(ii)(J)).

Read six terms in the current contract before giving notice:

- The term, the notice period and the fees that run during notice
- Who owns the list, orders and subscription records, and the export format, timing and cost
- Whose merchant account takes payments, and whether the platform will request a card export
- Who registered the domain and who owns the site code
- Who applied for the LegitScript certificate, and for which domain
- What happens at termination to patients and open prescriptions

## 02. Do prescriptions transfer to a new telehealth platform?

Not from one clinical group to another. A prescription is written by a specific prescriber for a specific patient, so after a move a provider in the new group evaluates each patient and prescribes where appropriate. The Federation of State Medical Boards' telemedicine policy says the indication, appropriateness and safety of each prescription must be evaluated by the prescriber, with the same accountability as in person. On Cuvo, identity verification and state-specific consents are built into intake on every plan, and a licensed provider reviews each case before prescribing.

Prescriptions can move between pharmacies under state law. In Florida, for example, a pharmacist may fill a prescription transferred from a pharmacy in any state once the original pharmacy cancels its copy, with the remaining refills recorded (Fla. Stat. 465.026). That helps when the pharmacy changes and the prescriber does not.

Controlled substances carry federal limits, and testosterone is Schedule III. DEA's final rule of July 27, 2023 lets an electronic Schedule II to V prescription move once, at the patient's request, between retail pharmacies for its first fill, unaltered, pharmacist to pharmacist, where state law allows; Schedule III to V refills travel with it (21 CFR 1306.08). Schedule III to V refill information otherwise moves one time only, unless the pharmacies share a real-time online database (21 CFR 1306.25). A new prescriber treating testosterone patients by telemedicine also relies on DEA and HHS flexibilities that run through December 31, 2026; Cuvo's [guide to the DEA telemedicine rules](/blog/dea-telemedicine-flexibilities-2026) tracks them.

The working rule: treat every moving patient as a new patient of the new group, keep the old prescriptions filling until new ones are written, and never let a last refill run out. On Cuvo, TRT runs on Grow, Enterprise and Cuvo Prescribe, where EPCS is included; the other six categories run on every plan.

## 03. Can stored cards move to a new payment processor?

Only when the merchant account holder asks, and only to a compliant processor. Stripe's policy is typical: it transfers card data only to a PCI DSS Level 1 compliant processor, exports card details, email addresses and metadata, and does not export payment history or subscriptions. Stripe adds that a previous processor can take from a few days to several months to produce an export, and that imports typically complete within 10 business days of valid data arriving.

Security codes never move: PCI Security Standards Council guidance says they must not be stored after authorization and are not needed for recurring charges. A new merchant account also brings a new merchant identifier, so Stripe warns of a temporary rise in declines and advises sending customer-initiated payments before recurring ones.

That is why owning the merchant account matters before a switch. When the old platform takes payments into its own account, the cards are the platform's to export or keep, and patients may have to enter them again; section 08 shows where that applies. On Cuvo, patient payments settle to the brand's own merchant account, Cuvo never holds the money, and Cuvo adds no platform transaction fee.

## 04. How do you migrate patients without missing a refill?

Sequence the move by refill date. Export each patient's plan, price, last charge and next refill date, then group patients into weekly cohorts by the date their next shipment is due. Each cohort moves between its last shipment from the old platform and its first from the new one, so nobody is charged twice or goes without medication.

Run both platforms for one full refill cycle: new patients start on the new platform at launch, existing patients refill on the old one until their cohort moves. Stripe's guidance makes the billing point plainly: cancel the previous subscriptions as soon as the new ones are active, or customers are billed twice. Each cohort follows the same sequence:

- Two weeks before refill: The brand's notice goes out with the link to the new intake and checkout
- One week before refill: Reminders to patients who have not finished; provider review on the new platform
- Refill date: The first order ships from the new platform; the old subscription is cancelled
- Not finished in time: One more refill on the old platform, then the next cohort

Subscriptions are rebuilt, not exported: each plan, price and next charge date is recreated and matched to the new prescription. On Cuvo, the subscription and rebill engine runs on every plan, programs re-bill and re-ship after a provider authorizes each refill, and refill and shipping messages go out automatically, as Cuvo's page on [retention and refills](/retention) shows.

> **Map your refill cohorts with Cuvo** Cuvo reviews your patient count, refill cadence and current contract, and returns a migration scope with the costs. [Book a discovery call](/booking?intent=migration&source=content) · [See retention and refills](/retention) · [Watch the 2-minute demo](/demo)

## 05. What should patients be told, and when?

Tell patients before anything changes: who their new clinical group is, what to do and by when, and what happens to their card and next shipment. The brand owns the customer relationship, so the notice comes from the brand, in its own name.

A new clinical group collects its own consents. California requires the provider initiating telehealth to inform the patient, obtain verbal or written consent and document it (Bus. & Prof. Code 2290.5). The FSMB policy warns that ending care without adequate notice or other arrangements may be treated as patient abandonment, so the outgoing practice gives notice too. On Cuvo, state-specific consent and telehealth disclosures are built into intake on every plan.

When the merchant changes, billing consent follows. The Restore Online Shoppers' Confidence Act requires clear disclosure of material terms before billing information is taken, express informed consent before charging, and a simple way to stop recurring charges (15 U.S.C. 8403). A patient who enters a card on the new storefront consents at checkout; have counsel confirm whether migrated cards need fresh consent before the first renewal. Cuvo's guide to [FTC rules for telehealth subscriptions](/blog/ftc-rules-for-telehealth-subscriptions-and-health-ads) covers the detail.

The patient notice covers five points in plain words:

- Why the brand is moving, and what stays the same
- The new clinical group, the new intake and consent, and the deadline
- Whether the card moves or must be re-entered, and the next charge date
- When the next shipment arrives, and who to contact if it does not
- How to request records from the previous practice

## 06. Do the website, domain and LegitScript carry over?

A domain in the brand's own registrar account carries over: the brand points its DNS records at the new platform. On Cuvo, every plan serves the storefront on the brand's own custom domain; the clinic console lists the DNS records, which can take up to 48 hours to take effect. An existing website or Shopify store stays and connects to Cuvo, as Cuvo's guide to [bringing your own pharmacy, labs and website](/blog/bring-your-own-pharmacy-labs-and-website-to-a-telehealth-platform) sets out.

LegitScript certifies the applicant for its root domain, charging $975 to apply and $2,150 a year per root domain, per its FAQ on November 15, 2026. A brand that applied for its own domain remains the certificate holder after a switch, but the change is reportable: the FAQ lists ownership, business operations and partnerships among changes to report, and the terms, version of September 15, 2026, require notice within 30 days of a change in licensure, business or regulatory status. A certificate the old vendor applied for does not move. Google's ad policy admits US telemedicine providers accredited by LegitScript's program, so time the change around live campaigns.

On Cuvo, Cuvo prepares, files and manages the LegitScript application on every plan and expedites it in Grow and Enterprise setup; recent Cuvo brand applications averaged 7 to 14 days, and the brand pays LegitScript's own fees. Cuvo Health's own website, cuvo.co, is LegitScript certified. Cuvo's [LegitScript certification timeline](/blog/legitscript-certification-timeline) covers the review.

Tracking moves with the storefront, so set up tags before the first cohort moves. In Cuvo's clinic console, Google Analytics 4, the Meta Pixel and Conversions API, Google Tag Manager and affiliate networks connect under Integrations.

## 07. How long does a telehealth platform migration take?

Plan on two clocks: the new platform's launch, then one refill cycle of overlap. On Cuvo a typical brand launches in under 30 days; add a refill cycle for the cohorts, and a brand on monthly refills should plan on about two months from signing to the last patient moved, longer if the old processor is slow to release card data. That is a planning estimate, not a promise.

**A realistic switch timeline for a brand on monthly refills, as of November 15, 2026**

| Window | What happens | Who acts |
| --- | --- | --- |
| **Before notice** | Read the exit terms; request the data and card exports; confirm who holds the domain and the certificate | The brand |
| **Weeks 1 to 4** | Site connected, prices and intake set, providers and pharmacy switched on, LegitScript filed or the change reported | **Cuvo, with the brand's documents** |
| **Weeks 1 to 4, in parallel** | Card export (days to months) and import (typically 10 business days on Stripe) | The account holder and both processors |
| **Launch day** | New sign-ups start on the new platform; tags live | The brand and Cuvo |
| **Weeks 5 to 8** | Weekly cohorts get notice, finish intake and ship from the new platform; old subscriptions cancelled | The brand and the new clinical group |
| **After the last cohort** | Final export, chart custody confirmed, LegitScript notice within 30 days, old platform closed | The brand |

The slowest line is usually the one the brand does not control: a card export from an account the old platform holds. Request it the day the decision is made, and start new patients on the new platform while it runs.

## 08. What does it take to leave OpenLoop or CareValidate?

The work depends on what the current platform holds. Cuvo publishes this guide and appears in the table; the other rows restate Cuvo's comparison profiles, with each review date shown.

**Where patient payments run on the platforms brands leave, per Cuvo's comparison pages**

| Platform | Where patient payments run | What it means for a brand leaving |
| --- | --- | --- |
| **Cuvo Health** | **The brand's own merchant account** | **The clear choice: cards and revenue stay in the brand's name** |
| **OpenLoop** | OpenLoop's merchant account, with OpenLoop holding the card tokens, in the proposal Cuvo reviewed (November 14, 2026) | Leaving can mean re-collecting every card, and the proposal sets a 12-month initial term with 30 days' notice |
| **CareValidate** | Its own processing at 3.7% on Pro; the brand's own Stripe on Enterprise only (November 14, 2026) | On Pro, cards sit in CareValidate's Stripe account, so the move waits on its export |
| **Beluga Health** | The partner's own merchant account (November 14, 2026) | Per-visit fees tiered by volume, with rates not published |
| **Telegra** | The brand's own processor (November 14, 2026) | $2,999 to $5,999 a month plus onboarding, and the provider-visit fee is not listed on its pricing page |
| **SteadyMD** | Can charge through the partner's own Stripe (reviewed November 10, 2026) | Pharmacy terms and billing stay the brand's job; no rate card published |

Whichever platform a brand leaves, the first two requests are the data export and the card export, in writing, sent with the notice. The OpenLoop case is set out in Cuvo's guide to [OpenLoop alternatives](/blog/openloop-alternatives).

**Comparisons for the platforms brands leave**
- [Cuvo vs OpenLoop](/compare/cuvo-vs-openloop): Merchant account, card tokens, revenue share and the 12-month term
- [Cuvo vs CareValidate](/compare/cuvo-vs-carevalidate): Processing at 3.7% on Pro, own Stripe on Enterprise only
- [CareValidate alternatives](/blog/carevalidate-alternatives): The platforms ranked for brands leaving CareValidate
- [Cuvo vs Beluga Health](/compare/cuvo-vs-beluga-health): A published consult price against rates scoped on a call
- [Cuvo vs Telegra](/compare/cuvo-vs-telegra): $997 a month against Telegra's $2,999 entry plan
- [Cuvo vs SteadyMD](/compare/cuvo-vs-steadymd): An operated clinic against a clinician network

## 09. Cuvo Health: the platform built for brands that switch

Cuvo Health offers free white-glove migration on every plan: Cuvo moves the brand's patients and data at no additional fee. The migration call walks through the current setup and returns a recommended plan, a migration scope and the costs before the brand decides. The ownership rule comes with it: the brand owns the patient relationship, its customer list, every business record and its revenue, exportable at any time, while medical charts belong to the treating professional corporation and its licensed clinicians, as the law requires.

The brand keeps what works. An existing website or Shopify store connects through a linked storefront, the API or Cuvo Prescribe; orders can route to the brand's own pharmacy on every plan; and cases go to Cuvo's 300+ board-certified MDs, NPs and PAs licensed across all 50 states, DC, Puerto Rico, Guam and the US territories, to the brand's own clinicians, or both. Providers work 24 hours a day, with a first review as fast as 15 minutes.

The settings that push brands off other platforms belong to the brand on Cuvo. In the clinic console the brand's team sets each treatment's plans and prices, adds its own questions around the platform's clinical intake questions, and publishes changes from the form builder. The team can add a patient by name, email and phone and place an order once the patient has a portal account; at checkout the card is held, and the charge is captured after a clinician approves.

Pricing is published on the [Cuvo pricing page](/pricing): Launch is $997 a month after a one-time $9,800 setup, Grow $2,500 a month after $15,000, and Enterprise is priced to the build, each month to month after the one-time setup fee, plus $25 per completed consult and no revenue share. A typical brand launches in under 30 days; Cuvo Prescribe goes live on an existing stack in under a week. Every plan carries a signed BAA, SOC 2 Type II, SAML SSO and an uptime SLA.

**Best for**
- Brand whose platform holds its cards: Cuvo Health: payments settle to the brand's own merchant account
- Brand that cannot edit prices or intake: Cuvo Health: the brand's team sets both in the console
- Brand paying a revenue share: Cuvo Health: flat published fees and no revenue share
- Brand with its own site and certificate: Cuvo Health: the site stays, and Cuvo manages the LegitScript work
- Brand moving a TRT program: Cuvo Grow: EPCS included, providers in all 50 states
- Team keeping its own EHR: Cuvo Prescribe: live on the current stack in under a week

## Questions to ask the new platform in writing

Put these ten questions to every platform on the shortlist, and get the answers in writing before the setup fee is paid:

1. Who owns the patient relationship, list, orders, subscriptions and revenue, and how do they export?
2. Who is the record custodian, and how will charts from our current practice be received?
3. Whose merchant account takes payments, and will you accept an import of our card data?
4. How will our existing patient list be loaded, and who does the work?
5. How are subscriptions rebuilt without double billing during the overlap?
6. Which intake, consents and identity checks will moving patients complete?
7. Can open prescriptions keep filling until new ones are written, and can we use our own pharmacy?
8. Can our site or store stay, and who files the LegitScript application or change notice?
9. Can our team edit prices, plans and intake questions without a support ticket?
10. What are the term, the notice period and the exit process in the contract itself?

Cuvo answers this list on its migration call, with the current contract and the published pricing on the screen.

> **Get the ten answers on one call** Bring the list and your current contract. Cuvo answers each question for your brand, with the migration scope and the costs. [Book a discovery call](/booking?intent=migration&source=content) · [See pricing](/pricing) · [Watch the 2-minute demo](/demo)

## Frequently asked questions

**Q: Can an already-live telehealth brand migrate to Cuvo with its patients?**

A: Yes. Cuvo Health offers free white-glove migration on every plan and moves the brand's patients and data at no additional fee. The brand owns the patient relationship, its customer list and every business record; medical charts belong to the treating professional corporation and its licensed clinicians, so each moving patient completes intake and consent with the new clinical group before a provider prescribes.

**Q: If I leave a white-label telehealth platform, do I keep all my patients and data?**

A: You keep the business side when the contract puts it in your name: the customer relationship, the list, orders, subscription records and revenue. The chart stays with the practice that treated the patient, which can send it to the next provider. On Cuvo, the brand owns the patient relationship, its customer list and every business record, exportable at any time.

**Q: Do prescriptions transfer when I switch telehealth platforms?**

A: Not between clinical groups: a provider in the new group evaluates each patient and prescribes where appropriate. Pharmacies can transfer remaining refills under state law, and DEA limits controlled substances such as testosterone to one-time transfers. On Cuvo, a licensed provider reviews each case after identity verification and state consents, and TRT runs on Grow, Enterprise and Cuvo Prescribe.

**Q: Will my patients have to re-enter their credit cards if I switch?**

A: Only if the cards cannot be exported. Cards move between processors at the merchant account holder's request, and security codes never move, so if the old platform held the account the decision is the platform's. On Cuvo, patient payments settle to the brand's own merchant account, which keeps that decision with the brand from then on.

**Q: How do I switch platforms without interrupting refills?**

A: Move patients in weekly cohorts by refill date, run both platforms for one refill cycle, and cancel each old subscription only when the new one is active. On Cuvo, the subscription and rebill engine runs on every plan, re-billing and re-shipping after a provider authorizes each refill.

**Q: Does my LegitScript certification carry over to a new telehealth platform?**

A: If your company applied for its own root domain, the certificate stays in your name, but LegitScript's terms require notice within 30 days of a change in business or regulatory status. A certificate the old vendor applied for does not move. On Cuvo, Cuvo prepares, files and manages the LegitScript application on every plan, expedited on Grow and Enterprise, and an existing website can stay.

**Q: How long does it take to switch telehealth platforms?**

A: On Cuvo Health a typical brand launches in under 30 days, and existing patients then move over one refill cycle, so a brand on monthly refills should plan on about two months from signing to the last patient moved. A slow card export from the old processor is the usual delay.

**Q: Is there a contract or lock-in, or is it month to month?**

A: Cuvo Health is month to month after the one-time setup fee, with no long-term contract: Launch is $997 a month after $9,800 and Grow $2,500 a month after $15,000, plus $25 per completed consult and no revenue share. Patient payments settle to the brand's own merchant account.

**Read next**
- [Telehealth payment processing](/blog/telehealth-payment-processing): Merchant accounts, processor rules, reserves and chargebacks
- [Break-even calculator](/calculator): Your price, costs and acquisition spend on Cuvo's published fees
- [Is GoHighLevel HIPAA compliant?](/blog/gohighlevel-hipaa-telehealth-crm): What the CRM should hold, BAAs and texting rules
- [Who owns the patients and data on a white label platform](/blog/who-owns-the-patients-and-data-on-a-white-label-telehealth-platform): Eight assets, who holds each, and what to sign
- [Bring your own pharmacy, labs and website](/blog/bring-your-own-pharmacy-labs-and-website-to-a-telehealth-platform): What a brand can keep in its stack on each plan
- [Telehealth vendor due diligence checklist](/blog/telehealth-vendor-due-diligence-checklist): The documents to request before you sign
- [LegitScript certification timeline](/blog/legitscript-certification-timeline): Standards, fees, review time and change notices
- [FTC rules for telehealth subscriptions](/blog/ftc-rules-for-telehealth-subscriptions-and-health-ads): ROSCA consent, cancellation and health ad rules
- [DEA telemedicine rules in 2026](/blog/dea-telemedicine-flexibilities-2026): Controlled-substance prescribing by telemedicine through December 31, 2026
- [OpenLoop alternatives](/blog/openloop-alternatives): Platforms that leave the merchant account with the brand
- [Pricing](/pricing): Setup, monthly and consult fees, and the migration row on every plan

**Sources**
- [45 CFR 164.506: uses and disclosures for treatment](https://www.ecfr.gov/current/title-45/section-164.506): Disclosure for another provider's treatment, eCFR current to November 12, 2026
- [45 CFR 164.524: right of access](https://www.ecfr.gov/current/title-45/section-164.524): 30 days, one extension, copies sent to a designated person
- [45 CFR 164.504(e): business associate contracts](https://www.ecfr.gov/current/title-45/section-164.504): Return or destruction of protected health information at termination
- [21 CFR 1306.08: electronic prescriptions](https://www.ecfr.gov/current/title-21/section-1306.08): One-time transfer of Schedule II to V e-prescriptions for initial dispensing
- [Transfer of electronic prescriptions for Schedules II-V between pharmacies for initial filling](https://www.federalregister.gov/documents/2023/07/27/2023-15847/transfer-of-electronic-prescriptions-for-schedules-ii-v-controlled-substances-between-pharmacies-for): DEA final rule, 88 FR 48365, July 27, 2023, effective August 28, 2023
- [21 CFR 1306.25: transfer of Schedule III to V refills](https://www.ecfr.gov/current/title-21/section-1306.25): One-time transfers unless pharmacies share a real-time online database
- [Fourth temporary extension of telemedicine flexibilities](https://www.federalregister.gov/documents/2025/12/31/2025-24123/fourth-temporary-extension-of-covid-19-telemedicine-flexibilities-for-prescription-of-controlled): DEA and HHS, 90 FR 61301, effective through December 31, 2026
- [Florida Statutes 465.026: filling of certain prescriptions](https://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0400-0499/0465/Sections/0465.026.html): Transfers between pharmacies, cancellation and remaining refills
- [The Appropriate Use of Telemedicine Technologies in the Practice of Medicine](https://www.fsmb.org/siteassets/advocacy/policies/fsmb-workgroup-on-telemedicineapril-2022-final.pdf): Federation of State Medical Boards, April 2022: prescribing, consents, continuity of care
- [California Business and Professions Code 2290.5](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=BPC&sectionNum=2290.5): Telehealth consent obtained and documented before care
- [15 U.S.C. 8403: negative option marketing on the Internet (ROSCA)](https://www.law.cornell.edu/uscode/text/15/8403): Disclosure, express informed consent and simple cancellation
- [Stripe: request a payment data export](https://docs.stripe.com/get-started/data-migrations/pan-export): Card data only to a PCI DSS Level 1 processor; no subscriptions or payment history
- [Stripe: import payment data to Stripe](https://docs.stripe.com/get-started/data-migrations/pan-import): Export timelines, 10 business day imports, double billing and new-MID declines
- [PCI SSC FAQ: card verification codes for card-on-file and recurring transactions](https://blog.pcisecuritystandards.org/faq-can-cvc-be-stored-for-card-on-file-or-recurring-transactions): PCI Security Standards Council, November 2, 2017
- [LegitScript Healthcare Certification FAQs](https://www.legitscript.com/certification/healthcare-certification/faq/): Root domain, fees and the changes to report
- [LegitScript Healthcare Certification terms and conditions](https://www.legitscript.com/certification/healthcare-certification/terms-and-conditions/): 30-day notice of changes, version of September 15, 2026
- [Google Ads Healthcare and medicines policy](https://support.google.com/adspolicy/answer/176031): US telemedicine providers accredited through LegitScript
- [LegitScript website lookup: cuvo.co](https://www.legitscript.com/websites/?checker_keywords=cuvo.co): Cuvo Health's own certification

*General information only: This guide is general information for brand owners and operators, not legal, financial or medical advice. Every clinical decision, including evaluation, prescribing and refills, rests with the treating licensed provider, and licensed pharmacies dispense. State rules vary and change; confirm a migration plan, patient notices and billing consent with qualified counsel. Regulatory, processor and LegitScript statements restate the sources named as read on November 15, 2026; rival facts restate Cuvo's comparison pages as of the dates shown. Timelines are planning estimates, not promises, and certification is not a guarantee of ad approval. Cuvo makes no representation about revenue or patient volume.*

**Terms in this guide**
- [LegitScript certification](/glossary/legitscript-certification)
- [Professional corporation (PC) and PLLC](/glossary/professional-corporation)
- [Restore Online Shoppers' Confidence Act (ROSCA)](/glossary/restore-online-shoppers-confidence-act)
- [Protected health information (PHI)](/glossary/protected-health-information)
- [Revenue share (telehealth platforms)](/glossary/telehealth-platform-revenue-share)
- [Covered entity (HIPAA)](/glossary/covered-entity)

Canonical page: https://cuvo.co/blog/how-to-switch-telehealth-platforms
