Move Numbers in GoHighLevel

/ CRM, GHL / By

How to Move Phone Numbers Between GoHighLevel Accounts

If you manage multiple workspaces in tools like ClickUp and also run several sub-accounts in GoHighLevel, you may eventually need to move phone numbers between accounts. This guide walks you step by step through moving Twilio-based numbers between GoHighLevel accounts in the US and internationally, while preserving tracking, calls, and SMS flows as much as possible.

The process is handled entirely through GoHighLevel support and follows strict carrier rules. Understanding the limitations, requirements, and timelines will help you plan the move with minimal disruption.

Before You Move Numbers in GoHighLevel

Moving phone numbers across GoHighLevel accounts is not a simple in-app toggle. It is a carrier-level change that must be completed by the support team, and there are important constraints you should know in advance.

Key requirements for GoHighLevel number moves

  • Only numbers owned by GoHighLevel (through its Twilio backbone) can be moved.
  • Your account currency must be USD, CAD, GBP, AUD, or NZD.
  • The number must be active and not in the process of being ported in or out.
  • You must have access to both the source and destination sub-accounts, or provide clear written authorization.

Because calls and SMS are tied to Twilio sub-accounts under GoHighLevel, changing ownership means your configuration and logs will be affected. Planning ahead reduces downtime and confusion for your clients.

Limitations When Moving GoHighLevel Phone Numbers

Before submitting a move request, confirm that your number is eligible and that you understand the trade-offs.

What cannot be moved inside GoHighLevel

  • Non-GoHighLevel numbers: Numbers not directly purchased through GoHighLevel’s built-in phone system cannot be transferred between internal sub-accounts via this process.
  • Local regulation restrictions: Certain regions may not support moving numbers between different GoHighLevel accounts due to carrier or regulatory rules.
  • In-flight porting: If your number is currently being ported in or out of GoHighLevel, it must finish or be cancelled before you can request a move.

What data you might lose when moving numbers

When a number is reassigned to a different sub-account in GoHighLevel, some data remains tied to the original Twilio sub-account. Common impacts include:

  • Historical call logs remaining in the old sub-account reporting.
  • Past SMS history becoming inaccessible in the new sub-account.
  • Previous tracking associations (funnels, forms, automations) needing to be reconfigured.

Plan to export or document any critical reports before you move the number.

Information You Must Collect for GoHighLevel Support

GoHighLevel support requires a clear and structured request so they can safely move the number. Prepare the following before opening a ticket.

Account and number details for the move

  • Source account: The existing GoHighLevel account or sub-account ID that currently owns the number.
  • Destination account: The GoHighLevel account or sub-account ID where you want the number moved.
  • Phone number list: A complete list of numbers to be moved, written in full E.164 format (e.g., +15551234567).
  • Country and type: Specify whether each number is local, mobile, or toll-free, and which country it belongs to.

Authorization for moving numbers in GoHighLevel

To protect account security, GoHighLevel support will only process moves when they have proof of authorization.

  • If you own both accounts, submit the ticket from the primary email on file for the GoHighLevel agency account and clarify your role.
  • If you are moving numbers to another client’s GoHighLevel account, obtain written authorization and include it in your ticket.

Clear authorization speeds up the process and avoids back-and-forth emails.

Step-by-Step: How to Request a GoHighLevel Number Move

Numbers are moved by the support team. Follow the steps below to submit a complete and accurate request.

1. Confirm eligibility in GoHighLevel

  1. Log into your GoHighLevel agency account.
  2. Open the sub-account that currently owns the number.
  3. Navigate to the phone numbers section and confirm the number is active and owned by the system (not an external provider).

2. Gather required details

  1. Copy the source sub-account or account ID.
  2. Identify the destination GoHighLevel sub-account or account ID.
  3. Create a list of all numbers to move using E.164 format.
  4. Note each number’s country and type (local, mobile, or toll-free).

3. Open a support ticket with GoHighLevel

  1. Go to the official support portal and log in with your agency email.
  2. Create a new ticket specifically requesting a phone number move.
  3. In your message, include:
    • Source account ID
    • Destination account ID
    • Full list of numbers with E.164 formatting
    • Country and number type details
    • Explicit authorization to move the numbers

4. Wait for confirmation from support

  1. Support will review your request and may ask for additional verification.
  2. Once approved, they will schedule and complete the move on the backend.
  3. You will receive confirmation when the numbers have been reassigned within GoHighLevel.

During the transition window, avoid making major configuration changes to the affected numbers to reduce the risk of conflicts.

Reconfiguring Numbers After the GoHighLevel Move

After support confirms the move, you must verify that the numbers behave correctly in the new sub-account.

Post-move checks inside GoHighLevel

  • Go to the phone numbers section in the destination sub-account and confirm each moved number appears.
  • Assign each number to the proper users, teams, or workflows.
  • Test inbound and outbound calls to verify audio and routing.
  • Send test SMS messages to confirm deliverability.

Re-creating tracking and automations

Some tracking logic and automations may need to be rebuilt in the new GoHighLevel destination:

  • Update call tracking in funnels, websites, and forms.
  • Reconnect numbers to call queues, IVRs, or forwarding rules.
  • Re-link numbers to campaigns, workflows, and triggers.
  • Adjust any integrations that referenced the old sub-account configuration.

Document these items beforehand so you can systematically restore them after the number move completes.

US and International GoHighLevel Number Moves

GoHighLevel works with Twilio as its backbone, and Twilio’s regional rules apply to each number. This affects how quickly numbers can be reassigned and what documentation may be requested.

Special considerations for international numbers

  • Some countries have strict regulations on ownership changes and address requirements.
  • Additional documents (business address, proof of identity, etc.) may be requested by carriers.
  • Certain regions may not support moves between different GoHighLevel accounts at all.

To review the most current regional rules, consult the official documentation at this GoHighLevel help article on moving phone numbers.

Best Practices for Managing GoHighLevel Number Moves

Following best practices will help you keep communication smooth for your clients and internal teams.

Planning and communication tips

  • Schedule moves during low-traffic hours for your business or client.
  • Notify stakeholders in advance about possible short interruptions.
  • Export or screenshot key call and SMS reports before the move.
  • Create a short test checklist to run immediately after the move.

If you need advanced help designing a scalable account structure or telephony strategy around GoHighLevel, agencies such as Consultevo specialize in implementations and migrations.

Summary: Moving Numbers Safely in GoHighLevel

Moving phone numbers between GoHighLevel accounts is a controlled support-driven process that shifts ownership of Twilio-based numbers from one sub-account to another. By understanding the eligibility rules, preparing complete information, and coordinating closely with support, you can move both US and international numbers with minimal disruption.

Use the steps in this how-to as a checklist: confirm eligibility, gather account details, submit a thorough ticket, then reconfigure and test numbers in the destination sub-account. With careful planning, GoHighLevel phone number moves can be completed smoothly while keeping your communication systems reliable and compliant.

Need Help With ClickUp?

If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.

Scale GoHighLevel

“`