Porting Client Phone Numbers Into HighLevel: The Agency Checklist That Avoids Rejections

Sooner or later every HighLevel agency gets the same request: "Can we keep our number?" The client has had it for years. It's on their trucks, their Google Business Profile and every flyer in town. Losing it isn't an option, and a botched port that drops their calls for a day is worse.

The good news is that porting a number into HighLevel is routine once you know what the carrier will check. This guide covers when to port and when to host instead, what you need before you start, how long it takes, why ports get rejected and what to do after the number lands.

Disclosure: I am an independent entity from HighLevel. I am not an agent or employee of HighLevel and have no authority to make binding contracts or represent HighLevel. I receive referral payments from HighLevel, including through the links in this post. The opinions expressed here are my own and shall not be interpreted as representations, guarantees or statements made by HighLevel.

TLDR

• Porting moves the whole number into HighLevel. Hosting adds texting in HighLevel while voice stays with the current carrier.
• You'll need the carrier account number, a wireless PIN if it's a mobile number, the exact service address and a recent bill.
• HighLevel says ports of fewer than 50 numbers generally take about 2 to 4 weeks after documents are in, and larger ports about 6 to 8 weeks.
• Rejections usually come from details that don't match the carrier's records exactly.
• Keep the old service active until the port is done, and register A2P 10DLC before texting.

Should You Port the Number or Host It?

HighLevel gives you two ways to use a number a client already owns:

• Porting: the number moves fully into HighLevel's phone system (LC Phone), for calls and texts. HighLevel becomes the provider.
• Number hosting: according to HighLevel's number hosting guidelines, the original carrier keeps handling voice calls while messaging is routed through LC Phone.

Hosting suits a client who wants to keep their desk phones or phone system as they are but add texting in HighLevel. HighLevel's guide notes some limits: mobile numbers aren't eligible, numbers already texting through another provider aren't eligible as they are and hosting covers US and Canadian numbers only. Support-assisted hosting is estimated at 3 to 10 business days.

Porting suits a client who wants calls, texts, call tracking and missed-call text-back all running in HighLevel on one number.

What Do You Need Before You Port a Number?

According to HighLevel's port-in guide, the in-app request asks for:

• Current carrier account number: from the client's bill or carrier portal.
• The numbers: landline and wireless numbers listed separately.
• Wireless PIN: for mobile numbers, the carrier's port-out PIN (or the last four digits of an SSN when the carrier requires it).
• Authorized representative: the name and email of the person who will sign the Letter of Authorization (LOA).
• Service address: the full address exactly as the carrier has it on file.
• Billing statement: a recent bill as a PDF or image.

HighLevel's manual porting guide adds that the bill should be no older than 90 days, that PO Boxes aren't accepted as service addresses and that Google Voice numbers need a screenshot showing the numbers and the associated email.

The fastest way to collect all of this is a short onboarding form for the client. It's the same idea as the rest of your onboarding, which our guide to migrating clients into HighLevel walks through.

How Do You Submit a Port Request in HighLevel?

For US numbers, HighLevel has an in-app flow. Per its guide, only Agency Owners and Agency Admins can use it, and it's enabled through Labs:

1. Go to Phone System, then Phone Numbers, then Add Number and choose Port-in Numbers.
2. Enter the carrier and service address details and upload the billing statement.
3. Submit. HighLevel generates the LOA and emails it to the authorized representative to sign.
4. Track the request under Phone Numbers, then Port-In Numbers, where you'll see its status and carrier actions.

The LOA is an easy step to stall on. HighLevel's guide says that if it isn't signed, the port may not move forward, so make sure the client knows the email is coming and checks spam.

International numbers go through a manual process with HighLevel support.

How Long Does Porting Take?

HighLevel's porting options guide gives these estimates:

• Fewer than 50 numbers: about 2 to 4 weeks after the required documents are submitted.
• Larger or more complex ports: about 6 to 8 weeks.

Once approved, the carrier sets a cutover window, and HighLevel notes that same-day or date-specific ports aren't guaranteed. Tell the client this up front so nobody plans a launch around a date the carrier hasn't confirmed.

Why Do Port Requests Get Rejected?

HighLevel lists the common causes:

• A service address that doesn't match the carrier's records.
• An incorrect account number.
• A wrong or made-up wireless PIN.
• An unsigned LOA.
• A suspended carrier account.
• A bill that's too old or doesn't show the numbers.

Rejected requests can't be edited. You verify the details with the carrier, delete the rejected request and submit a new one, which restarts the clock. That's why it pays to check everything against a recent bill before you submit.

How Do You Avoid Downtime During a Port?

• Don't cancel the old service: HighLevel's guides are clear on this. Keep the number active with the current carrier until the port is complete and working.
• Set up before cutover: build the call routing, voicemail and missed-call text-back in the sub-account while you wait.
• Export history first: per HighLevel's migration guide, contacts, conversations, recordings and voicemails don't move with the number.
• Test right after: make inbound and outbound test calls and confirm the number shows in the right sub-account.

What Do You Need to Do After the Port?

A ported number can take calls, but texting needs one more step. HighLevel's guides say US local numbers need A2P 10DLC registration and to be tied to an approved campaign before sending SMS, and toll-free numbers need Toll-Free Verification. Don't assume an earlier registration carries over. Our A2P 10DLC guide covers the process.

Once texting is live, turn on the features the client came for: missed-call text-back, review requests and appointment reminders. A US local number in LC Phone costs $1.15 a month, plus usage for calls and texts.

More From NetPartners

• Moving from HubSpot to HighLevel: a zero-downtime migration plan.
• HighLevel snapshots: build a client setup once and reuse it.
• Where SaaS Mode money leaks: our Substack edition on rebilling phone and usage costs.
• r/highlevelaffiliates: our small community for HighLevel users and affiliates.

Frequently Asked Questions

How long does it take to port a number into HighLevel?

HighLevel says ports of fewer than 50 numbers generally take about 2 to 4 weeks after documents are submitted, and larger or complex ports about 6 to 8 weeks. Exact cutover dates aren't guaranteed.

What do I need to port a number to HighLevel?

The current carrier account number, the numbers, a wireless PIN for mobile numbers, the exact service address, a recent bill and an authorized representative who signs the Letter of Authorization.

What is the difference between porting and number hosting?

Porting moves the whole number into HighLevel. Hosting routes text messages through HighLevel while the original carrier keeps handling voice calls. Mobile numbers can't be hosted.

Why was my port request rejected?

Usually because something doesn't match the carrier's records: the service address, account number or PIN. An unsigned LOA, a suspended account or an old bill can also cause rejections. Rejected requests have to be resubmitted.

Will the client lose calls during the port?

Keep the old service active until the port is complete, and set up routing in HighLevel beforehand. HighLevel notes there may be a brief service impact during the cutover window.

Can I text from a ported number right away?

Not until messaging compliance is done. US local numbers need A2P 10DLC registration and an approved campaign, and toll-free numbers need Toll-Free Verification.