THINXSTER
Blog/GoHighLevel
GoHighLevel8 min readAugust 5, 2026

How to Delete Your GoHighLevel Account Without Losing Your Data (or Your Phone Number)

Cancel in the wrong order and you lose your business phone number permanently. Here's the exact sequence: what to export, when to port, and how to close the account cleanly.

RK
Ryan Korsz
Founder & CEO, Thinxster

TL;DR

Cancel in the wrong order and you lose your business phone number permanently. Here's the exact sequence: what to export, when to port, and how to close the account cleanly.

→ See how this applies to your business (free 30-min call)

There's one mistake in this process that's genuinely unrecoverable, and almost everyone makes it: they cancel the account first, then try to keep their phone number.

Once the account closes, the number is released. If it was the number on your truck wraps, your Google Business Profile, and eight years of yard signs, it's gone — and there's no support ticket that brings it back. Porting has to happen *before* cancellation, and it takes one to three weeks.

So the order of operations matters more than any individual step. Here's the full sequence.

Step 1: Decide What You're Actually Deleting

GoHighLevel has two account levels and people conflate them constantly.

  • A sub-account (location) is one business's workspace — contacts, funnels, calendars, conversations. Deleting one doesn't affect your other sub-accounts or your agency plan.
  • The agency account is the parent. Closing it terminates every sub-account underneath it and ends billing entirely.
  • If you're a business owner who was set up inside an agency's account, you may not control the parent at all — you'll need the agency to either release the sub-account or export the data for you. Start that conversation early, because it can take days and it's the step most likely to go sideways if the relationship ended badly.

    Step 2: Export Everything (Before You Touch Billing)

    Do this while the account is fully active. Once billing lapses, access can be restricted quickly, and reactivating just to pull a CSV is a bad week.

    Export, at minimum:

    1.

    Contacts. The Contacts view exports to CSV. Before exporting, decide whether you want all fields — custom fields, tags, source, and DND status matter more than people expect when they rebuild elsewhere.

    2.

    Opportunities. Your pipeline data exports separately from contacts. Grab every pipeline, including archived ones.

    3.

    Conversations. This is the one people skip and regret. Call recordings, transcripts, SMS threads, and email history are your record of what was promised to whom. There's no single clean bulk export for everything here, so plan time: pull what matters most, and pull recordings for any account where a dispute is plausible.

    4.

    Calendars and appointments. Export upcoming appointments and reconnect them to whatever you're moving to before you cancel, or clients will show up to nothing.

    5.

    Forms and survey submissions. These export per form. If you have twenty forms, that's twenty exports.

    6.

    Snapshots. If you built workflows, funnels, and campaigns worth keeping, create a snapshot. Snapshots can be transferred to another agency account, which is the only way to preserve build work.

    7.

    Media and funnel assets. Images, PDFs, and downloadable assets in the media library. Also save the actual HTML or screenshots of key funnels so you can rebuild the layout elsewhere.

    8.

    Invoices and payment records if you used the payments module — you'll want these for accounting.

    Give yourself a full working day for this. Two if the account is mature.

    Cancel first and you're negotiating with a support queue for data you could have downloaded in an afternoon.

    Step 3: Port Your Phone Numbers — This Is the Deadline

    Phone numbers in GoHighLevel typically live on the underlying telephony provider. To keep a number, you have to port it out to another carrier or account while the GHL account is still active and in good standing.

    The practical steps:

    1.

    Choose the destination — a new telephony account, a business VoIP provider, or your next platform.

    2.

    Request a port-out authorization from your current setup. You'll typically need the account details, a recent bill or account statement, the service address, and a signed letter of authorization.

    3.

    Submit the port request to the receiving carrier.

    4.

    Wait. Standard porting runs roughly 7–14 business days, sometimes longer for toll-free or if any account detail mismatches. A single typo in the service address can reset the clock.

    5.

    Confirm the port completed and test inbound and outbound calls and SMS on the new carrier before doing anything else.

    Do not cancel until you've placed a real call and sent a real text through the new setup. And check whether the number is registered for A2P messaging on the new side — a ported number without messaging registration will silently fail to deliver texts.

    Step 4: Untangle Domains, DNS, and Anything Pointing at GHL

    Before the account closes, audit what's still pointed at it:

  • Custom domains and subdomains used for funnels or websites. Repoint DNS to the new host, and set up redirects so existing links and any ads pointing at old URLs don't 404.
  • Email authentication records. If you set up SPF, DKIM, and DMARC entries for GHL sending, clean them up or update them for your new sender. Stale records cause deliverability problems later.
  • Tracking links and QR codes printed on physical materials. These are the ones that bite six months later.
  • Webhooks and integrations in other systems that call into GHL. They'll start failing silently.
  • Ad platform destinations. Any live campaign pointing at a GHL funnel needs a new destination *before* the funnel disappears, or you're paying for clicks to a dead page.
  • Make a list, work it, and check it twice. This step is boring and it's where most of the residual damage happens.

    Step 5: Cancel the Subscription

    Once exports are done, numbers are ported, and DNS is repointed:

  • For a sub-account, an agency-level user can delete it from the agency dashboard's account list. Deletion is not instantly recoverable — treat it as permanent.
  • For the agency account, cancellation happens in the agency Settings under Billing. Some plans require the cancellation to be submitted through billing settings rather than a support ticket; follow whatever flow the interface presents and capture a confirmation.
  • A few things worth knowing:

  • Billing is typically not prorated. You keep access through the end of the paid period, so cancel early in a cycle only if you're truly finished.
  • Any remaining wallet balance for calls and texts generally does not refund. Spend it down or accept it as a loss.
  • Take screenshots of the cancellation confirmation and save the confirmation email. Disputed charges after cancellation are a common enough complaint that documentation is worth the ten seconds.
  • Watch your card statement for the next two cycles to confirm the charges actually stopped.
  • Where the Data Actually Lands on the Other Side

    Exporting is half the job. The migration is where people lose things quietly, because CSVs import fine and still arrive wrong.

    Four mapping problems to plan for:

    Custom fields don't survive automatically. Your export has columns for things like "roof age" or "insurance carrier." The receiving system needs those fields created first, with matching types. Import before creating them and the data lands in a notes field or nowhere.

    Consent and DND status is legally significant. Your contact export includes who opted out of calls, texts, or email. That status has to carry over. Importing a list into a fresh system with everyone marked as contactable is how businesses accidentally text people who unsubscribed two years ago — a compliance problem, not just a courtesy one.

    Tags carry your segmentation logic. Years of tagging encode which leads came from which campaign, which customers bought what, who complained. Map them deliberately rather than dumping them into one field.

    Conversation history usually can't be imported at all. Most platforms have no way to ingest another platform's call recordings and text threads. Plan to keep the exported archive in cloud storage, organized by contact name and date, and accept that it's a reference archive rather than live data. For any account with warranty obligations or dispute risk, this archive is worth keeping for years.

    Before you consider the migration complete, run a spot check: pick ten contacts across different segments and verify every field, tag, opt-out status, and open opportunity landed correctly. Ten records will surface every systemic mapping error.

    Step 6: Ask Whether You Should Actually Be Leaving

    I'd be doing you a disservice not to raise this. Having watched a lot of these migrations, most people cancel GoHighLevel for one of four reasons — and only two of them are actually about the platform.

  • "It's too expensive." Compare against the full stack it replaced, not against zero. If you're only using it as a CRM, you're right that it's overpriced — but that's an under-utilization problem, and the fix is usually cheaper than a migration.
  • "It's too complicated." Almost always a setup problem, not a product problem. An account built by someone who knew what they were doing feels completely different to use.
  • "Our emails aren't delivering." Usually authentication and list hygiene, both of which follow you to the next platform. Migrating won't fix a bad sending reputation.
  • "We need depth this can't do." This is a legitimate reason to leave. Complex B2B sales processes, sophisticated lifecycle email, real product catalogs — go buy the specialist tool.
  • If you're leaving for one of the first three, there's a decent chance you'll rebuild the same problems somewhere else at higher cost.

    $102M+
    client revenue tracked through properly built GoHighLevel pipelines

    What a Good Setup Actually Looks Like

    The accounts that work aren't the ones with the most features turned on. They're the ones where every inbound lead gets contacted within minutes, qualified automatically, and pushed into a pipeline where nothing goes stale. We build exactly that: AI callers responding to every lead within 90 seconds, qualifying on fit and urgency, writing every transcript back to the pipeline.

    62%
    average lead qualification rate across client accounts

    If you're about to cancel out of frustration, it's worth twenty minutes to find out whether the platform was the problem. [Book a free strategy call](/book) and we'll give you a straight assessment — including telling you to leave if that's the right call.

    Free Weekly Briefing

    One AI Marketing Tactic.
    Every Tuesday. Free.

    What's actually working across our client accounts right now — ROAS moves, follow-up sequences, creative angles. The stuff that isn't in any blog post yet.

    No spam. Unsubscribe anytime. 1,200+ business owners already in.

    Ready to Deploy

    SEE THIS IN
    YOUR BUSINESS.

    30 minutes. We scope the exact systems that apply to your situation and give you a plan.

    ★★★★★ Trusted by 47+ local service businesses

    BOOK A STRATEGY CALL →