<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=412158892933457&amp;ev=PageView&amp;noscript=1">
Skip to content
English
  • There are no suggestions because the search field is empty.

GHL to GROW Subaccount Porting Manual

GHL to GROW Subaccount Porting Manual

Purpose

This document outlines the process for onboarding customers who currently have subaccount(s) in Go High Level (GHL) and wish to migrate those assets to Hapana’s GROW platform.

There are two available methods for completing this migration.


Method 1: Snapshot Transfer

The customer can create a snapshot of their subaccount(s) within their current GHL agency and provide that snapshot to Hapana. This method allows assets to be copied into their GROW subaccount.

Pros

  • Quick and easy to execute
  • Allows the customer to retain their original account and data within their current agency (if they choose to maintain their subscription)

Cons

  • Contacts, notes, and historical activity will not transfer
  • Only the following assets will be migrated:
    • Workflows
    • Custom fields
    • Custom values
    • Forms and surveys
    • Media/images
    • Email and SMS templates
    • Snippets

Method 2: Full Subaccount Porting (Preferred)

The customer can request a full subaccount transfer from their current agency to Hapana via the GHL Agency view.

This can be done by:

  • Submitting a support ticket to GHL, or
  • Following the instructions within the GHL Agency UI HERE

Hapana Customer Relationship Number: 0-001-211

Pros

  • Full migration of all data, including:
    • Contacts
    • Notes
    • Conversations
    • All assets

Cons

  • The current agency will permanently lose access to the subaccount
  • Agency-level permissions will no longer be available, meaning:
    • Snapshot creation will require Hapana Support
    • Adding users across multiple accounts will require Hapana Support
    • Certain SaaS features may be limited or managed by Hapana
  • Payments will be processed through Hapana CORE (Stripe), so direct Stripe access within GROW will not be available

Additional Information

Phone Number (Calling & SMS)

Hapana uses Twilio as the mobile carrier, so phone number migration depends on how the number was originally provisioned:

If purchased directly through Twilio

  • Submit a porting request with Twilio at least a day before the GHL subaccount transfer
  • Hapana will provide:
    • Subaccount SID
    • Bundle SID (Australia only)
    • Address SID (Australia only)

If purchased through LeadConnector (GHL)

  • Request GHL Support to port the number along with the subaccount transfer
  • Hapana will provide:
    • Subaccount SID
    • Bundle SID (Australia only)
    • Address SID (Australia only)

If purchased from a different carrier (Verizon, AT&T, Telstra, and others)

  • Check with Hapana if the phone number can be ported to Twilio
  • Common requirements include your Account Number, PIN, and Owner information

What Hapana will handle

  • Creation of a Twilio subaccount
  • A2P registration (U.S. customers) or Registration Bundle (Australia or UK customers)

Alternative Option

  • Hapana can provision new phone numbers upon request

Note:
After porting, SMS functionality may take 24–72 hours to fully restore. Calling functionality is usually restored immediately.


Email Setup

Hapana will provide DNS records for email configuration. These must be added to your domain provider.

Once DNS records have propagated, full email functionality will be available after the subaccount is successfully ported.

Until the DNS records have been added to your domain host, emails will likely not be sent from our platform, or will land in spam.


Important: Domain Configuration Best Practices

If your domain is managed through WIX, please inform us.

WIX is not recommended for CRM email configuration because:

  • It does not properly support subdomain configurations
  • It may force the use of the root domain

Why this matters

Using your root domain for CRM communications increases risk. If domain reputation is damaged due to email sending issues, the entire domain may be impacted.

Best Practice

Always use a subdomain for CRM email:

  • ❌ Root domain: @yourwebsite.com
  • ✅ Recommended: @marketing.yourwebsite.com

This protects your primary domain and improves deliverability control.