Taking over someone else's GoHighLevel account can feel like walking into a business where nobody has labelled the switches.
There are dozens of workflows, hundreds of tags, several sales pipelines, and integrations connected to services you don't recognise. Some automations appear to work. Others send duplicate messages, miss follow-ups, or move opportunities into the wrong stages.
The previous agency says everything was working when they left. Your team says it hasn't worked properly for months.
So where do you start?
The best way to fix an inherited GoHighLevel account is to audit what already exists before rebuilding anything. You need to understand how leads enter the system, which workflows control them, where information gets lost, and whether your team has proper control over the account.
This guide walks you through that process, from securing access and tracing broken automations to cleaning up your CRM and deciding which problems actually justify a rebuild.
What Should You Do First When You Inherit a GoHighLevel Account?
Start with a read-only audit of the account's access, workflows, CRM data, pipelines, calendars, messaging and integrations. Identify which processes are working, document the problems affecting customers or revenue, and fix the highest-risk issues first.
Avoid deleting workflows, merging contacts, changing live triggers or disconnecting applications until you understand their dependencies. A broken automation can often be repaired without rebuilding the entire account.
The objective is simple: find out what's wrong, protect what's working, and make changes you can verify.
Why Inherited GoHighLevel Accounts Often Stop Working Properly
Most inherited CRM problems don't have one dramatic cause. They're usually the result of smaller issues building up over time.
A marketing agency might install a snapshot containing several prebuilt workflows. Six months later, someone creates another follow-up sequence without checking whether an existing workflow already handles the same leads.
An employee might change a custom field without realising that three automations depend on its original value.
A freelancer might connect a form through Zapier and leave without documenting the integration.
Eventually, the account becomes difficult to maintain because nobody has a complete picture of how its components work together.
Typical warning signs include:
- New enquiries appear in Contacts but never reach the sales pipeline.
- Customers receive two or three versions of the same follow-up message.
- Appointment reminders are sent at the wrong time or not at all.
- Workflows remain active even though the campaigns they supported have ended.
- Old users and external applications still have account access.
- Opportunities are assigned to employees who no longer work for the business.
- Email campaigns show sending activity but generate unexpected delivery failures.
- Dashboards report leads that don't match the actual number of enquiries.
These symptoms don't automatically mean the whole account is unusable.
A form may be connected to the wrong workflow. A trigger filter may depend on an empty field. An integration may need reauthorisation. The underlying system could still be perfectly serviceable.
That's why diagnosing the source of the problem is more valuable than simply replacing the visible component.
Step 1: Secure Your GoHighLevel Account Before Making Changes
Before investigating workflows or CRM data, establish who owns the account and who can access it.
This is especially important if the system was originally set up by an external agency.
Check who controls the account
GoHighLevel separates agency-level access from sub-account access. Having administrator permissions inside a sub-account doesn't necessarily mean you control the agency account that hosts it.
Confirm:
- Who owns the agency account hosting your business.
- Whether your business can access and manage its own sub-account.
- Who controls the subscription and relevant billing arrangements.
- Whether previous employees or contractors still have access.
- Who owns the connected domains, phone numbers and external applications.
- Whether the account can be maintained without the previous provider.
Within the sub-account, open Settings → Users and review the available roles and permissions.
Users should have access appropriate to their responsibilities. A sales representative usually doesn't need the same administrative permissions as the person maintaining integrations and workflows.
Don't share master credentials with a new freelancer or consultant. Create an appropriately permissioned user account instead.
Understand the difference between an account transfer and a snapshot
If you're leaving one GoHighLevel agency for another, this distinction matters.
An official sub-account transfer moves the supported account records and assets between agencies. It requires the appropriate agency-level permissions and coordination.
A snapshot is different. It copies selected configuration assets, such as workflows, forms, pipelines and templates. It is not a complete backup of your live business.
Snapshots don't transfer contact records, conversation history, appointments or all connected integrations.
Even an official sub-account transfer requires a dependency review. Phone-number arrangements, email providers, sending domains and other services may need separate attention.
What to fix: Establish account ownership, review unnecessary access and document external dependencies before approving any transfer or restructuring.
If you discover a genuine security problem, escalate it to the account owner and contain the risk through an authorised process rather than waiting for routine cleanup.
Step 2: Document the Current Setup Before Touching Anything
Once you have appropriate access, resist the urge to start cleaning.
You need a reliable picture of the account as it exists today.
Start by creating an inventory of the systems the business actually uses.
Area
What to document
Workflows
Name, purpose, trigger, status and business owner
Pipelines
Active pipelines, stages and opportunity owners
CRM data
Important custom fields, tags and segmentation rules
Lead capture
Live forms, surveys, funnels and landing pages
Calendars
Booking calendars, staff assignments and reminders
Communications
Sending domains, phone numbers and messaging setup
Integrations
Connected apps, authentication owner and purpose
Reporting
Key dashboards, metrics and data sources
You don't need to map every unused template immediately. Start with the processes that affect leads, appointments, customer communications and payments.
Use Audit Logs to understand recent changes
GoHighLevel includes Audit Logs for reviewing supported account activity.
Depending on your permissions, you can find these under Settings → Audit Logs at the relevant agency or sub-account level.
Review recent changes involving workflows, users, opportunities and other important modules.
Look for changes made shortly before problems appeared.
For example, if appointment reminders stopped working after someone edited a calendar configuration, that change is worth investigating.
HighLevel currently retains standard Audit Logs for 60 days, so older events may no longer be available.
Record or export relevant evidence where permitted.
Don't mistake a snapshot for a recovery plan
If you need to prepare for major changes, assess what must be preserved separately: customer data, communications, live appointments, payment connections and external account credentials.
A snapshot can be useful for preserving reusable configuration, but it shouldn't be your only recovery measure.
What to fix: Create a baseline inventory, identify undocumented dependencies and preserve necessary evidence. Make structural changes only after you've assessed their potential impact.
Step 3: Trace One Real Lead Through the Entire System
This is one of the most useful checks you can perform.
Instead of reviewing dozens of workflows without context, follow a single customer journey from beginning to end.
Imagine someone submits a quote request through your website.
What should happen next?
A typical journey might look like this:
Website enquiry → Contact created or updated → Workflow triggered → Opportunity created → Follow-up sent → Appointment booked → Sales pipeline updated
Now compare that expected journey with what actually happened.
Start with the original enquiry
Find a recent enquiry that didn't receive the correct response.
Check whether the form submission was captured and whether it created or updated the expected contact record.
If no contact exists, investigate the form, integration or submission process first.
If the contact exists but no opportunity was created, inspect the workflow responsible for opportunity creation.
If an opportunity exists but the customer didn't receive a message, investigate the communication action rather than assuming the entire workflow failed.
This approach helps you identify the first point at which the real journey differs from the intended one.
Ask these five questions
Did the original event occur?
Was the correct contact record created or updated?
Did the intended workflow enrol the contact?
Did its required actions execute?
Did the expected business outcome occur?
A workflow can run successfully without producing the result the business needs. For example, a message action might execute, but the message could still fail delivery.
What to fix: Correct the first confirmed failure, then repeat the full journey to see whether the next stage operates correctly.
Avoid changing several unrelated settings at once.
Step 4: Find Broken, Duplicate and Conflicting Workflows
Workflows are often where inherited GoHighLevel accounts become most complicated.
A previous provider may have created separate automations for new leads, missed calls, appointments, quotations and follow-ups.
Later, another provider may have added new versions without retiring the originals.
That doesn't automatically make every overlapping workflow wrong. Several workflows can legitimately respond to the same event.
The problem starts when their combined actions produce unintended results.
Create a workflow map
Open Automation → Workflows and review the active automations that affect important business journeys.
For each workflow, identify its:
- Purpose and entry trigger.
- Trigger filters and qualification rules.
- Actions, waits and IF/Else branches.
- Re-entry and exit settings.
- Connected fields, tags, calendars or integrations.
- Relationship with other workflows.
Group workflows by the events that start them.
For instance, if three workflows respond to the same website form submission, compare their filters and actions.
Do they serve different purposes, or do two of them send the same acknowledgement?
Don't disable one simply because the triggers look similar.
Use Trigger Statistics to investigate missing enrolments
Inside the Workflow Builder, Trigger Statistics can show how many events were attempted, matched or unmatched.
The detailed view can help identify why an event didn't satisfy a trigger's conditions.
This is useful when some leads enter a workflow while apparently similar leads don't.
Current Trigger Statistics cover the most recent 30 days.
Use Enrollment History and Execution Logs
These two tools answer different questions.
Enrollment History helps establish whether a contact entered the workflow.
Execution Logs help explain what happened after the contact entered, including available action results and errors.
For example, a contact may have enrolled successfully but followed an unexpected IF/Else branch because a custom field contained the wrong value.
In that case, changing the trigger wouldn't solve the problem.
Also review the workflow's re-entry settings. Returning contacts may behave differently from new contacts, and certain trigger types have specific re-entry rules.
How to fix a broken workflow safely
Once you've identified the issue:
Record the current configuration and affected contacts.
Confirm the intended business outcome.
Identify the specific trigger, filter, branch or action causing the failure.
Assess whether the change will affect contacts already enrolled.
Make the approved correction in a controlled manner.
Test the relevant journey and verify the outcome.
Monitor subsequent legitimate activity for recurrence.
If multiple workflows are broken and their relationships aren't clear, getting GoHighLevel technical support may be safer than repeatedly experimenting with live customer automations.
The important distinction is that repairing a workflow means correcting a known fault; rebuilding it means replacing its underlying design.
Those are not the same job.
Step 5: Clean Up CRM Contacts, Tags and Custom Fields
Inherited accounts often contain years of data, including imports from previous CRMs, outdated tags and fields created for campaigns that no longer exist.
The result is a CRM where the same type of lead might be classified in several different ways.
For example, one workflow may look for New Lead, while another uses new-lead and a third relies on a custom field called Lead Status.
That inconsistency can make segmentation and automation difficult to understand.
Find the data your business actually depends on
Review the Contacts section and identify:
- Fields used for lead qualification.
- Tags referenced by active workflows.
- Contact owners and assignment rules.
- Duplicate or incomplete records.
- Old segmentation rules.
- Fields used in reports and pipeline automation.
Don't assume a field is unnecessary because its name is unfamiliar.
Open the workflows that reference it before making changes.
Handle duplicate contacts carefully
HighLevel provides tools for identifying and merging duplicate contact records, but merges cannot simply be undone.
Before combining contacts, review the master record, communication history, opportunities and important field values.
Also check Settings → Business Profile → Contact Preferences for the available duplicate-contact settings.
A high number of duplicate records may indicate a problem with imports, forms or connected applications.
Fixing the source of duplicates is often more valuable than repeatedly merging the records they create.
What to fix: Agree on one naming convention, document important fields, improve duplicate detection and remove obsolete data only after checking dependencies.
The goal isn't to make the CRM look tidy. It's to make the information reliable enough for your team and automations to use.
Step 6: Check Pipelines, Opportunities and Appointment Booking
A GoHighLevel account may collect leads correctly while still failing to move them through the sales process.
One reason is that the configured pipeline no longer matches how the business operates.
Imagine a recruitment agency with separate processes for candidate applications and client vacancies.
If both are forced through an unsuitable opportunity pipeline, staff may struggle to understand what stage each relationship has reached.
Review the pipeline against the real sales process
Open Opportunities → Pipelines and review the available stages.
Ask:
- Does each stage represent a genuine step in the sales process?
- Is there a clear owner for new opportunities?
- Are opportunities being created automatically when appropriate?
- Are leads getting stuck in stages nobody monitors?
- Are duplicate opportunities being created?
- Are lost deals being closed properly?
- Do reported opportunity values represent meaningful amounts?
Where possible, compare actual customer records with pipeline entries.
Test appointment bookings from beginning to end
Calendars deserve their own attention because a booking involves several connected processes.
Verify that the relevant calendar is assigned to the correct person or team, availability is accurate and booking notifications work as expected.
Then check whether appointments trigger the intended follow-up actions.
If the booking appears in the calendar but not in the opportunity pipeline, investigate the configuration that connects those processes.
What to fix: Correct specific stage rules, opportunity creation, ownership or calendar associations.
Avoid deleting pipelines or moving large numbers of opportunities before reviewing workflow and reporting dependencies.
Step 7: Check Whether Your Emails, SMS and Calls Actually Work
Sometimes the workflow isn't broken at all.
It fires correctly, reaches the sending step, and records an action. But the customer never receives the intended message.
That's a communication problem, not necessarily a workflow-trigger problem.
Audit email sending
Check the sender domain, configured email provider, available sending reports and relevant authentication records.
SPF, DKIM and DMARC help receiving email systems authenticate messages. Incorrect configuration can contribute to delivery or authentication failures.
Also review sender addresses, suppression settings, unsubscribe handling and available bounce information.
Don't assume every missing email is caused by spam filtering. Use the actual sending evidence.
Audit phone and SMS configuration
Review the numbers connected to the account, their intended use, routing rules, provider configuration and available delivery errors.
Check whether the business has changed phone providers or moved between agencies.
Some phone numbers and communication configurations require additional migration steps when accounts change hands.
For UK businesses, confirm that messages are sent using appropriate routing and that marketing communications comply with the applicable requirements.
Check Do Not Disturb and unsubscribe settings
If a contact has opted out or has applicable communication restrictions, don't override those settings just to make a workflow send.
The correct fix may involve changing the business process rather than removing a valid suppression.
What to fix: Address documented sender authentication, provider, routing or action-level problems, and test through an authorised contact.
Step 8: Review Integrations That Nobody Fully Understands
A CRM may depend on several external applications without making those dependencies obvious.
You might discover that website leads arrive through Zapier, payments are connected through Stripe, reporting depends on another platform, and an important workflow sends data to an external webhook.
If one connection stops working, the visible problem may appear somewhere else.
Build an integration inventory
For every critical connection, record:
Question
Why it matters
What is connected?
Identifies systems involved in business processes
What data moves through it?
Shows dependencies and possible privacy implications
Who owns the connection?
Prevents reliance on inaccessible provider accounts
Where does the data go?
Helps investigate failures and unknown destinations
What happens if it fails?
Establishes operational risk
How can it be tested?
Makes future maintenance easier
Pay attention to integrations authenticated using a previous employee's or supplier's account.
If that access is revoked or expires, the integration may stop working.
Check webhooks and external automations
Review the expected event, destination endpoint, field mapping and available error logs.
If an external system isn't receiving information, determine whether GoHighLevel sent the request and whether the receiving system processed it successfully.
Don't automatically disconnect an unfamiliar webhook. It may be responsible for a critical payment, appointment or reporting process.
Where integrations are undocumented, the safest approach is to establish their purpose and ownership before changing them.
What to fix: Replace obsolete connections, repair failed authentication, correct mappings and document the responsibility for each essential integration.
Step 9: Check Whether Your Reports Reflect Reality
A CRM dashboard can look perfectly organised while giving the business the wrong picture of performance.
For example, a sales dashboard might show fewer opportunities this month.
That could mean fewer enquiries arrived. But it could also mean automation stopped creating opportunity records while forms continued collecting leads normally.
Those two situations require completely different responses.
Compare reports against real business activity
Choose a recent reporting period and compare:
- Form submissions with CRM contacts created or updated.
- Qualified enquiries with opportunities opened.
- Bookings with actual appointment records.
- Won opportunities with confirmed sales where available.
- Lead sources with the original enquiry records.
The figures won't necessarily match one-to-one because each metric measures a different event.
The point is to understand what each number represents and identify unexplained gaps.
What to fix: Correct the underlying tracking, workflow or field configuration before relying on dashboards for commercial decisions.
Step 10: Review UK Data Protection and Marketing Preferences
If you're inheriting a UK business account, technical configuration isn't the only concern.
You also need to understand how customer information is collected, stored, accessed and used.
Review privacy notices, relevant lawful bases, marketing preferences, consent records where needed, unsubscribe handling and data retention practices.
The distinction between different types of business contacts matters.
For example, UK electronic marketing rules under PECR can treat corporate subscribers differently from sole traders and certain partnerships. UK GDPR requirements can still apply when you're processing personal data for business marketing.
Check that relevant opt-outs and suppression lists are respected by automations.
Also identify any external integrations transferring personal data to third parties and confirm that the business understands those arrangements.
What to fix: Record compliance concerns, correct straightforward technical misconfigurations through an approved process and obtain appropriate legal or privacy expertise where the requirements are uncertain.
A technical account audit can highlight risks, but it is not a substitute for a formal legal compliance assessment.
How to Decide What to Fix First
After completing the review, you'll probably have a list of issues.
Some may affect revenue immediately. Others might simply make the account harder to manage.
Treating them all as equally urgent is a mistake.
Use this framework to prioritise the work:
Priority
Problem
What to do
Critical
Unauthorised access, suspected data exposure or harmful active communications
Escalate and contain the risk through an approved response
High
Lost leads, broken booking journeys or important messages failing
Diagnose and repair promptly
Medium
Duplicate automation, unreliable reporting or inconsistent CRM rules
Schedule controlled corrections
Low
Unused templates, unclear names or obsolete folders
Clean up after essential processes are stable
For each confirmed problem, document the affected process, evidence, proposed fix, responsible person and how success will be verified.
This turns a collection of technical observations into an actionable recovery plan.
A Practical Example: Why Rebuilding Everything Can Be the Wrong Decision
Consider a UK home-improvement business that changes marketing agencies because its enquiry follow-up has become unreliable.
The new team discovers 25 workflows, several pipelines and a collection of unused forms.
Some enquiries receive duplicate text messages. Others don't create opportunities.
At first glance, the account looks like it needs rebuilding.
But a structured investigation may reveal something much simpler.
Two workflows are responding to the same enquiry source and sending similar acknowledgements. Meanwhile, the opportunity-creation workflow has a filter that some valid enquiries don't satisfy.
The new team documents the existing processes, verifies these causes using actual enrollment and execution records, and proposes targeted corrections.
After approval, the team tests whether:
A qualifying enquiry is captured correctly.
The contact enters the intended workflow.
Only the intended acknowledgement is sent.
The correct opportunity is created.
The sales team receives the required notification.
This is a hypothetical example, but it illustrates an important principle: an account can look completely disorganised while only a few faults are responsible for its most serious business problems.
Fixing those faults may be faster, safer and less disruptive than replacing the entire setup.
Should You Fix, Optimise or Rebuild the Account?
There isn't one correct answer for every inherited GoHighLevel account.
Repair the existing account when the main CRM structure is sound and the problems can be traced to specific configurations, workflows or integrations.
Optimise the account when it works, but contains unnecessary complexity, inconsistent processes or automations that could be simplified.
Consider rebuilding when the underlying data structure and automation design no longer support the business, and a controlled redesign is more practical than maintaining the current configuration.
Before choosing a rebuild, account for the time required to preserve customer information, recreate integrations, reconnect communication services, validate the new setup and manage the transition.
If your existing workflows need substantial restructuring, GoHighLevel automation services can help turn an undocumented system into a maintainable one.
But the decision should follow an audit, not precede it.
What Should a Professional GoHighLevel Account Audit Deliver?
A useful audit should do more than tell you that the account is messy.
It should show you exactly what needs attention, why it matters and what it will take to correct.
At a minimum, you should expect a clear account inventory, evidence of identified issues and a prioritised set of recommendations.
A good report should answer questions such as:
- Which workflows are responsible for the most important business processes?
- Where are leads being lost or handled incorrectly?
- Are customer communications functioning as expected?
- Do CRM fields and pipelines support the current sales process?
- Which integrations are essential, broken or undocumented?
- What security and compliance configuration concerns need attention?
- Which problems can be repaired independently?
- Does any part of the system genuinely need rebuilding?
Just as importantly, the audit should separate diagnosis from implementation.
You should understand the proposed fixes before authorising someone to make changes to your live account.
Get a Professional GoHighLevel Audit in the UK
If you've inherited a GoHighLevel account and don't know where to begin, GHL Experts provides structured account audits for UK businesses and marketing agencies.
The GoHighLevel account audit reviews nine key areas, including CRM structure, workflows, deliverability, integrations, reporting and compliance configuration.
The service costs £395 excluding VAT and typically takes 3–5 working days from receiving access.
The audit is read-only, meaning your account is reviewed without implementing changes. You receive a written report with prioritised findings and a walkthrough of the recommendations.
If you subsequently commission implementation work from GHL Experts, the audit fee is credited towards that work.
You can also keep the report and use another provider for the repairs.
For a business considering a complete CRM rebuild, that clarity can make a substantial difference to the decision.
Frequently Asked Questions
Can you fix a GoHighLevel account built by another agency?
Yes. GoHighLevel accounts can be reviewed and repaired by appropriately authorised specialists who didn't build the original configuration. The main challenge is understanding how existing workflows, fields, pipelines and integrations depend on each other. A structured audit helps identify those relationships before changes are made.
How do I know if my GoHighLevel account is broken?
Common warning signs include missed enquiries, failed follow-ups, unexpected duplicate messages, unreliable appointment booking and inaccurate pipeline reporting. However, these symptoms don't necessarily mean the entire account is faulty. Testing a real customer journey and reviewing workflow history can help identify the specific problem.
Can I audit my GoHighLevel account without changing anything?
Many checks can be completed using account settings, existing records, workflow logs and read-only access. Some end-to-end tests may create contacts, appointments or messages, so these require separate authorisation and controlled conditions. A professional read-only audit should not make unapproved production changes.
What happens if the previous GoHighLevel agency still owns my account?
First, confirm your contractual arrangements and the level of access you actually have. If you need to move the sub-account, HighLevel supports authorised transfers between eligible agencies. The releasing and receiving parties must coordinate the process, and some external services or communications configurations may need additional migration steps.
Will creating a new GoHighLevel snapshot fix a messy account?
Not necessarily. A snapshot copies selected reusable configuration assets; it doesn't diagnose broken workflows or automatically repair poor CRM design. Loading another snapshot into an already complicated account may introduce additional workflows, tags and dependencies. Review the existing configuration and any potential conflicts first.
How long does a GoHighLevel account audit take?
The time depends on account size, complexity, workflow volume and the scope of the review. A relatively straightforward account may take less time than one with numerous integrations and undocumented automations. GHL Experts typically delivers its structured audit in three to five working days after receiving access.
How much does a GoHighLevel account audit cost?
Professional audit costs vary by provider and scope. GHL Experts advertises a fixed-price account audit at £395 excluding VAT, with a written report and recommendations. Implementation is separate, allowing you to review the findings before deciding what work to authorise.
Should I delete unused GoHighLevel workflows?
Not until you've confirmed they are genuinely unused. A workflow with little recent activity may still support occasional bookings, renewals or other important events. Review its triggers, dependencies and relevant history, then follow a controlled decommissioning process with appropriate approval.
Final Thoughts: Understand the Account Before You Rebuild It
Inheriting a poorly maintained GoHighLevel account doesn't mean you have to start again.
The problem may be an outdated trigger, duplicated automation, incorrect field mapping or disconnected integration. These are the kinds of issues that can often be corrected without replacing everything around them.
Start by securing access, understanding the existing setup and tracing the journeys that matter most to your business. Use actual records and logs to identify failures, then make controlled improvements in order of commercial importance.
If the account genuinely needs restructuring, you'll be able to make that decision with evidence rather than guesswork.
Not sure what's broken in your GoHighLevel account?
Request a GoHighLevel Account Audit from GHL Experts to identify the problems, understand your options and get a clear plan for what to fix first.
