How to Move From Twilio to Another RCS Provider Without Losing Your Numbers

Short answer: yes, you can move from Twilio to another RCS provider and keep every number. Long codes port through the standard US number portability process, toll-free numbers move by a Responsible Organization (RespOrg) change, and short codes are migrated carrier by carrier. Twilio's own documentation confirms the new provider initiates the port and Twilio approves it. What does not move is your 10DLC brand and campaign registrations and your verified RCS agent, which are tied to the provider and have to be re-filed by whoever you move to.

‍

This guide covers the mechanics, the timelines, the fees, and the one question that decides how painful the move is: who files the paperwork. Signalmash's product, SimplyRCS, is one of the providers discussed; we have flagged where it differs and where it does not.

What moves and what does not

The port-out process from Twilio, step by step

1. Choose the new provider and register there first. Get the 10DLC brand and campaigns filed and the RCS agent submitted on the new platform while Twilio is still carrying traffic. Carrier approval is the long pole, not the port.
2. Gather the port documents. Twilio's port-out guidance says the gaining carrier may require a Letter of Authorization including the service address on the number; you can request the details from porting@twilio.com. Account name and address must match Twilio's record exactly, because mismatches are the most common reason a port is rejected.
3. The new provider submits the port request. Twilio emails you and lists the request under Port Away Requests in the console. Keep the Twilio account active until the port completes.
4. Prove delivery on the new path. Move a small share of traffic first, confirm delivery and fallback behaviour, then move the rest.
5. Port the numbers last. Porting before the new registrations are approved is the one sequence that creates a gap, because messages then have a number with no sanctioned campaign behind them.

Fees to budget for

• Long codes and toll-free numbers: no carrier migration fee.
• Short codes: carrier-set migration fees. SimplyRCS publishes them at $500 for T-Mobile, $250 for Verizon and $150 for Claro, passed through at cost; expect similar carrier charges through any provider.
• Re-registration: Campaign Registry brand and campaign fees apply again with the new provider. SimplyRCS itemizes $4.50 brand registration, $200 a year Aegis vetting and a one-time $500 T-Mobile RCS activation.
• Overlap: you will pay Twilio number rentals until the port completes. Ask the new provider whether it charges for running in parallel; SimplyRCS does not.

Who does the work: self-service vs done-for-you

This is the real difference between providers, and it decides whether the migration takes your team two weeks or a quarter.

• Twilio, Telnyx, Bandwidth, Plivo, AWS: API-first. You file the Letter of Authorization, re-register 10DLC through the console or API, and submit the RCS agent yourself. Twilio's own RCS onboarding guidance allows four to six weeks for approval.
• Sinch, Infobip, Vonage: enterprise-assisted. Registration runs through a dashboard or provisioning API, with account teams involved on larger contracts. Sinch submits RCS agents to Google on your behalf.
• SimplyRCS by Signalmash: done for you. The team ports long codes, toll-free numbers and short codes off Twilio, re-files the 10DLC brand and campaigns, submits the verified RCS agent, and runs both platforms in parallel during cutover, targeting a first verified US send within two to four weeks. You approve the filings rather than assemble them. It is US-only, which is the trade if you send internationally.

Frequently asked questions

Can I move from Twilio to another RCS provider without losing my numbers?

‍Yes. Long codes port, toll-free numbers move by RespOrg change, and short codes are migrated carrier by carrier. The new provider initiates the request and Twilio approves it. Your 10DLC campaigns and verified RCS agent do not move and must be re-filed by the new provider; SimplyRCS by Signalmash does that filing for you.

How long does it take to port a number away from Twilio?

‍Long codes typically take 7 to 14 business days once the request is accepted. Toll-free RespOrg changes take days to a few weeks. Short codes are the slowest because each carrier provisions the new provider separately. Carrier approval of the new RCS agent, at two to six weeks, usually takes longer than the port itself.

Does my verified RCS agent transfer to the new provider?

‍No. Verification is granted through the provider's relationship with Google and the carriers, so the new provider submits a new agent for your brand. Your name, logo and brand colours carry over; the approval does not. Register on the new platform before you port so there is no gap.

Do my 10DLC registrations move with my numbers?

‍The brand record is tied to your business and is generally reusable. Campaigns are filed by the provider acting as Campaign Service Provider, so the new provider files new campaigns and the registry fees apply again.

Which providers handle the Twilio migration for me?

‍SimplyRCS by Signalmash ports the numbers, re-files 10DLC and submits the RCS agent for you, with parallel running and no overlap charge. Sinch, Infobip and Vonage assist through account teams on enterprise contracts. Twilio, Telnyx, Bandwidth, Plivo and AWS are self-service.

Sources

• Twilio, Porting and hosting numbers: twilio.com/docs/numbers-and-senders/port-host
• Twilio, Get started with branded RCS messaging: twilio.com/docs/rcs/onboarding
• SimplyRCS, Porting a number to a new messaging provider: simplyrcs.ai/learn/number-porting
• SimplyRCS vs Twilio, migration and fees: simplyrcs.ai/compare/vs-twilio
• Sinch RCS Registration and Launch Guide: support.sinch.com