Moving a Franchise Phone Number in GoHighLevel: What Stays Behind

A franchise branch is closing. The phone number printed on its vans, business cards, and customer invoices is staying with the business. The plan sounds simple: move that familiar number into another GoHighLevel location and let the receiving team answer it.

There is a catch: HighLevel can move an eligible number between subaccounts in one agency, but the prior contacts and conversations stay in the source account. Messaging registration and call settings need their own checks. The new branch might have the right number in its phone list and still be unready for the next caller.

If you need to move a GoHighLevel phone number between subaccounts, the useful decision happens before anyone clicks Move Numbers. What must the destination be able to do on the first call, and what information will remain behind?

First, identify which kind of number move you’re making

This article covers one specific case: reassignment of an eligible number between two existing subaccounts under the same HighLevel agency. It does not cover transferring an entire subaccount to another agency or porting a number from an outside carrier.

According to HighLevel’s September 4, 2026 Move Numbers guidance, the agency-level tool supports LC Phone to LC Phone moves. It also supports Twilio to Twilio moves when both subaccounts share the same Master Twilio account. The in-app route currently supports US and Canadian numbers, with up to ten eligible numbers in one move.

Those conditions matter when a franchise restructures. Two branches can share a brand and still sit under different agencies or phone providers. A Twilio number under another Master Twilio account is not eligible for the same in-app transfer. A provider change between LC Phone and Twilio belongs to a different process.

HighLevel’s phone-number migration and porting guide explains the other paths. Use that guide when the agency relationship, provider, or country does not match the same-agency tool. BrandLyft’s multi-location setup checklist covers the wider branch rollout. This move assumes the receiving branch already has its own subaccount.

The number moves. Five kinds of history and setup do not simply follow it

Imagine an established branch transferring its main line to a nearby office after the original location closes. The new office knows the telephone number, but a returning customer expects somebody to recognize an unfinished estimate from last month.

Moving the number alone will not put that estimate conversation in the destination inbox. HighLevel separates the phone number’s assignment from other records stored against a subaccount. That is the central boundary to plan around.

A familiar number can make a customer assume the person answering has the former location’s account notes, even though those records are still elsewhere. When that assumption is wrong, the receiving team needs a legitimate way to retrieve context. The move did not bring those records over.

Decide what the receiving team can see before cutting off source access

Find the relationships that remain active: appointments, open estimates, service issues, unpaid invoices, and promised callbacks. Then establish where those records currently live and which employee can answer questions about them after the transition.

A franchise may keep approved access to the old location for a period. It may retain permitted exports or move selected customer information through a separate process. Each option is a separate data and permission decision. Move Numbers does none of that. Nor does moving the number give staff permission to copy conversations or ignore communication preferences.

Keep source references with enough detail to explain what happened. If a customer says, “I left a voicemail yesterday,” staff need somewhere to look. Who can access the older voicemail, and when does that access end? An internal owner and an accessible record are better than a promise that someone will somehow find the old thread.

BrandLyft’s CRM data migration article addresses broader record-selection decisions. For this cutover, ask what history a caller will reasonably expect the next branch to have.

Check destination messaging registration before relying on texts

For eligible US local numbers, A2P 10DLC status belongs to the subaccount and its registration. It does not follow the digits alone. After the move, check the destination’s approved brand and campaign, then link the number where required by the messaging setup. A number appearing in the destination’s Phone Numbers screen does not prove it can send compliant business SMS.

HighLevel’s September 8 A2P number-linking instructions describe the number-level check. In the destination, review the approved campaign and link the number when needed. Then check for the expected A2P Verified indicator. An approved campaign and a linked number are two different conditions.

Toll-free messaging takes another path. Do not assume a toll-free verification automatically accompanies a transferred number; confirm its status in the receiving account. International and other messaging configurations have their own requirements. Avoid testing outbound SMS through an account that has not met the applicable registration and permission rules.

Moving a phone number does not create fresh permission for new automated texts, even if the receiving branch serves the same customers. The destination’s consent, opt-out, and communication-preference handling needs review apart from number ownership. A missed-call text-back workflow is particularly easy to overlook because it may send without an employee touching the conversation.

Write down the call path customers already use

A franchise number may ring several places depending on the hour: the front desk during business hours, an answering service after closing, or a backup employee when the desk is busy. When nobody answers, callers hear a voicemail greeting, and a separate workflow may offer a callback by text. The same number could also appear as outbound caller ID for staff.

Inventory the working behavior before moving it. Record forwarding, ring behavior, assigned users, voicemail, recording, whisper messages, business hours, and missed-call handling. Add the workflows that select or reference that number. Then name the intended destination behavior for each one.

