What is a HubSpot audit?
A HubSpot audit is a structured review of a portal's access, data, pipelines, automation, integrations and reporting, checked against how the team actually sells and services. It ends with written findings: what works, what is broken, what each problem costs, and a prioritized list of fixes.
This checklist is for whoever inherited a portal and does not trust it yet. It follows the order we use on our HubSpot audits: start with access, because everything else depends on who can change what, and finish with a plan rather than a list of complaints.
- 01 AccessUsers, seats, permissions
- 02 DataDuplicates, blanks, stale records
- 03 PipelinesStages against how deals close
- 04 AutomationOwners, triggers, conflicts
- 05 IntegrationsWhat writes to HubSpot
- 06 ReportingDashboards leadership trusts
- 07 PlanQuick wins, structural fixes, stop doing
When does a HubSpot portal need an audit?
Audit when the numbers stop being believed. Typical signs are reports exported to a spreadsheet before anyone acts on them, reps skipping pipeline stages, dashboards that disagree, automation nobody can explain, and Professional or Enterprise licenses being used like a basic contact database.
- You inherited the portal from someone who has left.
- Two reports show different numbers for the same thing.
- A migration, rebuild or new hub is coming and you need to know what to keep.
- Reps keep their own spreadsheets alongside HubSpot.
Step 1: Who has access, and what can they change?
Start with users and permissions. List every user, their seat type, their permission set and when they last logged in. Check who is a super admin, who can export data, who can delete records, and who can edit properties and workflows. Over-broad access is how most portals drift.
- Super admins limited to the people who genuinely own the portal.
- Export and bulk-delete rights reviewed by role.
- Departed users deactivated and their records reassigned.
- Sensitive properties (revenue, personal data) restricted where your tier allows.
Step 2: How good is the data?
Measure data quality by object. For contacts, companies and deals, check duplicates, blank required fields, inconsistent values and stale records. Then review properties: which are used, which duplicate each other, and which nobody has filled in for a long time. Record counts, not impressions, so you can show progress later.
Duplicates and incomplete records
Look for the same person or company stored more than once, records missing the fields routing and reporting depend on, and values entered in several formats (country names, phone numbers, job titles). Our cleanup and deduplication system covers what to do with them.
Unused and duplicate properties
Export the property list for each object with its fill rate. Properties that are empty, abandoned, or duplicates of another property ("Lead Source", "Lead source 2", "Original source (old)") are the first candidates for consolidation.
Step 3: Do pipelines and lifecycle stages match how you sell?
Compare each deal pipeline with how deals really close. Check that every stage has clear exit criteria, that close dates and amounts are kept up to date, and that lifecycle stages and lead statuses are defined and used consistently. Stages reps skip are a design problem, not a discipline problem.
- Stage-to-stage conversion and time in stage reviewed for each pipeline.
- Deals with past close dates or no amount counted.
- Lifecycle stage and lead status used for different jobs. See HubSpot lifecycle stages explained.
Step 4: What is the automation actually doing?
List every active workflow, sequence and automated email with its owner, trigger and purpose. Flag workflows with no owner, workflows that conflict (two rules setting the same property), and workflows with high error or enrollment rates on bad records. Anything nobody can explain gets switched off in a controlled way, not deleted.
- Every workflow has a named owner and a one-line purpose.
- Conflicting property updates identified.
- Workflow errors and failed actions reviewed.
Step 5: Which integrations write to HubSpot?
List every connected app and sync, what it reads and writes, and which system owns each shared field. Most "random" data changes come from two systems overwriting the same property. Check sync error logs and whether anyone is alerted when a sync fails.
Our guide to integration governance and monitoring sets out field ownership and alerting.
Not sure what is wrong yet? Start with a paid audit and get the findings in writing.
Step 6: Which reports does leadership trust?
Find the handful of dashboards that drive real decisions and check each one against the data underneath it. A report that needs a spreadsheet check is pointing at a data or definition problem upstream. Note which reports nobody opens; they can usually go.
Step 7: How do you turn audit findings into a plan?
Score each finding by impact and effort, then group them: quick wins your team can do this week, structural fixes that need design first, and things to stop doing. Write each one as a problem, its cost, and the recommended fix, so the plan can be acted on without the person who wrote it.
| Group | Typical examples |
|---|---|
| Quick wins | Deactivate departed users, archive empty properties, fix a broken form mapping |
| Structural fixes | Redesign a pipeline, consolidate duplicate properties, define lifecycle criteria |
| Stop doing | Unowned workflows, duplicate imports, manual list building |
The HubSpot audit checklist
Key takeaway: An audit is only finished when it produces a plan someone can act on. Count the problems, write down what each one costs, and fix them in priority order.
Frequently asked questions
How long does a HubSpot audit take?
It depends on the size of the portal, the number of hubs and integrations, and how much automation has built up. On our projects, audit and architecture together typically take one to two weeks. A focused audit of a single area, such as data quality, can be shorter.
What do I get at the end of a HubSpot audit?
A written findings document: what is working, what is broken, and what each problem is costing in time or trust, with recommendations ordered by priority. A good audit ends with a plan you can act on yourself or hand to a partner.
Does audit work carry into a rebuild?
It should. The audit is the discovery stage of a rebuild, so the findings become the brief for the architecture. When we run an audit and the client goes ahead with the build, the audit work carries into it rather than being repeated.
How often should a HubSpot portal be audited?
Run a full audit when you inherit a portal, before a migration or rebuild, and when reports start to disagree. Between those, a short quarterly review of duplicates, unused properties, failing workflows and sync errors catches most problems before they grow.
Sources
HubSpot documentation behind the feature and tier notes above, checked October 2026. HubSpot changes features and tiers often, so check your own portal too.

