Skip to content

How to Audit HubSpot Usage and Unused Features

Charlotte Mortimer
Charlotte Mortimer

Most HubSpot portals accumulate features faster than teams can adopt them. Hubs get added during a renewal conversation, workflows get built for a campaign that ran once, and properties multiply without anyone reviewing whether they still serve a purpose. Before long, the portal is cluttered and the monthly bill is harder to justify.

A HubSpot audit helps you step back and answer a simple question: is your portal supporting the way your business actually works?

This guide walks you through a practical approach to reviewing usage, identifying unused features and deciding what to keep, improve or retire. It is written for UK SME owners, operations leads and sales and marketing leaders who want honest answers before spending more.

Quick answer

  • A usage audit shows which parts of your portal your team relies on and which sit unused.
  • Starting with your core business processes prevents the audit from becoming an overwhelming feature checklist.
  • Reviewing active users and access rights often reveals paid licences and seats you can reclaim immediately.
  • Data quality and reporting use are two of the most reliable indicators of whether your team trusts HubSpot.
  • Hubflow Consulting builds portal audits around prioritised, practical next steps rather than abstract scores or dashboards.

What Should a HubSpot Usage Audit Tell You?

A usage audit is not a health score for the sake of a number. It should give you a clear, honest picture of three things: what your team is actually using, what is costing you money without contributing to the business, and where the practical opportunities sit.

Good audits answer specific questions: which pipelines are active, which workflows still fire, which reports anyone opens, and which properties contain reliable data. If your audit cannot answer these, it is too high-level to be useful.

The goal is a prioritised list of actions, not a 40-page document. You want to know what to fix first, what to switch off and what to leave alone. Everything else is detail you can address in stages.

Why Audit Before You Buy or Build More?

It is common for teams to request a new Hub, a higher tier or a custom integration before reviewing what they already have. In many cases, the features they need are already available but either misconfigured or never properly set up.

Running a usage audit before any purchasing decision protects your budget. It also gives you a realistic baseline for measuring whether future investment delivers a return. Without that baseline, you are guessing.

How to Start a HubSpot Audit with Core Processes

The fastest way to lose focus during an audit is to open every settings page and start cataloguing features. Instead, begin with your core business processes: how does a lead arrive, how does a deal progress, and how does a customer get looked after?

Map those three or four processes in plain English first. Then trace each one through HubSpot. Note where the process lives in the portal, where it breaks, and where the team reverts to spreadsheets, emails or memory.

Identify Which Processes HubSpot Should Support

Not every process needs to live in HubSpot. Some are better handled elsewhere, and forcing them into the CRM creates complexity without value. If you are still working out which Hubs you need, the Hub Explorer is a useful starting point.

Be honest about which processes genuinely benefit from being in the platform and which were added because someone assumed they should be.

A practical test: if removing a process from HubSpot would not change how the team works, it probably does not belong there. Focus your audit energy on the processes that matter.

Map the Gap Between Process and Portal

Once you know which processes should be in HubSpot, compare the current setup against the reality. Check whether pipeline stages reflect how deals actually move, whether lifecycle stages are aligned with how marketing qualifies contacts, and whether handovers between teams happen inside the system or outside it.

These gaps are where the value sits. Closing them is usually more useful than adding new tools.

How to Review Active Users, Access and Ownership

User adoption is one of the clearest signals of portal health. According to research compiled by Enable Services, only 37% of sales reps say their company fully uses its CRM. Log into your HubSpot account settings and review your user list. Look at last login dates, activity logs and the seats each person holds.

You will often find users who have not logged in for months but still occupy paid seats. You may also find team members with super-admin permissions who only need basic access, or former employees whose accounts were never removed.

Check Seat Allocation Against Actual Use

HubSpot's pricing model now ties certain features to specific seat types. If you are paying for Sales Hub Professional seats, check whether every seat holder is using the features that require that tier. Hubflow's licence checker can help you compare what you are paying for against what you need.

Reassigning seats based on actual usage can reduce costs without losing any capability your team relies on.

Review Ownership of Records, Pipelines and Dashboards

Ownership matters for reporting accuracy and accountability. Review who owns deals, contacts and tickets. Check whether pipeline ownership reflects current team structure. Look at who created key dashboards and whether those people are still in the business.

