Already have a business number that customers know? You may not need to abandon it when moving to HighLevel. Number porting lets eligible numbers move from your current carrier into HighLevel's phone system so you can manage calling and messaging from the same platform.
Number porting is the process of transferring an existing phone number from your current telecommunications provider to a new provider.
In this case, the destination is HighLevel's native LC Phone system.
The important part is that you are moving the number itself. You are not simply buying a new HighLevel number that looks similar to your old one.
That matters for businesses that have spent years putting the same number on websites, Google Business Profiles, business cards, ads, email signatures, invoices, social profiles and customer records.
Move an eligible existing business number instead of starting over with a completely new number.
Transfer the number from your current carrier into the HighLevel phone environment.
After the port, the number can be configured for supported calling, messaging, routing and automation.
The basic idea is simple, but the actual transfer is a carrier process. HighLevel needs enough information to prove that you are authorized to move the number and that the information in the request matches the records held by your current provider.
Once the request is submitted, the carrier reviews it. For the current US in-app workflow, HighLevel provides a Port-In Numbers dashboard where eligible requests can be tracked.
This is why preparing the right information before you start matters. A mismatch in the service address, account details, authorized name, PIN or other information can lead to rejection or delays.
In many cases, yes. But eligibility depends on the number, country, current carrier, number type and the porting route available for your situation.
| Your Situation | Typical HighLevel Path | What to Know |
|---|---|---|
| US number from another carrier | US in-app port-in | Eligible Agency Owners/Admins can submit through HighLevel when the feature is available. |
| US number requiring manual handling | Manual port request | May require signed LOA, billing statement and carrier details. |
| International number | Support-assisted international process | Requirements vary by country, provider and number type. |
| Twilio → LC Phone | Number migration | This is a migration rather than the standard external-carrier port-in workflow. |
| LC Phone → LC Phone, same agency | Move Numbers | Eligible US and Canada numbers can use the in-app move tool. |
| Keep voice with current carrier | Number Hosting | Hosting is different from porting because voice stays with the existing provider. |
The distinction between these paths is important. Do not submit a port request simply because you want to use an existing number with HighLevel.
Number hosting is an easy concept to confuse with porting.
With porting, the number moves to the new carrier. With number hosting, your existing carrier keeps the voice service while HighLevel can handle eligible SMS and MMS messaging through LC Phone.
| Feature | Porting | Number Hosting |
|---|---|---|
| Number moves to HighLevel | Yes | No |
| Existing carrier keeps voice | No | Yes |
| HighLevel SMS/MMS | Yes, after applicable setup | Yes, for eligible hosted numbers |
| Carrier transfer | Yes | No |
| Best when | You want HighLevel to manage the number | You want to keep your existing voice provider |
If your main goal is simply to add HighLevel messaging while keeping your existing voice service, read our GoHighLevel Phone System guide and investigate Number Hosting before deciding to port.
HighLevel can bring eligible numbers into its native phone environment. Before starting, make sure your carrier records and business information are accurate.
Explore HighLevelHighLevel's current US port-in workflow is designed to let eligible agencies submit and track number transfers from inside HighLevel.
The current support documentation says the feature is available to Agency Owners and Agency Admins through Labs.
Once enabled and available for your account, the Port-In Numbers workflow collects the information needed for the request and can generate the Letter of Authorization as part of the in-app process.
The exact information requested depends on your number and porting path, but the most important rule is simple: your submitted information needs to match the records held by your current carrier.
If you are using the newer in-app US workflow, HighLevel handles more of the form creation inside the platform. If your number needs a manual process, expect additional documentation.
A Letter of Authorization, commonly called an LOA, is the document that authorizes the transfer of your phone number.
For manual port requests, HighLevel requires the LOA to be signed by the authorized person and the information needs to match the service details held by the current carrier.
The current in-app US port-in workflow can automatically generate the LOA, which reduces some of the manual work involved in older porting processes.
Telecom carriers need to know that the person requesting the transfer is authorized to move the number. The LOA is part of that authorization process.
Do not guess the information on your LOA. Use the exact customer and service details your current carrier has on file.
Manual US port requests can require several documents and identifiers.
A signed Letter of Authorization confirming the request to transfer the number.
A recent carrier billing statement showing the relevant number and account ownership.
Carrier account information and PIN or passcode for wireless numbers where required.
HighLevel's manual porting documentation says the latest billing statement should generally be no older than 90 days and should clearly show the phone number, account owner and provider.
For wireless numbers, the carrier account number and correct PIN are particularly important. A wrong PIN can cause the port request to be rejected.
The current process can be handled through HighLevel's in-app port-in workflow when your account and number are eligible.
Porting is not usually an instant change.
HighLevel's current documentation says port requests involving fewer than 50 numbers can take approximately two to four weeks from submission of the required documentation. Larger and more complex ports can take approximately six to eight weeks.
If the phone number is printed on your website, ads, signage or customer materials, do not schedule a critical campaign launch around the assumption that the port will complete on a particular day.
The actual timeline depends on carrier review, documentation, number eligibility and whether anything needs to be corrected.
HighLevel's general porting documentation says there is no downtime associated with the standard porting process before the transfer is completed, allowing you to continue using the number during the process.
However, the actual cutover is still an important event. Your old carrier should remain active until the port is confirmed complete and you have tested the number.
Canceling the old service before the port is completed can interfere with the transfer. Keep the old carrier active until HighLevel confirms the number has moved and your tests pass.
A successful port does not mean every configuration around the old phone system automatically appears in HighLevel.
The number itself moves, but you should treat the HighLevel setup as a new configuration that needs to be checked.
Do not assume that porting the phone number moves your historical phone-system data from the previous provider.
In particular, moving a number from Twilio to LC Phone does not automatically migrate historical data, old call recordings or messaging registration from the Twilio account.
The number moves. The historical data and configuration are a separate matter.
Save important recordings, review integrations, document routing rules and identify workflows that depend on the existing number before you schedule the cutover.
Porting a phone number does not automatically complete every messaging compliance requirement.
For US local numbers, review the current A2P 10DLC requirements before sending SMS or MMS. If the number needs to be associated with an approved campaign, complete that process before relying on the number for messaging at scale.
US and Canadian toll-free numbers can have separate toll-free verification requirements.
For a broader look at HighLevel's communication setup, see GoHighLevel SMS Pricing and GoHighLevel Phone System.
Yes, but this is generally treated as a number migration rather than the standard external-carrier port-in workflow.
HighLevel has a dedicated process for moving US local and toll-free numbers from a Twilio account to LC Phone. HighLevel Support coordinates the migration after the required account and phone-number identifiers are supplied.
You may need information such as the losing Twilio Account SID, destination HighLevel Location ID, the affected phone numbers and a preferred cutover window.
This changes the phone system managing the number. After the cutover, future calls and SMS can route through LC Phone, but historical Twilio data and recordings do not automatically come along with the number.
If you are currently using Twilio, do not start with the standard non-Twilio porting form. Use the migration path that matches your current provider.
Yes, but this is another situation where the correct process is different from porting.
HighLevel's Move Numbers tool supports eligible LC Phone to LC Phone moves between sub-accounts within the same agency. The current in-app tool supports eligible US and Canada numbers.
The source and destination sub-accounts must meet the tool's eligibility requirements.
| Move | Use Move Numbers? | Correct Direction |
|---|---|---|
| LC Phone → LC Phone, same agency | Yes, when eligible | In-app Move Numbers |
| Twilio → LC Phone | No | Phone-number migration |
| External carrier → HighLevel | No | Port-in process |
| Different agencies | No | Cross-account migration process |
Moving a number between sub-accounts also does not automatically move the destination account's contacts, conversations, analytics, A2P registration or historical call assets.
International porting is different from the current US in-app workflow.
HighLevel's current support documentation says the standard in-app port-in workflow supports numbers from the United States. For international numbers, you need to contact HighLevel Support so the appropriate international porting process can be used.
International requirements can vary significantly by country, carrier and number type. You may need regulatory information, address documentation or other country-specific records.
This is especially important if your business depends on the number for customer calls because international porting rules can be more restrictive than a standard US transfer.
If you are trying to bring an Indian business number into HighLevel, treat it as an international porting case rather than assuming the US workflow applies.
HighLevel's current documentation directs users with international numbers to Support for the appropriate international process. Availability depends on the country, number type and telecommunications provider.
Before making any changes to an Indian number, confirm that HighLevel can accept that specific number and ask what regulatory documents are required.
If you only need outbound calling from HighLevel and already own a business number, there is also a newer option to use an existing number for outbound calls with Verified Caller ID. That is not the same as porting, but it can be useful when you want to test HighLevel calling before moving the number.
The right choice depends on whether you want HighLevel to become the phone provider for the number or simply want HighLevel to handle eligible messaging while your current carrier keeps voice service.
Compare HighLevel Phone OptionsThis is probably the mistake I would avoid first. Keep the old service active until the port is confirmed complete and tested.
Your service address needs to match the carrier's records. Do not use a new office address simply because it is your current address.
For wireless numbers, the correct carrier account PIN is important. A fake or incorrect PIN can cause the request to be rejected.
The phone number moving does not mean your old recordings, analytics, workflows or other provider-specific data automatically moves with it.
Getting the number into HighLevel is only one step. Check A2P, toll-free verification and other applicable messaging requirements before sending campaigns.
External carrier, Twilio, LC Phone and same-agency moves have different processes. Choose the path based on where the number is currently managed.
Make test calls and messages. Check routing. Check workflows. Check the number from a completely different phone.
If you already have a business number that customers recognize, porting can make a lot of sense.
You avoid forcing customers to learn a new number while bringing the phone number into the same environment as your HighLevel CRM, conversations, workflows and other communication tools.
But I would not rush the process.
First determine whether you actually need to move the number. If you only want HighLevel SMS while keeping your existing voice provider, Number Hosting may be the better route. If you are moving a number between HighLevel sub-accounts, use the appropriate Move Numbers process. If the number currently lives in Twilio, use the migration process.
Once you know which path applies, prepare the carrier information carefully. Most porting headaches come from incorrect or mismatched account information, not from the basic idea of transferring a phone number.
Yes, eligible phone numbers can be transferred into HighLevel. The current in-app port-in workflow supports eligible US numbers, while international numbers use a separate support-assisted process.
HighLevel currently states that requests involving fewer than 50 numbers can take about two to four weeks, while larger or more complex ports can take about six to eight weeks.
The porting process itself should be evaluated separately from ongoing HighLevel phone usage costs. Carrier, number, regulatory and usage charges may apply depending on the number and setup.
Manual port requests require a signed Letter of Authorization. The current US in-app workflow can generate the LOA as part of the submission process.
It is a Letter of Authorization that authorizes the transfer of the phone number and confirms that the requester is authorized to make the change.
Eligible wireless numbers can be ported, but the correct carrier account information and PIN are important. HighLevel's manual documentation specifically warns that an incorrect wireless PIN can cause rejection.
International porting uses a different process. HighLevel currently directs international-number requests to Support for the appropriate international porting process.
Yes. Twilio to LC Phone is handled as a phone-number migration rather than the standard external-carrier port-in flow.
Yes. Eligible LC Phone numbers can be moved between sub-accounts in the same agency using HighLevel's Move Numbers tool. The current in-app tool supports eligible US and Canada numbers.
Do not assume they will. A phone-number migration does not automatically transfer historical phone-system data or call recordings from the previous provider.
Yes, depending on your goal. HighLevel supports Verified Caller ID for outbound calling with an existing number, and eligible numbers can also use Number Hosting for SMS/MMS while voice stays with the existing carrier.
No. Keep the old carrier active until the port is confirmed complete and you have tested the number.
Not necessarily. Messaging compliance and registration requirements can still apply after the number has been ported.
HighLevel's current documentation says Agency Owners and Agency Admins can submit eligible requests through the Port-In Numbers workflow when the feature is available through Labs.
If your business already has a phone number customers know, you may not need to start from scratch. Check your number's eligibility, prepare your carrier records, and choose the correct HighLevel migration path before submitting anything.
Updated for 2026. Number-porting availability, carrier requirements, timelines, documentation, regional rules and HighLevel workflows can change. Always check the current porting instructions for your specific number and country before submitting a request.