Switching Texting Platforms Without Losing Opt-Outs
Every stop request sent through your old texting platform still binds your company after the switch, and the FCC gives you no more than 10 business days from receipt to honor it. The business the texts are sent for answers for opt-outs, even when a vendor stores them. A migration that drops part of the suppression list can send hundreds of messages to people who said STOP. A company that plans the move and keeps proof of how it did it has real defenses if a claim follows.
Who is liable when the old vendor held the opt-out list?
Your company is liable, and 47 C.F.R. § 64.1200(d)(3) says so in plain terms: “If such requests are recorded or maintained by a party other than the person or entity on whose behalf the call is made, the person or entity on whose behalf the call is made will be liable for any failures to honor the do-not-call request.”
The § 64.1200(d)(3) liability sentence sits in the telemarketing rules, which cover marketing texts. Informational texts sent with an autodialer rely on consent instead, and the FCC’s 2024 consent order puts the job of processing a revocation on “the text sender, who is responsible for processing the revocation request,” in the words of FCC 24-24. Either way, the vendor’s database isn’t a shield. It’s your list, held by someone else.
How long do you have to honor opt-outs during a migration?
The limit is 10 business days, and the switch doesn’t pause the count. The do-not-call rule says “This period may not exceed ten (10) business days from the receipt of such request,” per § 64.1200(d)(3). For texts that need consent, the revocation rule in § 64.1200(a)(10) adds that “All requests to revoke prior express consent or prior express written consent made in any reasonable manner must be honored within a reasonable time not to exceed ten business days from receipt of such request.”
Both deadlines have applied since April 11, 2025, the effective date the FCC announced for its 2024 consent rules, as the agency recounted in DA 26-12. The clock starts on receipt. The FCC said so in FCC 24-24 when it explained that “This timeframe begins upon receipt of the revocation request and not the sending of the confirmation text message.”
Section 64.1200(d)(3) counts from receipt, and receipt is where a migration breaks. Picture a customer who replies STOP to the old short code on a Friday, after the old platform has stopped syncing with your systems. Nobody on your team sees it. Your company “received” it all the same, and the new platform keeps texting. Ten business days later, every message to that number is a potential claim.
Do old opt-outs have to come across, and for how long?
Yes, and the export has to reach back 5 years, not just a few months. The do-not-call rule says “A do-not-call request must be honored for 5 years from the time the request is made,” under § 64.1200(d)(6). A vendor’s standard export that covers only the last year of activity, or only active subscribers, leaves out the people most likely to sue: those who said stop a long time ago and suddenly hear from you again.
The FCC also bars any company from designating “an exclusive means to request revocation of consent,” per § 64.1200(a)(10). Opt-outs don’t only arrive as STOP replies. They come through emails, call center notes, web forms, and plain-language replies asking to be taken off the list. A complete migration pulls every one of those sources, not just the platform’s keyword log.
Each imported record should carry 5 fields: the phone number, the date and time received, the channel, the exact words used, and the brand or program the customer was responding to. That last field is easy to skip. It shouldn’t be, because the FCC’s revoke-all rule may turn on it.
Teams that already keep the written policy § 64.1200(d)(1) requires, plus a single suppression file, have an easier move. The firm’s guide to what an internal do-not-call policy must include covers the written-policy and training requirements that sit beside the 10-day rule.
Does a STOP to one brand cover every brand after a consolidation?
For telemarketing, § 64.1200(d)(5) ties the answer to what the customer reasonably expected. A do-not-call request applies to the company that made the call and “will not apply to affiliated entities unless the consumer reasonably would expect them to be included given the identification of the caller and (for telemarketing calls) the product being advertised,” under § 64.1200(d)(5).
Under § 64.1200(d)(5), brand consolidations cut against the separate-affiliate argument. Once two brands text from the same number under one name, a customer who opted out of either one has a strong argument that the request covered the combined sender. The safer course is blunt: merge every brand’s suppression list into one before the first consolidated campaign goes out. Arguing later about what a consumer expected is expensive, and a jury may not see it your way.
Informational texts carry a separate question, the FCC’s “revoke-all” requirement. As adopted, § 64.1200(a)(10) would make an opt-out in response to one kind of informational robotext apply to all of a caller’s robocalls and robotexts on unrelated matters. The FCC has delayed that piece twice. In an order released January 6, 2026, the FCC’s Consumer and Governmental Affairs Bureau stated “we extend the effective date of any such requirement until January 31, 2027,” in DA 26-12. The firm’s post on the FCC’s January order extending the revoke-all waiver walks through what that delay does and doesn’t change.
The waiver in DA 26-12 covers only the revoke-all piece. The same order says it “does not alter the status quo relating to any other prior Commission rules or rulings addressing revocation of consent,” per DA 26-12. That’s why the brand-and-program field matters. If the FCC changes the revoke-all rule before 2027, a company that knows which program each opt-out came from can apply whatever scope rule ends up in force. A company that flattened its records into a bare list of numbers can’t.
What should the new vendor contract say about opt-out data?
Because § 64.1200(d)(3) puts the liability on your company, the contracts with both platforms decide whether the records exist when you need them. Most standard platform terms say little about opt-out data.
The first exit term to negotiate is an export duty: the outgoing vendor delivers every opt-out, consent record, and message log in a usable file within, say, 30 days of notice. The second is retention: the outgoing vendor keeps the full message and opt-out history for a fixed period after termination, and won’t delete it while a claim is pending. The third is reply forwarding, so the old number or short code keeps passing inbound replies to your company until the migration is finished. The fourth is litigation cooperation, meaning help authenticating logs and answering subpoenas.
The new platform’s contract should require it to record each opt-out “at the time the request is made,” the standard in § 64.1200(d)(3). It should also require the vendor to load your suppression file before the first send and block sends to suppressed numbers at the platform level. The firm’s guide to indemnity and audit terms in TCPA vendor contracts covers the risk-shifting side of those agreements.
Logs deleted by a former vendor create a separate problem in litigation. Once a claim is reasonably expected, a company that let a former vendor purge its message history can face a spoliation fight on top of the TCPA claim. The firm has written on what happens when text logs go missing in litigation.
What exposure does a dropped opt-out list create?
| Claim theory | Rule | Exposure per message | Defenses that answer it |
|---|---|---|---|
| Marketing texts after a do-not-call request | 47 C.F.R. § 64.1200(d)(3), (d)(6); 47 U.S.C. § 227(c)(5) | Up to $500, or up to $1,500 if willful or knowing | Only one message in 12 months, sent within the 10-business-day window, reasonable-practices defense |
| Autodialed or prerecorded texts after consent was revoked | 47 C.F.R. § 64.1200(a)(10); 47 U.S.C. § 227(b)(3) | $500, or up to $1,500 if willful or knowing | Request not made by a reasonable method, honored within 10 business days, no autodialer or prerecorded voice used |
| A state’s suit over a pattern of texts | 47 U.S.C. § 227(g) | $500 per violation, up to three times that if willful or knowing | No pattern or practice, same merits defenses as private claims |
The do-not-call claim requires “more than one telephone call within any 12-month period by or on behalf of the same entity,” under 47 U.S.C. § 227(c)(5). The same section gives a company an affirmative defense if it “has established and implemented, with due care, reasonable practices and procedures to effectively prevent telephone solicitations in violation of the regulations.” A documented migration plan, a reconciliation report, and a written sign-off are the kind of proof that defense needs.
Consent claims under § 227(b)(3) set damages at $500 for each violation, and a court may increase the award to as much as three times that amount for willful or knowing violations. Migration errors also scale fast. One bad import can touch thousands of numbers, and a state can sue over a “pattern or practice of telephone calls or other transmissions” under § 227(g). The firm’s guide to how state attorneys general bring TCPA suits explains that route.
Avoid the second confirmation text
A one-time confirmation after an opt-out is allowed only if it confirms the request, carries no marketing, and “is the only additional message sent to the called party after receipt of the revocation request,” under § 64.1200(a)(12). Some platforms send welcome messages or re-subscription prompts when contacts are imported. If the import treats your old opt-outs as fresh contacts, each of them may get a text the rule doesn’t allow. Turn off automated welcome flows for the import, and test with a small batch before loading the full list.
If a claim arrives after the switch
- Put a litigation hold on both platforms’ data: message logs, opt-out records, consent records, and the migration files themselves, and tell the old vendor in writing not to delete anything.
- Pull the opt-out history for the claimant’s number from every source, with the date, the channel, and the exact words, and show when each system suppressed it.
- Pull the National Do Not Call Registry scrub records and the version dates used for the campaigns that reached the number.
- Collect both vendor contracts, the migration plan, the reconciliation report, and the message templates the number received.
- Talk to a lawyer before responding to a demand letter, contacting the claimant, or offering anything to settle.
The firm’s TCPA litigation defense page covers how demand letters and class actions move through state and federal court.
Questions businesses ask about changing texting vendors
Can we keep texting during the migration?
Yes, if the new platform has the full suppression list loaded before the first send and the old number still forwards replies within the 10-business-day limit. Pausing marketing sends for a few days around cutover is the safer choice. A short pause costs less than a batch of texts to people who already said stop, and it gives your team time to reconcile the two systems’ opt-out counts.
Does our old vendor have to give us our opt-out data?
Only if the contract says so, because § 64.1200(d)(3) puts liability on your company without setting terms between you and the vendor. If the contract has no export and retention clause, you may be negotiating for your own records while the 10-business-day clock runs. Add those terms before you give notice.
Are opt-outs from texts we sent years ago still binding?
For telemarketing, a do-not-call request must be honored for 5 years from the time it was made. A customer who opted out in 2022 is still off limits for marketing texts in 2026. Revoked consent for autodialed texts has no stated end date in the rule, so a company should treat it as permanent until the customer gives new consent.
Should we tell customers we are switching platforms?
No, a text announcing the new number to someone who said stop is one more message after an opt-out. For active subscribers, a notice from the old number before cutover helps customers recognize the new sender so their replies reach the right system.
Sued after a platform change?
If your company is accused of texting customers who opted out before a vendor switch, the migration records and both platforms’ logs usually decide the case. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving texts sent after an opt-out request. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227. The FCC’s rules are at 47 C.F.R. § 64.1200. The FCC’s 2024 consent order is FCC 24-24, Report and Order, CG Docket No. 02-278 (released Feb. 16, 2024). The waiver extension is DA 26-12, Order, CG Docket No. 02-278 (Consumer and Governmental Affairs Bureau, released Jan. 6, 2026).
This post is general information about the Telephone Consumer Protection Act and related laws as of January 12, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.