Orphaned records and reports owned by departed team members are a common source of confusion. Reassigning ownership during an audit prevents data from silently falling out of view.

How to Review Tools, Automation and Connected Processes

This is where most portals carry the most dead weight. Open your workflows list and sort by status. Check how many are active, how many have enrolled contacts in the last 90 days, and how many were built for a one-off campaign and never switched off.

Do the same for sequences, forms, landing pages and email templates. The pattern is usually the same: a handful of active assets surrounded by dozens of dormant ones.

Audit Your Workflows by Purpose and Performance

Group your active workflows by purpose: lifecycle management, lead routing, internal notifications, deal automation, data hygiene. For each group, ask whether the workflow still reflects the current process and whether it is firing correctly.

Workflows that trigger but produce no meaningful outcome are worse than inactive ones. They clutter activity logs, send irrelevant notifications and make it harder to trust the system. If a workflow does not serve a clear business need, switch it off.

Check Integrations and Connected Apps

Open your connected apps list in HubSpot settings. For each integration, check whether it is syncing data correctly, whether the app is still in use and whether the sync direction is appropriate.

Unused integrations create risk. They can push stale data into your CRM or pull records into systems your team no longer monitors. Disconnecting unused apps is a quick win that improves data reliability and reduces automation complexity.

Assess Whether Your Automation Reflects Real Business Rules

Good automation should mirror the way your team actually works. If your automation has drifted from the underlying process, it creates friction rather than removing it. The audit is a good moment to ask: would we build this the same way today? If the answer is no, document what needs to change and add it to the prioritised plan.

How to Review Data Quality and Reporting Use

Reporting is only as reliable as the data behind it. If your team does not trust the numbers on a dashboard, they will stop looking at it. The audit should examine both the data feeding your reports and whether anyone is using those reports to make decisions.

Assess Property Hygiene and Data Completeness

Start with your most important properties: lifecycle stage, deal stage, company size, lead source and any custom properties tied to your reporting. Check completion rates. If a key property is empty on more than half your records, the reports built on it are unreliable.

Look for duplicate properties, inconsistent naming and fields created during a past project that no one uses. A clean property set makes everything else in HubSpot work better, from reporting to segmentation to workflow enrolment criteria.

Review Which Reports and Dashboards Are Actually Used

HubSpot lets you see when a dashboard was last viewed. Review your dashboard list and note which ones have been opened in the past month. Dashboards that nobody checks are not adding value, regardless of how carefully they were built.

For the dashboards your team does use, check whether the reports answer a real business question. A report that shows total contacts created is less useful than one showing qualified leads by source. The audit is a good time to retire vanity metrics and replace them with reporting you can trust.

Check Contact, Company and Deal Data for Duplicates

Duplicates erode confidence in the CRM. Research from Datalere's 2025 Customer Insight Report found that up to 20% of CRM data is duplicated due to poor integration. HubSpot has built-in duplicate management tools, but many teams never run them.

During your audit, check for duplicate contacts, companies and deals. Merge where possible and investigate the source of duplication so you can prevent it recurring.

If your data migration brought duplicates in from a previous system, that is worth addressing properly rather than managing around it indefinitely.

How to Decide What to Keep, Improve or Retire

By this stage, you should have a clear picture of what is active, what is dormant and what is causing problems. The next step is to sort your findings into three categories.

Keep: Features and Processes That Work Well

Identify the parts of your portal that your team uses regularly and that support a genuine business process. These are your foundations. Protect them, document them and make sure the team understands why they matter.

Improve: Features That Have Value but Need Attention

This category usually holds the most opportunity. It includes workflows that need updating, reports that need better data, pipelines that need restructuring and tools that the team would use if they understood them properly.

Prioritise improvements by impact and effort. A workflow fix that takes an hour and saves the sales team 20 minutes a day is a better starting point than a reporting project that requires a month of data cleansing. Practical training often unlocks value from features that are already configured but underused.

Retire: Features That No Longer Serve a Purpose

Switching things off takes a bit of confidence, but dormant features create noise. Inactive workflows, unused properties, abandoned forms and disconnected integrations all make the portal harder to manage and harder to trust.

Document what you are retiring and why. If a feature was turned off for a good reason, the next person who finds it should understand the decision without needing to reconstruct the context.

