Home/HighLevel/Features/Phone System/HighLevel phone number migration and porting guide

Conversations and Inbox

HighLevel phone number migration and porting guide

In short

The Phone Number Migration & Porting Guide explains how to transfer a single or bulk phone number between LC Phone, Twilio, subaccounts, or an external carrier. It outlines the required information, step by step actions, limits, and post move validation so businesses can keep service running during the change.

AreaPhone System · General
Used forDental practice, Real estate agency, Software startup
Setup steps25 steps in 5 tasks
Last updatedNovember 16, 2026

01Who this is for

  • Agency owners who need to shift numbers between agencies or subaccounts to keep client communication aligned.
  • Founders of SaaS startups that rely on LC Phone or Twilio for inbound support lines and need a clear path for provider changes.

02Moving phone numbers, explained

The migration and porting feature lets a business move a phone number from one HighLevel phone environment to another or bring a number in from an outside carrier. It distinguishes between a migration, where the number stays within supported platforms, and a port, which involves carrier ownership verification.

All actions are performed from within the HighLevel platform or, for cross account moves, through a request to HighLevel Support. The in app Move Numbers tool handles same agency transfers, while Labs enabled port in workflows manage eligible US carrier ports. External ports require documentation uploaded through the portal.

After a move completes, the number appears in the destination location, but routing, messaging, and automation settings must be reviewed and re configured manually.

03How businesses use moving phone numbers

  • Dental practice. The practice can move its clinic line from LC Phone to a Twilio account to integrate with a new patient management system. It gathers the Twilio Account SID and location ID, formats the number in E.164, then submits a migration request to HighLevel Support.
  • Real estate agency. When an agent switches agencies, the agency uses the Move Numbers tool to shift the agent’s LC Phone number between subaccounts within the same agency, selecting up to ten eligible numbers and confirming the destination before finalizing the move.
  • Software startup. The startup ports its toll free support line from an external carrier into HighLevel. It enables the port in feature in Labs, enters carrier and billing information under Phone System > Phone Numbers, uploads the required statement, and submits the request.

04The numbers and rules that matter

  • Move Numbers tool allows up to 10 phone numbers per move.
  • Crossaccount migration typically takes approximately 1 to 2 business days after HighLevel Support receives all required information.
  • External carrier port for fewer than 50 numbers takes approximately 2 to 4 weeks.
  • Larger or more complex ports take approximately 6 to 8 weeks.
  • Manual US ports require a signed LOA, a billing statement no older than 90 days, phone number list in E.164 format, destination Location ID, carrier account number and wireless PIN when applicable.

05Before you start

  • Gather the required identifiers, documentation, and E.164 formatted numbers for the chosen transfer type before starting the move.
  • Do not delete, release, disable, disconnect, or cancel the number before the migration or port is confirmed complete.

06How to set up and use moving phone numbers in HighLevel

LC Phone > Twilio migration

  1. Collect the gaining Twilio Account SID.
  2. Collect the HighLevel Location ID that currently holds the number.
  3. Prepare all phone numbers in E.164 format.
  4. If any numbers are international, prepare the required regulatory information for the country and number type.
  5. Submit the complete migration request to HighLevel Support.

Twilio > LC Phone migration

  1. Collect the losing Twilio Account SID.
  2. Collect the destination HighLevel Location ID.
  3. Prepare all phone numbers in E.164 format.
  4. Prepare any applicable international regulatory information when required.
  5. Submit the migration request to HighLevel Support.

LC Phone > LC Phone across different agencies migration

  1. Collect the destination Location ID.
  2. Collect the source Location ID when it is available.
  3. Prepare the list of phone numbers to move.
  4. Prepare applicable international regulatory information when required.
  5. Submit the migration request to HighLevel Support.

Move numbers between subaccounts in the same agency

  1. Open Agency Settings > Phone Integration > Subaccount Settings.
  2. Click Move Numbers.
  3. Select the source subaccount and the destination subaccount.
  4. Select up to ten eligible phone numbers for the move.
  5. Review the destination details and complete the move.

Port a number from an external carrier or VoIP provider

  1. Enable the port in feature through Labs.
  2. Navigate to Phone System > Phone Numbers.
  3. Click Add Number and choose Port in Numbers.
  4. Enter carrier, number, authorized contact, service address details and upload the billing statement.
  5. Submit the request and save the Request SID.

07Settings that matter

  • Labs feature toggle. Controls whether the in app US port in workflow is available for eligible numbers.

08Things to know before you rely on it

  • Same agency Move Numbers supports a maximum of ten eligible US or Canada numbers per move.
  • Cross account migrations are coordinated by HighLevel Support and can include multiple eligible numbers in one request.
  • External carrier ports for fewer than 50 numbers typically take two to four weeks; larger ports may require six to eight weeks.

09If something goes wrong

  • Move Numbers is unavailable. Confirm that both subaccounts belong to the same agency, that the phone environments are compatible, and that the numbers are eligible US or Canada numbers.
  • A port request is rejected. Verify the service address, account number, wireless PIN, LOA signature, carrier account status, and billing documentation with the losing carrier before resubmitting.
  • An international number cannot move. Check the destination’s regulatory requirements, address information, and any required Regulatory Bundle before proceeding.
  • The number moved but SMS is not working. Review A2P 10DLC registration, Toll Free verification, SMS permissions, and country specific messaging requirements in the destination.
  • The number moved but calls route incorrectly. Inspect call forwarding, assigned users, voicemail, inbound routing, IVR, and workflow references for the moved number.

10How it connects to the rest of HighLevel

Michael's take

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

Wondering if you really need a full migration plan or just a quick port? The difference matters because migrations use HighLevel’s own tools or Support coordination, while ports involve the carrier’s paperwork and longer timelines. If the number is already on LC Phone or Twilio, stick with the migration path to keep things fast. For numbers sitting with an outside carrier, be ready to gather LOAs, recent bills and possibly a wireless PIN before you even start.

I’d start by mapping every number you own, noting whether it lives on LC Phone, Twilio or an external provider. That inventory tells you which table to follow and prevents surprise delays. Test the numbers as soon as they appear in the new location, and only then release the old carrier.

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

Common questions

Common questions about moving phone numbers.

How do I know if I need a migration or a port for my VoIP numbers?

If the numbers already use LC Phone or a supported Twilio environment, they follow a migration path. Numbers that belong to another carrier or VoIP provider require the porting process.

Can I move all of my VoIP numbers at once?

Same agency moves support up to ten eligible numbers per batch. Cross account migrations and eligible US port in requests can include multiple numbers in a single Support or portal request.

How long does a cross account migration usually take?

A supported cross account migration typically completes in approximately one to two business days after HighLevel Support receives all required information.

How long does an external carrier port take?

Ports for fewer than 50 numbers usually finish in two to four weeks; larger or more complex ports may require six to eight weeks.

Should I cancel my old provider after submitting a port request?

No. Keep the numbers and the source carrier account active until the port is confirmed complete and you have validated calls and messaging in the new destination.

Do contacts, recordings, and voicemails move with the phone number?

Moving or porting a number does not automatically transfer contacts, conversation history, recordings, or voicemail assets. Export any needed data before the source account is closed.

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.