Home/HighLevel/Features/Phone System/HighLevel manual migration of Twilio international numbers

Conversations and Inbox

HighLevel manual migration of Twilio international numbers

In short

The manual migration feature lets you transfer international phone numbers from Twilio into HighLevel’s LC Phone system when the automated migration stalls. It requires creating a compliant regulatory bundle in Twilio, obtaining specific IDs from HighLevel support, and submitting a Twilio support ticket to finish the transfer.

AreaPhone System · Phone Numbers
Used forMarketing agency, International ecommerce store, Non profit organization with a global helpline
Setup steps7 steps in 1 task
Last updatedNovember 16, 2026

01Who this is for

  • Agency owners who manage client phone numbers and need to move them into LC Phone.
  • Support teams handling international helplines that require number migration.

02International number migrations, explained

The manual migration process moves an international Twilio number into the LC Phone system inside HighLevel. It begins by starting the migration in the Phone Integration settings, which shows a “Migration in Progress” status. If that status does not clear, the user follows additional compliance steps.

Compliance involves creating a regulatory bundle and address in the Twilio Console that matches the number’s country and type. After the bundle is approved, the user requests the Gaining Account SID, Regulatory Bundle SID, and Regulatory Address SID from HighLevel support. Finally, a Twilio support ticket is opened to transfer the number, copying migration@leadconnectorhq.com and attaching the required IDs and LOA.

All actions occur within the HighLevel platform (Phone Integration settings) and the Twilio Console. The process is temporary until an upgraded migration feature is released.

03How businesses use international number migrations

  • Marketing agency. The agency creates the required regulatory bundle in Twilio for each client’s international number, requests the needed IDs from HighLevel support, and submits a Twilio support ticket to move the numbers into LC Phone. This ensures the agency can manage client numbers within the platform.
  • International ecommerce store. The store builds a compliant bundle for its overseas support line, obtains the bundle and address SIDs from HighLevel, and files a Twilio ticket to transfer the number. After migration, the store can send SMS and handle calls directly from HighLevel.
  • Non profit organization with a global helpline. The organization follows the manual steps to create a regulatory bundle matching its toll free number, secures the required IDs from HighLevel, and initiates a Twilio ticket to bring the helpline number into LC Phone, allowing unified communication handling.

04How to set up and use international number migrations in HighLevel

Manual migration process

  1. Start the migration from the Phone Integration settings in the HighLevel account.
  2. If the status remains “Migration in Progress”, continue with the manual steps.
  3. Open the Twilio Console and create a Regulatory Bundle for the number’s country or region.
  4. Add a Regulatory Address linked to the newly created bundle.
  5. Confirm the bundle is approved for the correct number type such as Mobile, Local, or Toll Free.
  6. Contact HighLevel Support or your partner to obtain the Gaining Account SID, Regulatory Bundle SID, and Regulatory Address SID.
  7. In the Twilio Console, open a support ticket requesting the number transfer, CC migration@leadconnectorhq.com, and include the LOA, Bundle SID, and Address SID.

05What it looks like in HighLevel

06Settings that matter

  • Phone Integration settings. Controls the initiation of the LC Phone migration and displays the migration status within HighLevel.

07Things to know before you rely on it

  • The manual process is temporary and will be replaced by an upgraded migration feature.
  • A migration can remain stuck if regulatory requirements are incomplete.
  • The regulatory bundle must be fully approved before the manual transfer begins.
  • The bundle’s number type must match the type of the phone number being moved.

08If something goes wrong

  • Migration in Progress stuck. Verify that the regulatory bundle is approved and matches the correct number type.
  • Missing Regulatory Approval. Complete the bundle approval process in Twilio before starting the manual migration.
  • Wrong Number Type on Bundle. Create or adjust the bundle so its type (Local, Mobile, Toll Free) matches the phone number.

09How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

If the numbers aren’t critical, I sometimes leave them in Twilio until the automated migration improves.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about international number migrations.

Why does my migration stay on 'Migration in Progress'?

The status can remain stuck when required regulatory steps, such as bundle approval or matching the number type, have not been completed.

Do I need a regulatory bundle for every international number?

Yes. Each international number must have a regulatory bundle created in Twilio that matches its country or region and number type.

What IDs do I have to request from HighLevel support?

You need the Gaining Account SID, the Regulatory Bundle SID, and the Regulatory Address SID.

How do I start the manual transfer in Twilio?

Log into the Twilio Console, open a support ticket requesting the number move, CC migration@leadconnectorhq.com, and attach the LOA along with the Bundle SID and Address SID.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.