HubSpot audit checklist: what to check, and in what order
What to check in your HubSpot portal, based on how we run client audits, and what you should have when you finish.
Print it out and tick off each step as you go, or keep it open next to you while you work.
Table of contents
Super Admin access (or a partner seat), and a short talk with your sales and marketing users about what slows them down in HubSpot.
If nobody has checked your HubSpot portal in a while, you're probably making pipeline and marketing decisions on numbers you can't fully trust. You may also be paying for hubs and seats nobody uses. This checklist shows you how to find out and what to fix first, based on how we run client audits. It's written for the HubSpot admin or RevOps lead who runs the audit, and for a CRO or CMO who just inherited the portal. If you already know the one problem you need to fix, skip to the step that covers it.
The audit runs in three parts:
- Steps 1 to 3 happen before you open HubSpot: set the objective and map how the team is supposed to work, then get the right access.
- Steps 4 to 11 are the HubSpot system checks: subscriptions and users, data quality, duplicates, deals, unused tools, integrations, workflows and marketing assets.
- Steps 12 to 14 review the findings: check each pain point against the evidence, then work out the cause with the team and write it up.
By the end you'll have a readout of the portal and a short list of critical findings, each with a question for the team. If you inherited the portal recently, read how to evaluate an inherited HubSpot account alongside this one. For the bigger picture on HubSpot audits, see our HubSpot audit article.
Before you start
You need Super Admin access (or a partner seat), and a short talk with your sales and marketing users about what slows them down in HubSpot. Step 3 covers what to do if you aren't a Super Admin.
Before you open HubSpot
Start with the business, not the portal. If you go straight into HubSpot without knowing what the sales and marketing teams actually do, you'll misread what you find. A pile of records on an object the team stopped using years ago looks like a problem, until someone tells you why it's there.
1. Decide what the audit is for
When this step is done, you'll have a short written goal for the audit, plus a list of pain points with the name of the person who raised each one.
An audit with no objective gives you a readout of the system, which helps, but it won't tell you what to fix first. Sit down with the people who use HubSpot every day and find out where it gets in their way.
- Write down the question the audit needs to answer, such as why reps don't trust the pipeline, or where unexplained records are coming from.
- Talk to the main users: sales reps, account managers and the marketing team. Ask what slows them down and what they've stopped using.
- Write each pain point down in your own notes, with who raised it. Write those notes yourself rather than relying on AI notes, so you understand each pain point before you test it later.
- Turn complaints into things you can check. If reps say there are too many fields on the deal record, plan to go through each field and see which ones get used and which could be cut or simplified.
2. Map the processes HubSpot should mirror
When this step is done, you'll have a written map of how the team is supposed to work: each pipeline's stages with their entry and exit criteria, which rules HubSpot actually enforces, and what your team means by a lead and a contact.
You can only judge whether HubSpot is set up well against how the team is supposed to work. The best case is a portal that mirrors the agreed process, with guardrails that keep reps following it.
- List the stages in each pipeline and the entry and exit criteria the team agreed on.
- Note which rules HubSpot enforces (required fields, stage rules) and which exist only on paper.
- Note how marketing uses HubSpot day to day, so you know which marketing tools to expect in use.
- Agree on what a lead is and what a contact is, especially if HubSpot is connected to Salesforce, where the two words mean different things. Our recommendation, and the setup we've seen work best, is to stop using the Lead object in Salesforce and track early interest as a pre-pipeline opportunity. Our guide to Salesforce leads vs contacts explains why.
3. Confirm your access
When this step is done, you'll have Super Admin access (or a partner seat) for as long as the audit runs, confirmed by opening every hub, settings page and record type.
If you aren't a Super Admin, you probably won't see everything an audit needs. Several tools used below are restricted. The audit log needs Super Admin (see the FAQ below). The data quality and duplicate tools need Super Admin, or the data quality tools access permission plus view access to the records. The workflow health page needs Super Admin or workflow permissions.
- Confirm you can open every hub and settings page, and all records.
- If you aren't a Super Admin, ask for that access for the length of the audit. If a HubSpot partner runs the audit for you, a partner seat in your portal gives them enough access.
- Treat the audit as read only. Record what you find, and make changes only after you've walked the team that uses HubSpot through the findings and explained why each change is needed. This matters most when HubSpot syncs with another system, because a change in HubSpot can carry over.
HubSpot system checks
HubSpot has no quick way to query your data the way Salesforce does, so most of these checks mean opening an object, adding filters and writing down the count. Think of it as walking the store: click through the portal the way a rep or a marketer does every day, so you see what they see, then check the settings behind it that nobody sees until something breaks. Write each count and finding down as you go, because they become the readout in step 14.
4. Subscriptions, users and permissions
When this step is done, you'll have a list of every hub you pay for and its tier, with your seat counts, how many Super Admins you have, which inactive users still hold paid seats, and whether users have 2FA turned on.
Start with what you're paying for and who can change things. HubSpot often sells hubs as bundles, so it's common to find a hub on the invoice that the team never opened.
- Open Account & Billing (click your account name in the top right). On the Overview tab, list every hub in the subscription and its tier (Starter, Professional or Enterprise).
- Flag any hub the team doesn't use.
- On the same tab, record your marketing contact tier and how many contacts count as marketing contacts, plus assigned and total seats. On the Subscriptions tab, note each subscription's term and next billing date. If you're near your marketing contact limit, see how to reduce marketing contact volume in HubSpot.
- Compare the team's complaints with the tier. Something they say HubSpot "can't do" may be a feature of a higher tier, and fixing it means upgrading. No setting will change it.
- Count your Super Admins.
- Check who can create properties and change record layouts. In HubSpot's user permissions, these are Edit property settings (Account tab) and Customize record page layout (CRM tab). Those rights should sit with the people who own the system.
- List inactive and deactivated users, and any paid seats still assigned to them.
- Check two-factor authentication. Go to Settings > Security, open the Permissions tab and find the 2FA measure, which needs Super Admin or Security Center access. HubSpot's security health only shows each user's enrollment for some accounts, such as paid accounts in their first 30 days. If yours doesn’t, ask users to confirm. HubSpot already requires 2FA on paid accounts, so the setting to require it for everyone only matters on its free tools.
- Review teams and seat types, and check that seats match people's roles.
Say 10 people on a 15-person team are Super Admins. Any of them can create a field with no documentation or change a page layout, and the sales team logs in one morning to a deal record that looks different. That's the kind of friction this step is meant to catch.
5. Contacts and companies
When this step is done, you'll have a list of the counts from each contact and company check in this step, plus the property issues HubSpot's data quality tools flag.
This is the data health pass on your main objects. Work through each filter and write down the count.
- Total contacts.
- Contacts missing an email address or a name.
- Contacts with no associated company (orphan contacts), so there's no way to tell where they work.
- Contacts whose owner is inactive or missing. An inactive owner is one of the bigger data quality problems we find, because nobody is working those records and they drop out of assignment and reporting.
- Total companies.
- Companies with no contacts, and companies with no deals. A few of these is normal. If most of the database looks like this, you may be storing companies you don't need.
- Companies missing industry, website or owner. Without industry, you can't analyze who your customers are or report by segment.
- Open HubSpot's data quality tools (Data Management > Data Quality) and review the property issues it lists: duplicate, empty and unused properties.
HubSpot's data quality tools are available from Starter up on most hubs, but Smart CRM and Revenue Hub need Professional or Enterprise, and some features need additional subscriptions.
6. Duplicates
When this step is done, you'll have the number of duplicate pairs for contacts and for companies, a few example pairs saved as evidence, and a note on whether HubSpot creates companies automatically.
Duplicates are one of the biggest blockers we find in audits. They split a buyer's history across two records and inflate every count you just took.
- Go to CRM > Contacts, click Actions, then Manage duplicates. Note the number of duplicate pairs for each rule.
- Do the same for companies (CRM > Companies > Actions > Manage duplicates).
- Record a few example pairs as evidence. Hold off on merging until the findings are reviewed.
- If HubSpot is connected to Salesforce, check whether HubSpot is set to create and associate companies automatically (Settings > Data Management > Objects > Companies, in the Automation section). HubSpot's documentation warns that turning this on with the Salesforce integration can create duplicate company records. If it's on, record it as a finding and review it with whoever owns the sync before changing anything.
HubSpot's duplicates tool needs a Professional or Enterprise subscription to Marketing Hub, Sales Hub, Service Hub, Data Hub or Smart CRM. Merging in bulk needs Data Hub Professional or Enterprise. You also need data quality tools access plus edit rights on all contacts or companies, or Super Admin. When you're ready to fix them, our CRM deduplication playbook covers the cleanup.
7. Deals and pipeline health
When this step is done, you'll have a list of the counts from each deal check in this step, plus the pipeline stages that don't match the criteria you mapped in step 2.
This is the most pressing part of the audit. It tells you whether the pipeline is healthy and whether the numbers in it can be trusted for forecasting. Your pipeline is only as honest as the people updating it. When updating HubSpot feels like extra work on top of selling, deal details stay in reps' heads and never make it into the system, and the forecast suffers.
- Compare each pipeline's stages with the stage criteria you mapped in step 2. Note stages that don't match how the team sells, and criteria that exist on paper but aren't enforced in HubSpot.
- Count deals in each pipeline. Look for pipelines that could be merged, or a split that doesn't match how you actually sell.
- Deals with no amount.
- Deals with an amount of $0, unless your business really has $0 deals. We often find $0 amounts where the amount field is required, because 0 is the quickest way past it.
- Deals with no deal type.
- Deals with no close date.
- The split between open and closed deals.
- Deals with no associated contacts. Without them you can't trace who was involved on the buyer's side or who the main buyer was. With contacts properly associated, you can analyze your buyers by title and persona.
- Open deals with no activity in more than 60 days. Filter open deals by Last activity date. The right window depends on your sales cycle, but a deal with no activity in 60 days usually shouldn't still be open. Last activity date only counts activity logged on the deal record. A deal can look stale when calls and emails are logged on the contact but not associated with the deal.
- Open deals whose close date has already passed.
- Deals that were moved out of closed won or closed lost and back into the pipeline.
What you find here can point to an adoption problem rather than a setup problem. A pipeline full of stale deals and missing close dates is a question to take back to the sales team in step 13 before you clean anything up. For stale deals, an automated reminder to the deal owner is one way to keep them current once the audit is done.
8. Objects and tools nobody uses
When this step is done, you'll have a list of the tools and objects that are switched on but nobody uses, plus a short note on each custom object saying what it's for and whether it's documented.
HubSpot has a lot of tools a portal can have switched on without anyone using them. Some of them you may be paying for.
- Check whether the team uses Leads, Campaigns and Tasks. Note any that aren't used, flag them for discussion and leave them switched on for now. HubSpot's Leads object (separate from the Salesforce Lead object in step 2) comes with Sales Hub Professional or Enterprise, so it won't appear in every portal.
- For HubSpot Campaigns (Marketing Hub Professional or Enterprise), look for campaigns marked active that the team has stopped using, and any with data issues.
- Check the main sales and service tools: meetings scheduler, goals, target accounts, inboxes and calling. Note which are set up and which are used. Target accounts needs Marketing Hub or Sales Hub Professional or Enterprise, and HubSpot calling needs Sales Hub or Service Hub plus a seat that allows it. The conversations inbox comes with every plan, though more than one inbox needs Professional or Enterprise.
- List every custom object. Custom objects need an Enterprise subscription, so a portal below Enterprise won't have any. For each one, note what it's for, whether it's documented, whether the team knows how to use it, and whether a standard object would do the same job.
Custom objects should only exist when they're really needed. Each one adds complexity, so if a standard object can do the job, the simpler option usually wins. Any custom object you keep needs documentation and a clear process for how the team uses it.
9. Integrations and the Salesforce sync
When this step is done, you'll have a list of every connected app and the records it creates or changes. If you sync with Salesforce, add the sync error counts, your API use and a summary of the sync rules.
Integrations are where a lot of portals break. Companies connect system after system, and then new records keep arriving every day without anyone knowing where they come from. Each unknown source adds more data quality problems on top of the ones you already found. Sync errors can also drop inbound leads without anyone noticing, so sales never follows up.
- Go to Settings > Integrations > Connected Apps and list every connected app.
- Flag any app you don't recognize or the team has stopped using, including ones a previous admin connected years ago that are still running.
- For each active integration, note which records it creates or updates.
If HubSpot is connected to Salesforce, the sync is the center of the integration review. The HubSpot-Salesforce integration needs a Professional or Enterprise subscription to Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub or Smart CRM.
- Go to Settings > Integrations > Connected Apps > Salesforce, then open the Data sync tab and Sync Health. Note the error count for each error type, such as picklist mismatches and property issues. A high error count is a sign the sync isn't healthy.
- In the same Sync Health view, check API call use against your allocation.
- Note which Salesforce user the integration is connected through. HubSpot requires a Salesforce system administrator, and that user's permissions decide what HubSpot can sync, so confirm it still has the access the sync needs.
- On the Data sync tab, review the sync rules for contacts, companies, deals and activities, including any inclusion list that limits which contacts sync.
- Check how new HubSpot contacts arrive in Salesforce, as leads or as contacts, and whether that matches the definitions you agreed in step 2. It's one of the Salesforce integration settings, on the Data sync tab under Contacts > Sync rules, in the Creating and Updating Contacts section.
- List what isn't syncing, such as tickets, and decide whether it should.
- If nobody has reviewed the sync settings in the last year, look for newer options. HubSpot keeps adding settings to the connector and announces them by email and in its community forums. Some give you more visibility in Salesforce into what comes over from HubSpot.
Workflows that change synced fields affect both systems, so step 10 checks them against these sync rules.
10. Workflows
When this step is done, you'll have a count of active, inactive and deleted workflows, plus a list of the workflows the team needs to review or explain.
Workflows build up over time. A workflow set up five or ten years ago for a campaign nobody remembers can still be running and still be touching records. Start with the workflows Health tab (Automation > Workflows > Health). It reports workflows that need review because of issues, and unused workflows, meaning workflows with no enrollments for at least 90 days. The Health tab needs a Professional or Enterprise subscription to Marketing Hub, Sales Hub, Service Hub, Data Hub, Smart CRM or Revenue Hub, plus Super Admin or workflow permissions.
- On the Health tab, note how many workflows need review and how many are unused, then open each list from the bottom of its report.
- Count active, inactive and deleted workflows.
- Flag workflows that conflict with each other.
- Flag active workflows the team can't explain.
- Note temporary workflows, such as a one-off campaign or cleanup, that should have been turned off.
- If HubSpot is connected to Salesforce, list the workflows that change lifecycle stage, record owner or synced fields, and check them against the sync rules from step 9.
When you set up a workflow that isn't meant to last, set a reminder to turn it off and delete it once it's no longer needed. For examples of workflows worth keeping, see our HubSpot workflows guide.
11. Marketing assets
When this step is done, you'll have your email health numbers for the last 30 days, plus a list of marketing assets that are broken or forgotten.
If marketing runs out of HubSpot, check how it's performing, but keep this pass short. The goal here is to find what's broken or forgotten. A full website review is a separate job.
- Go to Marketing > Email and open the email Health tab. Review the score, opens, click-throughs, hard bounces, unsubscribes and spam reports. It shows the past 30 days by default; change the date range to compare with an earlier period. The tab needs view permissions for marketing emails, and shows data only if you sent at least 400 emails in the last 30 days.
- Check landing pages, website pages, blog posts, CTAs and forms: what's published, what's still in draft, and whether anything is broken.
- List the social and ad accounts connected to HubSpot, and whether they're still in use.
Reviewing the findings
The system review tells you what's in HubSpot. This part tells you why, and what to do about it.
12. Check every pain point against the evidence
When this step is done, you'll have a short note for each pain point from step 1 saying what you found, with evidence such as screenshots or example records.
Go back to the pain points you wrote down in step 1.
- Investigate each one directly in HubSpot: the records, workflows, sync logs and settings involved.
- Document what you found for each pain point, with evidence: screenshots, example records, workflow details or a short screen recording.
13. Work out the cause with the team
When this step is done, you'll have one question for the team about each critical finding, with their answers.
It's hard to tell from the system alone whether a finding is a technical problem or a process or adoption problem. Be skeptical, and double-check before you assume anything based on the data.
Some patterns do point somewhere. Lots of unused custom objects or fields often means anyone can create them, which is a process problem. Bad data on its own doesn't tell you the cause. If reps say the deal record has too many fields, check which ones they actually skip before you decide what to remove.
- Write a question for the team about each critical finding.
- Take the questions to the people who use HubSpot every day, and to anyone who knows the portal's history, especially someone who's about to leave.
14. Write up the audit
When this step is done, you'll have the finished audit write-up, ready to walk the team through.
The write-up has three parts:
- A readout of the system: the counts and data you collected in each section.
- Critical findings: the main red flags, such as a high number of duplicates or custom objects nobody documented.
- Questions for the team.
Check that it worked
The audit is done when you can say yes to each of these:
- You understand every finding well enough to explain it to the team.
- Every major object, custom object, hub and setting has been reviewed.
- Every pain point from step 1 has a finding or an explanation.
- Every critical finding has a question for the team.
- No section is left blank or marked "to be done" without a reason.
Run the audit again quarterly, or whenever you take over the portal or the team stops trusting the data.
Frequently asked questions
Does HubSpot have an audit log?
Yes. Go to Settings, then Account Management > Audit Logs. You need Super Admin permissions to see it. It records activity such as logins, security events and changes to records, properties, workflows and settings, but which activity it records depends on your subscription tier. In an inherited portal it's a useful way to see who changed what, and when.
How is a HubSpot audit different from a Salesforce audit?
In Salesforce you can run a query and get the number back. In HubSpot you build each check by hand with views and filters, as in the system checks above, so HubSpot audits take more clicking. HubSpot also needs a bigger marketing review, because more marketing usually runs inside it, and its hubs and tiers mean there's often something switched on, and paid for, that the team never adopted.
Can AI run a HubSpot audit for me?
It can do a lot of the work. An AI assistant connected to HubSpot can handle most of the metadata checks if you give it a checklist and context about your business. What doesn't work is asking it to "audit my system" with no instructions, which produces a long readout of little use. It also shouldn't replace your own notes from the user conversations in step 1. You still need to click through the portal yourself and understand every finding before you act on it.
What to do next
Walk the team through the findings and agree what to fix first, starting with the problems that affect pipeline and reporting. Between audits, a data quality dashboard helps, built from reports such as open deals with past close dates.
If you'd rather have someone else run the audit, RevBlack runs HubSpot and Salesforce audits for B2B teams.







