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

The question people are really asking is whether they will be punished for leaving. They will not. Twilio is a pay-as-you-go platform, and the porting rules that apply to it are the same rules that apply to every US messaging provider. The move is mostly administrative, and the parts that take time are the carriers, not Twilio.

What "losing your numbers" would actually mean

A phone number is not a Twilio asset. Long codes and toll-free numbers are assigned to your business under US number portability rules, and short codes are leased to your business from the registry. Twilio is the carrier of record, or the Responsible Organization, while the number sits on its platform. Moving providers changes that record. It does not cancel the number, and recipients keep texting the same digits throughout.

The one way to genuinely lose a number is to release it before the port completes. A number that has been released back to the pool is no longer yours to port, so the rule is simple: keep the Twilio account and the number active until the gaining provider confirms the port, then close what you no longer need.

Long codes: port them out of Twilio

A 10-digit long code moves the way any US number does. You sign a Letter of Authorization, the gaining provider submits the port request, and the request is validated against the customer service record Twilio holds for your account. On the Twilio side the gaining carrier initiates the port; you do not file anything with Twilio itself.

Almost every rejected port is a details mismatch. The account name and service address on the request have to match Twilio's record exactly, not approximately. A trading name where Twilio holds the legal entity, or a suite number that changed since you signed up, is enough to bounce the request and restart the clock. Pull the exact details from your Twilio account before the Letter of Authorization is drafted. Porting a number to a new messaging provider covers the mechanics for each number type in full.

Toll-free numbers: change the RespOrg

A toll-free number is not ported in the technical sense. Toll-free numbers live in a shared registry, and each is assigned to a Responsible Organization, the RespOrg. Leaving Twilio means changing the RespOrg on the record to the new provider. The outcome is the same, you keep the number, but it is a different process on a different timeline, and toll-free verification for messaging is re-submitted by the new provider once the record changes.

Short codes: migrate carrier by carrier

A short code is leased to your business, so it comes with you, but it moves slowest of the three. The new provider has to be provisioned on the code with each carrier individually, and the carriers set migration fees that are passed through at cost: $500 for T-Mobile, $250 for Verizon and $150 for Claro. Long codes and toll-free numbers carry no migration fee. What is a short code and do I still need one is worth reading before you plan the move, because many brands find the code was only ever there for volume that RCS on a 10DLC number now handles.

What does not move off Twilio

This is the part migration plans underestimate, and it is the same on every platform, not a Twilio quirk.

• 10DLC campaigns. Campaigns are filed in The Campaign Registry by the provider acting as Campaign Service Provider, so Twilio's filings stay with Twilio and the new provider files new ones. Your brand record is tied to your business rather than to Twilio and is generally reusable. How does 10DLC registration work covers what the filing involves.
• The verified RCS agent. RCS verification is granted through a provider's relationship with Google and the carriers, so a new provider submits a new agent for your brand. Your name, logo and colours carry over; the approval does not, and the new agent has to be approved before branded RCS sends from the new platform. What is a verified sender explains what that approval covers.
• Opt-in records. Consent belongs to you and must be carried across, not re-collected. Export the records with their timestamps and source before you move, because losing the audit trail is a compliance problem even though nothing technical breaks. How does RCS consent work sets out what the record needs to show.
• Your integration. Code written against Twilio's API and webhooks is Twilio-specific. On the new provider you either rebuild against its API or, if the channel is run by a marketing or operations team, move to a platform with a no-code builder and inbox so there is nothing to rebuild.

The order that avoids a gap in service

The safe pattern is to overlap rather than cut over cold.

1. Register and verify on the new provider first, while Twilio is still carrying your traffic. Brand registration, the new 10DLC campaigns and the new RCS agent submission all run in this window.
2. Import contacts and opt-in records with their consent history intact.
3. Prove delivery on a small share of volume from the new platform, with SMS fallback active, and compare delivered, read and tap rates against the same send on Twilio.
4. Move the remaining traffic, then port the numbers last. Because the port is the final step, a rejected port for a details mismatch delays nothing.
5. Close the Twilio numbers you no longer need only after the gaining provider confirms each port.

Running both platforms for a few weeks costs you Twilio's number rental and whatever you still send there, and nothing more, because Twilio bills pay as you go. A migration only becomes risky when the numbers port before the new registrations are approved, because that is the window where a message has a number but no sanctioned campaign behind it.

The migration checklist, with who does what and how long it takes

The whole sequence is 2 to 4 weeks on SimplyRCS, and the port itself is the shortest step in it.

What the porting request has to contain