The new branch might need a different greeting and routing rule, which is reasonable if the team planned it. Trouble starts when staff assume the old setup follows the phone number unchanged.

Check what external systems still publish or reference the number, too. A website, Google Business Profile, directory, ad, or old invoice may still send people to it. Keeping the digits can preserve that entry point, but it does not make the destination’s answering workflow correct.

The wider question of which branch should own each new lead belongs to BrandLyft’s GoHighLevel lead-routing guide for franchises. This move is smaller: prove that calls to one number reach the intended team.

Choose the cutover window based on call coverage, not convenience

An admin may have time to make the change on Friday afternoon. The business might not have anyone available afterward to test every route and fix a failed callback. A less busy window is useful only if someone can stay accountable through the checks.

Assign the HighLevel admin, test-call recipient, SMS registration owner, and final approver before the move. Someone else should own provider escalation if the setup fails. If a route fails, staff need a supported fallback for customer contact.

Do not build the plan around a guaranteed zero-interruption cutover. HighLevel does not promise that a moved number arrives with its old routing, messaging approval, and history already usable. Nor does a phone-number move provide a one-click restoration of customer context.

Set a short validation period after the transfer and tell the receiving team what will be checked. Someone should record the first failed test without marking the transition complete merely because the number shows up on screen.

Use the in-app move only after the preflight is signed off

For an eligible same-agency move, go to Agency Settings and open Phone Integration. Under Sub Account Settings, choose Move Numbers. Choose the source and destination subaccounts, select the eligible number or numbers, review the destination, and complete the move. The current interface permits up to ten numbers in one operation.

Pause before the final action. The source and destination Location IDs should already be in the change record. Confirm the exact number, country, phone provider, and receiving branch against that record. Similar location names are a poor substitute for IDs when the franchise operates several offices in one region.

Once the number appears in the destination, the transfer itself may be complete. The customer-facing cutover is not. That second decision belongs to the acceptance tests below.

Phone Number Move Acceptance Sheet

Use one sheet per moved number, even when several numbers are transferred together. The purpose is to prevent a successful tool action from becoming an unverified declaration that the branch is ready.

Record the number in international format, both Location IDs, agency, provider, country, planned window, and actual move time. Add test owners and the release approver. Keep any registration evidence and historical-data access decision attached to the same record.

The sheet should allow three outcomes for every test: Pass, Blocked, or Not applicable with a reason. A blank SMS result is not a pass. A branch that does not use SMS should say so rather than inventing a successful messaging test. Review the final release decision once every required row has an owner and result.

Run the tests from outside the destination, not just inside the settings screen

Start with an inbound call from an external test handset. Check whether the right location receives it and whether the intended staff member answers. Then make an outbound call and confirm which caller ID the recipient actually sees. Outbound-number preferences can differ from what the team expects, especially when users have access to more than one number.

Next, test an unanswered call. Listen to the voicemail or forwarding behavior rather than reading the configuration and assuming it is correct. For an after-hours path, use an approved test window or a safe configuration review. Do not interfere with real callers. Any missed-call text-back path should be included when messaging is allowed.

For SMS, use an authorized test contact after checking the destination’s registration and consent requirements, then send an inbound message and verify the receiving account. Then send an outbound reply through the intended workflow or operator and verify the recipient sees the right sender. Record failures and their error details, not just a checkbox.

Finally, inspect a test conversation and associated task or alert. Does the destination team see the message, know who owns the reply, and receive the expected notification? The tests should reflect real branch behavior. One call from the admin who moved the number is not enough.

A failed test changes the release decision

Voice may work while SMS fails because the number still lacks the appropriate campaign link in the destination. That is an incomplete handoff. Keep that messaging path on hold while the registration issue is resolved. Do not send unregistered automated texts simply because calls are now reaching the correct office.

If calls reach the wrong employee, check forwarding, assignments, and the number’s configuration first. If customers cannot reach the destination, use the planned escalation path and an accurate temporary contact method. Moving the number back is not a guaranteed rollback. It could require another eligible move, setup work, and the same tests.

If an eligible LC Phone move fails, HighLevel asks for both Location IDs and the affected numbers when contacting Support. Keep the failed action, error, time, and support reference in the change record. When the provider is unsupported, use the applicable migration process instead of repeating the failed attempt.

Do not declare the cutover complete while the receiving branch is unready

The destination must own the number, the intended team must answer its calls, and any active messaging path must have its required registration. Older customer context needs an agreed access route, too. An authorized operator should sign off on any remaining exceptions.

That is how a familiar franchise phone number can keep doing its job after the office behind it changes. The number itself is only one part of the handoff.