How to Migrate Phone Numbers in GoHighLevel — Complete Guide

Moving phone numbers between providers shouldn't require a support ticket and a prayer. Yet for most GoHighLevel users, phone number migration feels like navigating a maze blindfolded. The reality? It's a straightforward two-step process—once you know exactly where to look and what documentation you need.

In this guide, I'll walk you through the complete phone number migration workflow in GoHighLevel, covering everything from US to international numbers, migrations between sub-accounts, and the critical steps that prevent downtime on your calls and SMS. Whether you're consolidating accounts, switching from LeadConnector to Twilio, or moving numbers between agencies, you'll have a clear roadmap by the end.

And if you haven't experienced GoHighLevel's full platform yet, start your free 30-day trial here—double the standard trial period—to see how thousands of agencies run their entire business on one platform.

Understanding Phone Number Migration in GoHighLevel

GoHighLevel integrates with two primary phone number providers: LeadConnector Phone (LC Phone) and Twilio. When you need to move a phone number—whether between these providers, between sub-accounts, or into GoHighLevel entirely—the platform uses a structured migration workflow designed to eliminate downtime.

The core principle: you never actually "move" a number in the traditional sense. Instead, you request a migration, which triggers a backend process that reassigns the number from one sub-account to another while maintaining all call and SMS routing. This is why following the exact steps matters.

Before you start any migration, determine which scenario applies to you:

• New number to GoHighLevel: You're acquiring a fresh phone number within the platform
• Existing number migration: You're moving an already-owned number into or between GoHighLevel accounts
• Provider switch: Moving from LeadConnector Phone to Twilio (or vice versa)
• Sub-account transfer: Moving a number between different GoHighLevel sub-accounts or agencies

Documentation Requirements: US vs International Numbers

The documentation you need depends entirely on the country where the phone number is registered. This is non-negotiable—missing docs will delay or block your migration.

For US Phone Numbers:

• Valid government-issued ID (driver's license, passport, state ID)
• Proof of service address (utility bill, bank statement, or lease agreement dated within 60 days)
• Authorization letter (if migrating on behalf of a client)

US numbers typically migrate within 24–48 hours once documentation is submitted and approved.

For International Phone Numbers:

International requirements vary significantly by country. Some require business registration documents, tax IDs, or local compliance certifications. Before submitting anything:

1. Contact GoHighLevel support with the destination country
2. Request the specific documentation checklist for that country
3. Gather all documents in digital format (PDF preferred)
4. Ensure documents are in English or provide certified translations

International migrations typically take 5–15 business days, depending on country-specific regulatory requirements.

The Two-Step Migration Process

All phone number migrations in GoHighLevel follow the same structural workflow: Request → Approval → Activation.

Step 1: Submit the Migration Request

Log into your GoHighLevel account and navigate to Phone Numbers under your sub-account settings. Select the phone number you want to migrate and click "Request Migration" (or the equivalent option for your scenario). You'll see a form asking for:

• Current phone number
• Destination sub-account (if moving between sub-accounts)
• Destination provider (LeadConnector or Twilio)
• Your documentation files
• Any notes relevant to the migration

Upload all required documents at this stage. Incomplete submissions will be rejected and returned, delaying the process by several days.

Step 2: Wait for Approval & Activation

The GoHighLevel support team (or [email protected] for LC-specific requests) reviews your submission. They verify:

• All documentation is valid and complete
• The phone number is eligible for migration
• The destination sub-account exists and is properly configured

Once approved, the system automatically transfers the number to the new location. You'll receive an email confirmation, and the number will immediately begin routing calls and SMS to the new sub-account.

This is built into GoHighLevel. Try it free for 30 days →

How to Migrate from LeadConnector to Twilio

Many agencies start with LeadConnector Phone but eventually migrate to Twilio for cost savings, feature flexibility, or integration preferences. This migration requires a specific workflow.

Why Migrate from LC Phone to Twilio?

• Twilio pricing is often more competitive for high-volume accounts
• Direct Twilio integration offers more API flexibility
• Some agencies prefer managing their phone infrastructure independently

The LC to Twilio Migration Steps:

1. Create or link your Twilio account: If you don't have a Twilio account, create one directly at twilio.com. If you do, ensure it's properly verified and funded.
2. Submit the migration request: In GoHighLevel, go to Phone Numbers and select the LC Phone number you want to migrate. Choose "Migrate to Twilio" and provide your Twilio account SID and Auth Token.
3. Verify ownership: GoHighLevel confirms you own the Twilio account by checking your credentials.
4. Submit documentation: Upload the same ID and address proof required for any migration.
5. Wait for processing: The GoHighLevel team coordinates with Twilio to transfer the number. This typically takes 24–72 hours.
6. Activate in GoHighLevel: Once transferred, configure the number's routing, integrations, and automations within GoHighLevel as needed.

After migration, your calls and SMS will route through Twilio's infrastructure while remaining fully controllable within GoHighLevel's interface.

Moving Numbers Between Sub-Accounts and Agencies

One of the most common scenarios: you've onboarded a client in your sub-account but want to move their phone number to their own dedicated sub-account or agency. This requires coordination between accounts.

Within the Same Agency (Sub-Account to Sub-Account):

1. Go to the source sub-account and select the phone number
2. Request a migration to the destination sub-account
3. Confirm the destination sub-account ID (found in Account Settings)
4. Submit documentation if required
5. Wait for approval and activation

Between Different Agencies:

This is more complex and requires support coordination:

1. Contact GoHighLevel support at [email protected] (or [email protected] if using LC Phone)
2. Provide the phone number, source agency/sub-account, and destination agency/sub-account
3. Request the Twilio sub-account SID for the destination location
4. Include authorization from both account holders
5. Submit required documentation

Inter-agency migrations take longer—typically 5–10 business days—because they require manual approval from both account managers.

Troubleshooting Common Migration Issues

Issue: "Number is not eligible for migration"

Cause: The number may be newly acquired, in an active port request elsewhere, or flagged for compliance issues.

Solution: Wait 24 hours and retry. If it persists, contact support with the phone number. They can manually review eligibility.

Issue: Documentation rejected as incomplete

Cause: Your ID or address proof doesn't meet requirements (expired, low resolution, etc.).

Solution: Resubmit with high-quality scans (300+ DPI), ensure your name matches exactly across documents, and verify the address proof is dated within 60 days.

Issue: Calls/SMS don't route after migration

Cause: The number migrated successfully, but automations or integrations weren't updated in the destination sub-account.

Solution: Log into the destination sub-account, open the phone number settings, and reconfigure any integrations (CRM routes, automations, webhooks) that were in the source account.

Issue: Migration request stuck in "Pending" status for weeks

Cause: Your submission may have been missed, or GoHighLevel is awaiting clarification.

Solution: Reach out directly to [email protected] with your phone number and migration request ID. Ask for a status update and escalate if needed.