The gaining provider files the port; what it needs from you is a signed Letter of Authorization and the details Twilio holds on file. A request that is complete the first time is the difference between days and a restarted clock.

• Legal business name exactly as it appears on your Twilio account, not the trading name.
• Service address exactly as Twilio holds it, including suite number and ZIP code.
• The numbers, one per line, each marked long code, toll-free or short code, with the Twilio account or sub-account each one sits in.
• Losing provider named as Twilio, plus the account SID for the account that owns the numbers.
• Authorised signer: name, title, signature and date. The signer has to be someone Twilio would recognise as authorised on the account.
• Requested port date, set after the new registrations and the RCS agent are approved, never before.
• For toll-free numbers, the same details on the RespOrg change form, and the new provider's RespOrg ID.
• For short codes, the lease details from the registry and the carriers to be provisioned, because each carrier is a separate migration.

Pull every field from the Twilio console rather than from memory. The port is validated against Twilio's customer service record, and the request is rejected on any mismatch, however small.

Two templates for the internal handoff

Recipients never need to hear about the move, because the number and the verified brand name they see do not change. The communications that matter are internal. Two that save a round of questions:

To legal, with the Letter of Authorization attached: "We are moving our business messaging from Twilio to [new provider]. Our phone numbers are assigned to us and move with us; the attached Letter of Authorization authorises [new provider] to port them. Please check that the legal entity name and service address on the LOA match our Twilio account exactly, confirm the signer is authorised on that account, and confirm whether our Twilio agreement carries a notice period or minimum commitment we have to serve before [date]. Nothing changes for customers: they keep texting the same numbers."

To ops and finance, once the port date is set: "Port date for our messaging numbers is [date]. Until [new provider] confirms each number, keep the Twilio account, all listed numbers and their 10DLC campaigns active; do not release or cancel anything. Twilio bills pay as you go, so the overlap costs the number rental plus whatever we still send there. After confirmation, close the Twilio numbers on the attached list and leave the rest of the account until the final invoice clears."

Common gotchas

• Contracts. Most Twilio accounts pay as you go and can leave any time, but an enterprise or committed-spend agreement carries a term, a notice period and sometimes a minimum you owe whether or not you send. Read it before you set the port date; the port itself does not end the contract.
• Carrier rejections. A port bounces for a details mismatch, a number that sits in a different sub-account from the one on the LOA, an open order already pending on the number, or a number that was released before the request arrived. Each rejection restarts the clock, so fix the record first and file once.
• Short codes versus toll-free. A toll-free number moves by a RespOrg change with no carrier fee and its messaging verification is re-submitted by the new provider. A short code moves carrier by carrier, with the migration fees above, and takes weeks rather than days. Many brands find the code was only there for volume that RCS on a registered 10DLC number now carries, and let it lapse instead.
• Releasing early. A number released back to the pool is no longer yours to port. Nothing on the Twilio side is cancelled until the gaining provider has confirmed the number is live.
• Consent without the trail. Contacts moved as a plain list, without opt-in timestamps and source, leave you unable to answer a complaint. Export the records, not just the numbers.
• Webhooks pointing at the old platform. Delivery and reply webhooks written against Twilio's API stop firing when traffic moves. Re-point them, or move the workflow to a platform with a built-in inbox so there is nothing to re-point.

How long it takes

The number port itself is measured in days. The long pole is carrier approval of the re-filed 10DLC campaigns and the new verified RCS agent, which is why the whole move takes about as long as a new verified send would: 2 to 4 weeks on SimplyRCS, and 4 to 6 weeks by Twilio's own onboarding guidance if you were setting up there. A short-code migration adds time because each carrier provisions the code separately.

Where SimplyRCS sits

SimplyRCS ports long codes, toll-free numbers and short codes off Twilio, re-files your 10DLC brand and campaigns, and submits your verified RCS agent with the carriers, with your approval at each step rather than your effort. A migrating RCS sender has the same one-time $250 sender setup as a new one. Both platforms can run in parallel during cutover and there is no overlap charge from us. The traffic lands on Signalmash's direct connections to AT&T, Verizon and T-Mobile rather than on a reseller of someone else's, the platform holds a SOC 2 Type II report, and every carrier and registry fee you will pay is listed on billing transparency before you sign. The rates you move to are published: $0.0039 per RCS text segment and $0.0150 for a card or a message with media, with no monthly platform or agent fee, a one-time $250 RCS Sender ID setup and review, and carrier fees passed through at cost. SimplyRCS vs Twilio has the line-by-line comparison, and SimplyRCS vs Twilio vs Sinch on pricing and migration adds the third provider most Twilio customers shortlist.