Moving Phone Numbers in HighLevel: A Step-by-Step Migration Guide

Onboarding a new client often requires taking over an existing business phone number. For established companies, changing phone numbers is rarely viable because their existing lines are tied to years of marketing collateral, local brand equity, and active customer inbound traffic.

Managing phone migrations historically involved navigating complex carrier paperwork and manual telecom configurations. A misplaced parameter could take a business line offline for days. Within HighLevel, moving phone numbers between sub-accounts, transferring between LeadConnector and Twilio, or porting external landlines can be handled systematically with minimal operational downtime.

Gathering Required Credentials Before Transferring

Before initiating any phone number transfer, collect all technical identifiers associated with both the losing and gaining accounts. Missing information is the primary reason migration requests stall or get rejected by telecom routing networks.

For domestic transfers within the United States, assemble the following data points prior to submitting a request:

• The Twilio Account SID for both the source and target accounts (if applicable)
• The destination Location ID or sub-account identifier
• The full E.164 formatted phone numbers requiring transfer

International transfers require additional compliance verification due to regional telecommunication regulations. Ensure you have gathered:

• The active Regulatory Bundle SID assigned to the target account
• The validated Address SID corresponding to the physical business location
• The complete phone numbers including country and area codes

Relocating Numbers Between LeadConnector and Twilio

Switching telephone infrastructure between LeadConnector and custom Twilio accounts—or moving numbers between separate HighLevel agency instances—follows a standardized support workflow. Because these migrations involve updating upstream routing tables, they require coordinated technical execution.

Follow this operational sequence when transferring numbers across distinct system accounts:

1. Compile all required Account SIDs, sub-account Location IDs, and phone numbers into a single reference document.
2. Submit a migration request through HighLevel Support detailing the direction of the transfer (LeadConnector to Twilio, Twilio to LeadConnector, or agency-to-agency).
3. Specify a preferred cutover timeframe during off-peak business hours to minimize potential disruption to inbound calls.
4. Wait for technical support confirmation before testing inbound call routes and SMS automation in the destination sub-account.

Transferring Numbers Across Sub-Accounts in the Same Agency

When reassigning phone numbers between two sub-accounts managed under the same agency dashboard, you do not need to submit a support ticket. HighLevel includes a built-in migration utility within the account settings.

To perform an immediate internal transfer, complete these steps:

1. Navigate to the main agency dashboard or access the source sub-account settings.
2. Open the Phone Integration area and locate the internal number migration tool.
3. Select the specific phone number or list of numbers you intend to relocate.
4. Designate the target sub-account from the destination dropdown menu and confirm the reassignment.

In rare instances where an internal move fails due to backend configuration mismatches or legacy account setups, open a brief support ticket containing the source Location ID, target Location ID, and the exact phone numbers. Support can override the lock and push the assignment through manually.

Porting Third-Party Carrier Lines into HighLevel

Bringing numbers from external carriers such as AT&T, Verizon, Comcast, or traditional landline providers into LeadConnector requires a formal porting process. This transfer involves legal ownership handoffs governed by telecommunication regulatory bodies.

To ensure a smooth transition without losing control of active business lines, prepare the mandatory documentation before starting the request:

• A signed Letter of Authorization (LOA) executed by the authorized account owner listed on the current carrier account.
• A recent billing statement (issued within the last 30 days) displaying the account holder name, billing address, and phone numbers.
• An exact match of the physical service address as registered with the losing carrier.

Submit these documents alongside your support ticket, specifying the intended cutover window. The support team submits the regulatory paperwork directly to the losing and gaining carriers. Once the underlying carrier approves the port date, you will receive confirmation to conduct live call testing on the scheduled activation day.