A HubSpot portal can look functional while operational problems accumulate underneath it.
Contacts still enter the CRM.
Forms still submit.
Workflows still run.
Reports still display numbers.
But over time, teams may start encountering duplicate records, unclear lifecycle stages, conflicting automation, unreliable source data, inconsistent ownership or reports that nobody fully trusts.
The instinct is often to rebuild.
That should usually not be the first step.
A better starting point is to understand what is actually broken, what still works, what should be cleaned up and what genuinely requires redesign.
A HubSpot audit should therefore examine the portal as an operating system rather than as a collection of individual features.
Start with the business process, not the HubSpot settings
Before opening workflow settings or reviewing properties, document the process HubSpot is supposed to support.
For a typical B2B organization, that journey might look like:
Then ask what HubSpot is expected to do at each stage.
Questions may include:
- Who creates the record?
- How does the CRM know where the lead came from?
- When does a lead become qualified?
- Who owns it?
- What automation runs?
- What information does Sales need?
- Which report measures the outcome?
Without that context, an audit can become a long list of configuration observations without establishing whether the portal actually supports the business.
1. Audit the CRM data model
Start with the objects and properties that hold the data.
Review whether important information lives in the right place and whether teams understand what each field means.
Examine areas such as:
- contact properties
- company properties
- deal properties
- custom properties
- field types
- duplicate or overlapping properties
- unused fields
- required business information
- naming conventions
- integration-created properties
A common warning sign is finding several properties that appear to answer the same question.
For example:
- Lead Source
- Original Lead Source
- Marketing Source
- Acquisition Source
- Source Detail
That does not automatically mean those properties are wrong.
But every overlapping property should have a defined purpose.
If nobody can explain which one should be used in reporting, automation or sales handoff, the problem is governance rather than simply CRM clutter.
2. Review duplicate records and identity rules
Duplicate records affect more than database cleanliness.
They can distort:
- contact counts
- attribution
- segmentation
- ownership
- workflow enrollment
- reporting
- sales activity history
A portal audit should go beyond merging records.
Ask why duplicates are entering the CRM.
Potential sources can include:
- forms
- imports
- integrations
- inconsistent company creation
- manual entry
- external systems
Fixing records without understanding the creation pattern means the same problem may return.
3. Review lifecycle stages
Lifecycle stages are one of the most important structural areas in a B2B HubSpot portal.
They should represent meaningful points in the marketing-to-revenue journey rather than become labels that teams update inconsistently.
For every active lifecycle stage, establish:
What does this stage mean for this business?
There should ideally be a clear entry condition.
For example:
A contact becomes an MQL when the agreed qualification criteria are met.
Not:
Marketing sometimes changes them to MQL.
Also review what can change lifecycle stages, including:
- forms
- workflows
- manual updates
- integrations
- sales activity
- deal creation
If several mechanisms modify the same lifecycle field without clear governance, reporting becomes difficult to interpret.
4. Separate lifecycle stage from lead status
Lifecycle stage and lead status should not be treated as interchangeable.
Lifecycle stage describes the broader position of a contact within the marketing-to-revenue journey.
Lead status can describe more detailed sales qualification or follow-up activity within part of that journey.
During the audit, check whether the business is trying to make one field perform both jobs.
That can make automation harder to govern and reporting more difficult to interpret.
5. Audit workflows as a system
Do not review workflows only one at a time.
A portal with many technically correct workflows can still have a poor automation architecture.
For each important workflow, establish:
Purpose
Why does this workflow exist?
Enrollment
Exactly what causes a record to enter?
Re-enrollment
Can the same record enter again?
Actions
What does the workflow change?
Dependencies
Does another workflow depend on those changes?
Ownership
Who is responsible for maintaining it?
Failure risk
What happens if it stops behaving as expected?
Pay particular attention to workflows that modify:
- lifecycle stage
- lead status
- owner
- source fields
- qualification properties
- deal creation
- notifications
- reporting fields
Those often have wider downstream effects than simple internal alerts.
For a dedicated guide to reviewing workflow logic, see the HubSpot workflow audit guide.
6. Check for automation conflicts
Imagine Workflow A changes a lead to MQL.
Workflow B sees the MQL value and assigns an owner.
Workflow C later overwrites that owner because another condition becomes true.
All three workflows may be functioning exactly as configured.
The system can still be wrong.
A useful HubSpot audit therefore identifies not only broken workflows but also conflicting workflow logic.
Map critical fields back to every automation capable of modifying them.
If several workflows can update the same important property, there should be a clear reason.
7. Review lead assignment and routing
Lead routing connects Marketing Operations with Sales execution.
For each important inbound lead path, determine:
- Who should receive the lead?
- What determines assignment?
- What happens when information is missing?
- What happens for an existing contact?
- What happens for an existing company?
- What happens if the intended owner is unavailable?
- What happens when ownership already exists?
Test routing using realistic scenarios rather than only reading workflow logic.
Examples:
- New US enterprise lead → expected owner → actual owner
- Existing customer submits form → expected treatment → actual treatment
- Lead without territory → fallback owner → actual result
The goal is to identify edge cases before real leads discover them.
8. Audit forms and lead capture
Forms should be reviewed as part of the CRM architecture rather than only as website components.
For each important form, examine:
- fields collected
- required fields
- hidden fields
- conditional fields where used
- consent implementation
- resulting CRM properties
- source information
- workflow enrollment
- notifications
- routing
- lifecycle changes
The key question is:
What happens to the record after the user submits the form?
If nobody can answer that confidently, the form process is not fully governed.
9. Review traffic source and record source separately
Acquisition source and record creation mechanism answer different questions.
For example:
Both can be correct.
A HubSpot audit should check whether reporting confuses:
how the person found the business
with:
how the CRM record was created.
This distinction becomes particularly important when contacts can enter HubSpot through imports, integrations, sales activity and web channels.
10. Review property history when something looks wrong
Current property values do not always explain how the CRM reached its current state.
When an important property appears incorrect, investigate how and when it changed.
The goal is to move from:
HubSpot changed the lifecycle stage.
to something more precise:
This automation or process changed Lifecycle Stage after this condition became true.
That level of traceability is important when troubleshooting automation.
11. Review integrations and data ownership
An integration can make HubSpot appear inconsistent even when HubSpot itself is configured correctly.
Document each important connected system and establish:
Which system owns the field?
Review:
- synchronization direction
- field mappings
- overwrite behaviour
- record creation
- deletion behaviour where relevant
- sync errors
- duplicate risk
- dependency on external IDs
If HubSpot and another platform can both update the same important value, define which system is authoritative.
Do not automatically disconnect integrations because they add complexity.
Determine whether the integration is necessary and whether the data contract is clear.
12. Audit reporting from the business question backward
A dashboard is not trustworthy simply because HubSpot can render it.
For each important report, ask:
What business question is this supposed to answer?
Then trace the report backward.
Example:
If those underlying components are poorly governed, the report may be technically valid but operationally misleading.
Review the underlying data and definitions before redesigning dashboards.
13. Audit permissions and governance
CRM quality is partly a technology problem and partly an operating-model problem.
Identify who can:
- create important properties
- modify lifecycle stages
- build workflows
- import records
- change reports
- install integrations
- modify forms
- manage CRM settings
The objective is not necessarily to restrict everyone.
It is to make responsibility clear enough that structural changes do not happen invisibly.
14. Review what is no longer being used
Old HubSpot configuration accumulates.
You may find:
- old workflows
- unused lists
- abandoned properties
- legacy forms
- outdated reports
- old integrations
- test assets
- previous campaign structures
Do not delete these immediately.
First determine whether other assets depend on them.
Cleanup without dependency analysis can create more problems than the clutter it was intended to remove.
15. Prioritize findings instead of rebuilding everything
The output of a useful HubSpot audit should not simply be:
Here are 87 things wrong with your portal.
| Priority | Meaning | Example |
|---|---|---|
| Critical | Can lose leads, corrupt important data or break commercial processes | Lead routing failure |
| High | Materially affects reporting, automation or team execution | Conflicting lifecycle automation |
| Medium | Creates inefficiency or unnecessary complexity | Duplicate properties |
| Low | Cleanup or documentation opportunity | Old unused lists |
The objective is a remediation roadmap rather than an overwhelming checklist.
A simple HubSpot audit framework
Should you rebuild the HubSpot portal?
Not simply because it is messy.
An audit may show that the portal needs substantial restructuring.
It may also show that the core architecture is sound and only a limited number of workflows, properties or reporting definitions require correction.
The objective should be:
That is more useful than assuming every inherited CRM requires a fresh implementation.