Do I need to cancel my Twilio account before porting my numbers?

No, and you should not. Keep the account and every number active until the gaining provider confirms each port has completed. A number released back to the pool before the port finishes is no longer yours to move. Close what you no longer need afterwards.

Do my 10DLC campaigns move from Twilio to the new provider?

Campaigns do not. They are filed in The Campaign Registry by the provider acting as Campaign Service Provider, so the new provider files new campaigns for the same use cases. Your brand record is tied to your business rather than to Twilio and is generally reusable, so you are re-filing the campaign layer, not starting from nothing.

Does my verified RCS sender move from Twilio?

No. RCS verification is granted through a provider’s relationship with Google and the carriers, so the new provider submits a new agent for your brand. Your name, logo and colours carry over; the approval is issued again. Branded RCS from the new platform starts once that new agent is approved, which is why it is submitted before the numbers port.

Can I keep sending from Twilio while the move is in progress?

Yes, and it is the safer sequence. Register and verify on the new provider while Twilio still carries your traffic, prove delivery on a small share of volume, move the rest, then port the numbers last. Twilio bills pay as you go, so the overlap costs number rental and whatever you still send there. SimplyRCS does not charge for the overlap.

How long does it take to move numbers off Twilio?

The port itself takes days. The whole move takes 2 to 4 weeks on SimplyRCS, because carrier approval of the re-filed 10DLC campaigns and the new verified RCS agent is the long pole rather than the port. Short-code migrations take longer because each carrier provisions the code separately.

What happens to my Twilio API integration when I switch?

It stays behind. Code written against Twilio’s API and webhooks is Twilio-specific, so you either rebuild against the new provider’s API or move the channel to a platform with a no-code builder and inbox so there is nothing to rebuild. SimplyRCS offers both: a public REST API with signed webhooks, and an app a marketing or operations team can run without engineering.

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

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

Yes. Phone numbers are assigned to your business, not to Twilio, so every number type moves with you: long codes port out through standard US number portability, toll-free numbers move by a change of Responsible Organization, and short codes are migrated carrier by carrier. What does not leave Twilio with the number is the paperwork behind it. Your 10DLC campaigns and your verified RCS agent are tied to the provider that filed them, so the new provider files them again, and your opt-in records travel as data you export. Do it in the right order, verify on the new provider first and port last, and your customers never see a change.

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.

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.
Import contacts and opt-in records with their consent history intact.
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.
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.
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.

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. Both platforms can run in parallel during cutover and there is no overlap charge from us. The rates you move to are published: $0.0039 for an RCS text or an interactive card and $0.0150 for a message with media, plus $250 a month per verified RCS agent, with 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.

Key facts

Numbers are assigned to your business, not to Twilio; long codes port, toll-free numbers change RespOrg, short codes migrate carrier by carrier.
Short-code migration fees are carrier-set and passed through at cost: $500 T-Mobile, $250 Verizon, $150 Claro. Long codes and toll-free numbers carry none.
10DLC campaigns and the verified RCS agent do not transfer; the new provider re-files both. The brand record is generally reusable.
Opt-in records move as data you export; they are never re-collected.
Keep the Twilio number active until the port is confirmed; a released number cannot be ported.
Verify first, port last. Plan on 2 to 4 weeks, driven by carrier approval rather than the port.