HubSpot portal audit checklist
A HubSpot portal audit checks seven areas: account settings, users and integrations; CRM data and properties; Sales Hub; Marketing Hub; Service Hub; workflows and automation; and reporting. Score every finding by severity, from critical (leads or revenue are lost now) to low (clutter), and fix in that order: anything that loses or misroutes leads first, then access, the data model, definitions, automation conflicts and reporting, and clean-up last. Most portals need a ranked fix list, not a rebuild. Checkpoint GTM, a Berlin RevOps consultancy and HubSpot Platinum Partner with 80+ implementations, uses this checklist before it touches a portal. Run it yourself, or bring us what you find.
How do you score what a HubSpot audit finds?
Give every finding one severity before you fix anything. Severity is about what the problem costs the business, not how ugly it looks in the portal. A messy property list is low; one broken form that stops leads reaching sales is critical.
| Severity | What it means | Typical finding | When to fix |
|---|---|---|---|
| Critical | Leads, revenue or customer data are being lost or exposed right now | A form that no longer creates contacts, routing that leaves new leads without an owner, a former employee who still has access | This week, before anything else |
| High | The numbers leadership uses are wrong, or a team works around the CRM | Open deals with close dates in the past, lifecycle stages nobody follows, two workflows writing to the same property | This month, in a planned fix |
| Medium | Work is slower or harder than it should be, but the data is still usable | Duplicate contacts and companies, free-text fields that should be dropdowns, contacts without a company | This quarter |
| Low | Clutter that makes the portal harder to use and maintain | Unused properties, old lists, inactive workflows, templates and dashboards nobody opens | Batch it into a clean-up, after the rest |
The severity levels are our own working scale for audit findings, not a HubSpot standard. Adjust the examples to your motion: for a team that runs on inbound, a broken form is always critical.
How do you run a HubSpot portal audit?
Start with the business, not the settings. Write down the processes the portal has to support: how a lead arrives and gets routed, how a deal moves through the pipeline, how a customer is handed to onboarding or support, and which numbers leadership reviews every week. Every check below is measured against those processes. A property nobody uses for any of them is clutter, however well it is named.
Then work through the portal one area at a time with a super admin login, and keep one list of findings with the area, what you found, the severity and an owner. Look at real records, not just settings: open ten recent leads, ten open deals and ten closed tickets and check whether they tell the story they should.
Audit only the hubs you pay for. If you run Sales Hub and Marketing Hub, skip the Service Hub list. The CRM data, workflow and reporting checks apply to every portal.
Account, users and integrations
Check who can get in and what is connected before you look at the data. Findings here are often critical because they are security or data-loss risks.
- Users who left. Every former employee and agency user is deactivated, and their records, deals and tasks are reassigned. Usually critical.
- Super admins and permissions. Only a few people are super admins, and permission sets match roles: reps cannot delete records or export the whole database unless they need to. Usually high.
- Paid seats. Paid Sales Hub and Service Hub seats sit with people who use those tools, not with former staff or occasional viewers. Usually medium.
- Connected apps and integrations. Every connected app and private app has a known owner and a purpose, apps nobody can explain are removed, and each sync writes only to the fields it should. Usually high.
- Tracking and domains. The tracking code runs on every site and domain you own, and email sending domains are authenticated. Usually high.
CRM data and properties (every hub)
This is where most portals drift. Check the fields your routing, scoring and reporting depend on first, then the rest.
- Critical fields. The fields your processes need, such as owner, lifecycle stage, country and lead source, are filled on the records that need them, and are required where they are created. Usually high.
- Duplicates. Duplicate contacts and companies are reviewed and merged with written rules for which record and which values win, and the source that creates them, often an import or an integration, is fixed. Usually medium.
- Property sprawl. No custom properties that copy a default property, no free text where a dropdown belongs, and every property has a description and an owner. Check where a property is used before you delete it. Usually low to medium.
- Lifecycle stage and lead status. Each value has one written definition, the stages move in one direction, and workflows set them the same way everywhere. Usually high.
- Associations. Contacts are linked to their company, and deals and tickets to the right contacts and company. Records without associations break account-level reporting. Usually medium.
- Owners. No open records without an owner or owned by an inactive user. Usually high for leads and open deals, low for old records.
Sales Hub
Sales Hub findings show up in the forecast. Check the pipeline against how your team really sells.
- Pipelines and deal stages. Each stage has an exit criterion the team can repeat, and there are no stages that nobody uses or that mean the same thing. Usually high.
- Required fields per stage. The fields the forecast needs, such as amount, close date and next step, are required when a deal enters the stage that needs them. Usually high.
- Stale deals. No open deals with close dates in the past or with no activity in months; they inflate the pipeline and the forecast. Usually high.
- Activity logging. Emails, calls and meetings are logged automatically where possible, so a deal record shows what really happened. Usually medium.
- Sequences and templates. Active sequences have owners and current copy, and old templates are archived. Usually low.
Marketing Hub
Marketing Hub findings decide whether leads reach sales and whether you can say where they came from.
- Forms. Every live form creates or updates contacts, maps its fields to the right properties and uses dropdowns for fields such as country. Test each one. A broken form is critical.
- Source and attribution. UTM parameters are used consistently and the source properties are reliable enough to report on. Usually high.
- Marketing contacts and lists. Only contacts you actually market to are set as marketing contacts, which drives your HubSpot bill, and old lists and segments are cleaned out. Usually medium.
- Email health. Subscription types match what people signed up for, and bounced and unengaged contacts are excluded from sends. Usually high.
- Lead scoring and handoff. The score is used by someone, its criteria still match your ideal customer profile, and the handoff to sales has a written trigger and owner. Usually high.
Service Hub
Service Hub findings show up in renewals. Check that every request lands with an owner and that support data reaches the account.
- Ticket pipelines and statuses. Statuses match the real support process, and no tickets sit open without an owner. Usually high.
- Routing and inboxes. Every channel, such as email, chat and forms, creates a ticket that reaches the right team. Usually critical if requests are lost.
- Associations to the account. Tickets are linked to the right contact and company, so the account team sees support history before a renewal. Usually medium.
- Feedback and knowledge base. Surveys feed a property someone reviews, and help articles are current. Usually low.
Workflows and automation (including Data Hub, formerly Operations Hub)
Automation is where hidden conflicts live. List every active workflow before you change one.
- Workflow inventory. Every active workflow has an owner and a one-line purpose, and workflows nobody can explain are reviewed and switched off. Usually medium.
- Conflicts. No two workflows write to the same property, such as owner or lifecycle stage, with different logic. Usually high.
- Errors. Workflow errors and failed actions are reviewed, not left to pile up. Usually high.
- Enrolment rules. Triggers and re-enrolment settings do what the owner thinks: no record enrolled twice by accident, no record silently skipped. Usually medium.
- Data sync and custom code. Syncs with other tools write in the agreed direction, and any custom code actions keep secrets out of the code and have an owner. Usually high.
Reporting and dashboards
Reporting is the last check because it depends on everything above.
- One definition per metric. MQL, SQL, pipeline and win rate each have one written definition, and every report uses it. Usually high.
- Dashboards in use. Each dashboard has an owner and a meeting it serves; the ones nobody opens are archived. Usually low.
- The numbers reconcile. Pipeline and revenue in HubSpot match finance and what leadership reports. Usually high.
- No shadow spreadsheets. If a team keeps its own spreadsheet, find out which number HubSpot cannot give it. Usually medium.
What do we fix first after a HubSpot audit?
We audit first and fix in order of revenue impact. On most portals, that order looks like this:
- Anything that loses or misroutes leads now. Broken forms, routing gaps, workflow errors on the lead path.
- Access and integrations. Users who left, too many super admins, connected apps nobody owns.
- The data model and critical fields. Required fields, dropdowns instead of free text, and duplicates stopped at the source.
- Definitions. Lifecycle stages, lead status and deal stages, each with one written meaning.
- Automation conflicts. One workflow per property decision, and dead workflows switched off.
- Reporting. Dashboards rebuilt on the fixed definitions, then the clean-up of unused properties, lists and templates.
Measure before and after: pick a few numbers, such as time from form fill to first sales touch and the share of open deals with every required field filled, and check them at the start and again after the fixes. If the audit shows that your data model cannot represent how you sell, a fix list is not enough. Our article on when a HubSpot portal needs a rebuild has the test we use.
Where does Checkpoint fit, and who are we not right for?
Checkpoint GTM is a Berlin-based RevOps consultancy and HubSpot Platinum Partner with 80+ implementations. When a portal runs but nobody trusts it, we audit first, fix in order of revenue impact, and can stay on as a retainer so it does not drift back.
Good fit
- Seed to Series B B2B SaaS teams whose HubSpot portal grew without an owner and whose data nobody trusts
- Teams that want the fixes built in their portal, documented and handed over, not only a report
- Companies that want delivery in English, German, Italian, French or Spanish
Not the right fit
- You only want a scored report to file: we fix what we find
- Your portal is new and simple: run this checklist yourself first
- Your CRM is not HubSpot: start with our RevOps and GTM process audit instead
HubSpot portal audit: questions, answered
What is a HubSpot portal audit?
A HubSpot portal audit is a structured review of a HubSpot account: users and integrations, CRM data and properties, each hub in use, workflows and reporting. The output is a list of findings scored by severity and a fix order, so you know what is losing leads or distorting the numbers and what is only clutter.
What should a HubSpot audit checklist include?
Seven areas: account settings, users and integrations; CRM data and properties; Sales Hub pipelines and deal stages; Marketing Hub forms, attribution, lists and email health; Service Hub ticket pipelines and routing; workflows and automation, including Data Hub syncs; and reporting definitions and dashboards. Audit only the hubs you pay for.
How do you prioritise HubSpot audit findings?
Score each finding by what it costs the business. Critical means leads, revenue or data are lost or exposed now; high means the numbers leadership uses are wrong; medium slows work down; low is clutter. Fix critical findings first, then access, the data model, definitions, automation conflicts and reporting, and clean-up last.
How much does a HubSpot audit cost with Checkpoint GTM?
We do not publish a separate price for an audit, and we scope before quoting. A portal that runs but nobody trusts usually gets an audit and then an optimisation retainer, which runs €6K–€25K per month. A full rebuild is scoped like an implementation: a standard Sales Hub and Marketing Hub implementation is €15K–€50K over 6–10 weeks. All prices in EUR, excl. VAT. You can run this checklist yourself for free.
How often should you audit your HubSpot portal?
At least once a year, and after any CRM migration, merger of databases, new hub, large import or change of RevOps owner. Between audits, a short quarterly review in which every property and workflow has a named owner keeps the portal from drifting.
Should we fix our HubSpot portal or rebuild it?
Fix it in place unless the audit shows a structural problem: the data model cannot represent how you sell, the records are so unreliable that cleaning costs more than a controlled migration, or a migration was started and never finished. Most portals have a drift problem, not a build problem, and need a ranked fix list.
Can we audit HubSpot ourselves?
Yes. You need a super admin login, a list of the processes the portal must support, and time to look at real records, not just settings. This checklist covers what to check. An outside partner helps most when nobody inside knows why the workflows and properties exist, or when the fixes need more hours than your team has.
What do you fix first after a HubSpot audit?
Anything that loses or misroutes leads now, such as broken forms, routing gaps or workflow errors. Then access and integrations, the data model and critical fields, the definitions of lifecycle and deal stages, automation conflicts, and reporting. Clean-up of unused properties and lists comes last.
Want a second pair of eyes on your portal?
Bring the findings from this checklist, or just tell us where HubSpot hurts. In a 30-minute call we tell you what we would fix first and whether your portal needs a fix list or a rebuild.
Book a call