Moving Phone Numbers across accounts (US and International)

Modified on: Fri, 19 Sep, 2025 at 10:20 AM

This guide explains how to move numbers from LC Phone to Twilio, from Twilio to LC, and from LC to LC when the agencies are different. It uses a simple two-step process handled through HighLevel Support (no Twilio ticket required).


IMPORTANT: Same process for all three cases:

Presently, LC→Twilio, Twilio→LC, and LC→LC (different agencies) follow the same process. Customers provide the appropriate Twilio Account SID—the gaining SID when moving into Twilio or the losing SID when moving out of Twilio—plus the destination sub-account ID and the phone number(s). For International numbers, provide the Regulatory Bundle SID and Address SID instead of the Account SID. HighLevel Support coordinates the migration end-to-end.



IMPORTANT: You no longer need to open a Twilio Support ticket. HighLevel Support coordinates migrations end-to-end.

TABLE OF CONTENTS


Before Moving Your Number


Ensure you have the following information and access:

US numbers: 


  • Twilio Account SID (gaining for LC→Twilio, losing for Twilio→LC)

  • Destination sub-account ID (where the number will live)

  • Phone number(s) in E.164 format (e.g., +1XXXXXXXXXX)


International numbers: 


  • Regulatory Bundle SID (instead of Account SID)

  • Address SID

  • Destination sub-account ID (if applicable)

  • Phone number(s) with country


Moving  US Phone Numbers


The three moves—LC→Twilio, Twilio→LC, and LC→LC (different agencies)—follow the same flow. First, collect the Twilio credentials that prove ownership/target for your specific case; then open a HighLevel Support ticket with your details and a cutover window. We’ll coordinate the migration end-to-end; you don’t need a Twilio ticket.



Before you start: 

US numbers: Have the relevant Twilio Account SID (gaining for LC→Twilio, losing for Twilio→LC), the destination sub-account ID, and the phone number(s).

International numbers: Have the Regulatory Bundle SID, Address SID, and the phone number(s) (include country).



Step 1: Gather Twilio credentials (when required)

These can be found in the Twilio Console under the Account Info section.


  • LC → Twilio: Gaining Twilio Account SID (destination Twilio).

  • Twilio → LC: Losing Twilio Account SID (current Twilio).

  • LC → LC (different agencies): You don't need Twilio credentials in this case. 



Step 2: Obtain the Location ID consisting the phone number (or where to transfer the phone number)

Navigate to Settings → Business Profile in your HighLevel account to locate the Sub-account ID (also known as Location ID) of the LC Phone Sub-account holding the phone number(s).




Step 3: Open a HighLevel Support ticket

This ticket kicks off the migration—include the numbers, the relevant gaining/losing Twilio Account SID, the destination sub-account ID, and your preferred cutover window. HighLevel Support schedules and coordinates everything, then confirms when the number is live (no Twilio ticket needed).


Moving International (Non-US) Numbers


International moves follow the same two-step flow as US moves, but instead of a Twilio Account SID, you’ll use Regulatory credentials. Collect the Regulatory Bundle SID and Address SID that apply to the number’s country and number type (local or toll-free), then follow the same process as mentioned above.


Pre-checks (recommended): Ensure the bundle is approved & current, documents are valid, and any country-specific sender ID/registration (e.g., Alphanumeric Sender ID, local onboarding, emergency address) is in place for the destination.


Note: We do have a Migration guide for reference. For more, visit Moving Phone Numbers: Migration Guide

Frequently Asked Questions


Q. How long will my migration take?
1–2 business days from the time HighLevel Support has all required IDs (gaining/losing Twilio Account SID, destination sub-account ID) and the number list. We’ll confirm the cutover window and notify you when the number is live.



Q. Can I move multiple numbers at once?
Yes. Include a single list (CSV or inline) in your ticket and validate each number after cutover.



Q. Do A2P/Toll-Free approvals transfer automatically?
Not always. After the move, confirm numbers are attached to the correct brand/campaign or Toll-Free verification.



Q. Do past recordings/voicemails migrate?
No. Future assets follow the number after cutover. Download any historical items you need to retain.



Q. What if I need to roll back?
Reply to the ticket immediately during the cutover window; feasibility depends on the carrier and timing.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article