How to Build a Prioritised Action Plan from Your Audit

A list of findings is not an action plan. Group your audit outcomes by theme: data quality, automation, reporting, user management and licensing. Then assign a priority to each based on business impact and the effort involved.

Quick wins go first. These are changes you can make in hours that produce an immediate improvement: reclaiming unused seats, merging duplicate records, switching off broken workflows or fixing a misconfigured pipeline stage.

Plan Improvements in Phases

Larger improvements should be planned in phases rather than attempted all at once. A phased approach lets you validate each change before moving to the next. It also reduces the risk of disrupting active processes while fixing dormant ones.

If you need specialist support for specific phases, a support retainer gives you access to experienced help without committing to a large project. Hubflow Consulting works this way with many UK SMEs: agree the priorities, then work through them at a sensible pace.

Set a Review Cadence to Prevent Drift

An audit is a point-in-time exercise. Without a regular review cadence, the same problems will return. Set a quarterly check on key indicators: active users, workflow performance, data completeness and reporting use. This does not need to be a full audit. A focused 30-minute review against the original action plan is enough to catch drift early.

Common Mistakes to Avoid During a HubSpot Portal Audit

Some audit approaches create more confusion than clarity. Knowing what to avoid is as useful as knowing what to do.

Do Not Treat the Audit as a Feature Catalogue

Listing every feature in your portal and ticking boxes does not tell you anything useful. Focus on the features connected to real processes and real users. Everything else is context, not a priority.

Do Not Audit Without Involving the People Who Use the System

The team using HubSpot every day knows where the friction is. An audit run entirely from the admin panel misses the operational reality. Speak to sales reps, marketing coordinators and service agents. Their perspective is as valuable as the data.

Do Not Try to Fix Everything at Once

Audit findings look overwhelming if you treat them as a single to-do list. Prioritise ruthlessly. Fixing three things well is more valuable than starting ten and finishing none.

When to Bring in Outside Help for a HubSpot Audit

You can run a useful audit internally if you have someone with the time and the HubSpot knowledge to do it properly. For many SMEs, that person does not exist. The operations lead is busy, the marketing manager is focused on campaigns and the business owner has other priorities.

An independent consultant brings a fresh perspective, a structured approach and the technical knowledge to spot issues that an internal team might miss. Hubflow Consulting delivers HubSpot audits focused on what is working, what is not and what to do next: a prioritised plan, not an abstract assessment.

If you are not sure where you stand, Hubflow's free 60-second health check gives you an instant portal health score with tailored next steps. No email required, and no obligation.

FAQs About HubSpot Usage Audits

What is a HubSpot portal audit?

A HubSpot portal audit is a structured review of your CRM setup, covering data quality, automation, reporting, user adoption and licensing. Hubflow Consulting delivers audits as a prioritised action plan so you know exactly what to fix first and why it matters for your business.

How often should you audit your HubSpot portal?

A full audit once a year is a sensible starting point. Between audits, a quarterly check on key indicators (active users, workflow performance, data completeness) helps catch problems before they compound. This regular review prevents the portal from drifting back into disrepair.

Can a HubSpot audit help reduce costs?

Yes. Audits often reveal unused seats, unnecessary tier upgrades and redundant integrations. Hubflow Consulting regularly helps UK SMEs identify licence savings during audits, reclaiming budget that can be redirected to improvements that genuinely support the business.

What is the difference between a HubSpot audit and a health check?

A health check is typically a quick, high-level review that flags obvious issues. An audit goes deeper: it traces processes through the portal, examines data quality, reviews automation logic and produces a detailed action plan. Hubflow offers both, starting with a free 60-second health check to help you decide whether a full audit is the right next step.

Do you need HubSpot expertise to audit your own portal?

You can make progress with a structured approach and basic admin access. This guide gives you the framework. For deeper technical issues (workflow logic, integration conflicts, data architecture) or if your team lacks the time, bringing in a specialist like Hubflow Consulting will save time and surface problems that are harder to spot from the inside.

What should a HubSpot audit report include?

A good audit report includes findings grouped by theme (data, automation, reporting, users, licensing), a priority rating for each finding and a recommended next step. It should be clear enough for a business owner to read and act on, not just a technical document for the person managing the portal.

Share this post