# HubSpot Audit: Portal Review and Repair Checklist

A HubSpot audit should identify the failures that affect customer handling, reporting and access, then turn them into a prioritized repair plan. Review a defined portal population, trace changes to their sources and test the resulting workflow. A useful audit records both confirmed defects and gaps in evidence, with an owner and acceptance condition for each finding.

Canonical URL: https://www.martechdevs.com/blog/hubspot-audit

By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo)

Data Engineer and Co-founder at [Martechdevs](https://www.martechdevs.com) and [Growth and Analytics Partners](https://www.growthandanalytics.com)

[LinkedIn](https://linkedin.com/in/jafrinalo)

Last updated: 2026-11-15

Next step: [CRM workflow and reporting repair](https://www.martechdevs.com/crm-lifecycle). Connect verified findings to owned changes and repeatable acceptance checks.

## Audit Coverage

Start with the customer workflow that needs to remain reliable.

| Area | Review question | Evidence | Repair owner |
| --- | --- | --- | --- |
| Access | Approved users and operations | Users, roles, permissions and sample access | Portal administrator |
| Data | Correct identity and required values | Defined record population and change history | CRM operations |
| Automation | Correct entry, actions and completion | Workflow settings and record paths | Workflow owner |
| Integrations | Correct destination and field authority | Mappings, exclusions, failures and matched IDs | Integration owner |
| Reporting | Explained totals and audience | Filters, underlying records and sharing | Reporting owner |
| Operating ownership | Repeatable detection and repair | Finding log, escalation and review dates | Revenue operations |

For a B2B enquiry process, follow one record from form submission through assignment, qualification and accepted sales action. Include an existing customer, a duplicate identity and a record that should be excluded. Those cases reveal more about the process than a count of available portal features.

For a renewal process, start with the contract or subscription authority and trace the renewal date into HubSpot, the reminder workflow and the account owner's view. The appropriate audit population depends on the decision being made.

When findings span source systems, workflows and ownership, [CRM and lifecycle services](https://www.martechdevs.com/crm-lifecycle) can turn the audit into a maintained operating process. Keep the audit's finding list separate from the implementation scope so each proposed change has a clear reason and acceptance test.

## Audit Scope and Evidence

Agree the portal, business unit, objects, time window and processes before extracting data. Specify what counts as in scope: perhaps open sales deals, active customer companies and enquiries created during a fixed month. A portal-wide export can include years of records that no longer participate in the workflow.

Record the population definition alongside every defect rate. Fourteen missing owners among 200 eligible enquiries is meaningful; fourteen missing owners without a denominator cannot distinguish a localized problem from a widespread one.

Use four finding states:

- **Confirmed failure:** Observed behavior or data violates an agreed requirement.
- **Evidence gap:** The available logs or sample cannot establish the outcome.
- **Accepted exception:** An owner has approved a documented deviation with a review date.
- **Verified repair:** The original failing case and relevant negative cases pass after a change.

An evidence gap should remain visible. A blank log view is not proof that a workflow never ran, and an integration showing no current errors is not proof that every eligible record reached its destination.

Keep record IDs, timestamps, configuration references and expected outcomes in a restricted evidence file. Avoid copying full message bodies or unnecessary customer details into the audit summary. The executive finding should explain the business effect without reproducing the underlying personal data.

The [HubSpot implementation checklist](https://www.martechdevs.com/blog/hubspot-implementation-checklist) covers a new rollout. An ongoing audit should compare actual use with the current operating agreement, including changes made since launch and controls that have lost an owner.

## Portal Access Review

1. List active users, administrators, teams and the paid capabilities each role needs.
2. Compare granted operations with current responsibilities.
3. Select representative ordinary users and integration identities for testing.
4. Check permitted and prohibited operations on sample records.
5. Record unexplained grants and the business owner who can resolve them.

HubSpot separates tool permissions and record access, with some capabilities dependent on the user's seat and subscription tier. For example, sales and service access can expose additional granular controls, while billing permissions govern paid seat changes. Review both entitlement and permission rather than treating a paid seat as blanket authority. [HubSpot user permissions](https://knowledge.hubspot.com/user-management/hubspot-user-permissions-guide).

A useful test is specific: a representative can update their own deal's next step, cannot edit an unrelated team's restricted record, and can see the report needed for their weekly review. Document the expected result for each operation before testing it.

Treat unused accounts and broad access as findings requiring context. An integration identity may have no interactive login because it operates through an approved application. Confirm its owner, authentication route, object scope and downstream dependencies before changing it.

For departed staff, include owned workflows, scheduled report emails and connected applications in the handover. Removing a person from the user list does not establish that every process they administered has a new accountable owner.

## Data and Property Review

HubSpot's data quality overview includes duplicate, formatting, enrichment and property insights. Availability and actions depend on subscription and permissions; individual features have additional requirements. It is a useful input to an audit, alongside the process-specific population. [Data quality tools](https://knowledge.hubspot.com/data-management/use-data-quality-tools).

Begin with fields that affect action: record identity, owner, lifecycle state, consent or subscription status, next action and relevant dates. A missing optional job title may have little operational effect. A missing owner on an eligible enquiry can stop follow-up entirely.

Inspect the producer of each important property. The [CRM property ownership guide](https://www.martechdevs.com/blog/crm-property-ownership) provides a field-level approach to deciding which system can set a value and how conflicts are resolved. For the audit, capture the current value, expected authority and evidence of the last change.

For an individual record, HubSpot's property history shows changed values, dates and sources. Open the record's property history when a value unexpectedly reverts or changes after an integration run. [Record property history](https://knowledge.hubspot.com/records/view-record-property-history).

Do not infer campaign origin from the system that last updated a field. Record creation, field modification and acquisition attribution are different questions. Keep the audit worksheet's columns specific enough to preserve that distinction.

HubSpot also notes a limitation of its data quality tool: after a record is corrected there, a later manual change back to an incorrect format will not be flagged again by that overview. Repeated process checks therefore need their own defined population and validation. [Data quality behavior](https://knowledge.hubspot.com/data-management/use-data-quality-tools).

## Defect Rate Example

Suppose an audit examines 200 eligible enquiries from a fixed month. Fourteen lack an assigned owner, eleven lack the required qualification state and five appear in both groups. These are hypothetical counts, not a suggested industry benchmark.

| Measure | Calculation | Result | Interpretation |
| --- | --- | ---: | --- |
| Missing owner rate | 14 / 200 | 7% | Assignment defect in the eligible population |
| Missing qualification rate | 11 / 200 | 5.5% | State defect in the same population |
| Records with either defect | 14 + 11 - 5 | 20 | Unique affected records |
| Unique affected rate | 20 / 200 | 10% | Combined defect rate without double counting |

Adding 7% and 5.5% would overstate the unique affected rate because some records have both defects. Keep a record-level finding file so the combined count can be reproduced. Use the [conversion rate calculator](https://www.martechdevs.com/tools/conversion-rate-calculator) for a numerator and denominator check, while preserving the deduplicated population separately.

If the team fixes 16 of the 20 affected records, the original cohort has four unresolved cases. Its unresolved rate is 4 / 200, or 2%. That is a repair measure for the original cohort. Review new incoming enquiries separately to establish whether the source problem has stopped producing defects.

A repair can improve the old cohort while the producer continues making mistakes. Report both numbers: remaining old defects and defects among newly eligible records. Keep the same definition over time, or explicitly record the changed scope.

## Workflow and Change History

For each important workflow, record its owner, entry criteria, re-enrollment policy, exclusions, actions, completion condition and failure route. A workflow named Customer Onboarding may contain several unrelated populations after years of edits; inspect its actual criteria.

HubSpot's workflow details page supports action logs, enrollment history and revision filtering. Action logs are retained for 90 days, while enrollment history is retained for six months for workflow-based filters. Successful execution logging has a daily limit of 100,000; after that threshold, success and information logs stop being stored for the day while errors continue and workflows keep running. [Workflow history and limits](https://knowledge.hubspot.com/workflows/understand-your-workflow-details-page).

Choose examples that cover the process boundaries:

| Case | Expected behavior | Evidence | Failure treatment |
| --- | --- | --- | --- |
| Newly eligible enquiry | Correct assignment and task | Record path and resulting owner | Repair entry or routing |
| Existing customer | Customer-specific treatment | Exclusion or separate branch | Repair classification |
| Suppressed recipient | No marketing action | Subscription state and branch outcome | Stop the affected send route |
| Repeated source event | Defined repeat behavior | Enrollment and resulting actions | Repair duplicate action policy |
| Completed process | No unnecessary continuation | Completion condition and record path | Repair exit logic |

Use an approved test population and prevent external sends during a rehearsal. For a production incident, inspect the existing record path before replaying an action. A replay can create a second task, alter an owner or send another message even when the original log is incomplete.

The centralized audit log answers a different question. HubSpot requires Super Admin access to view and export it, and it records user-based actions. A property update from a form submission does not appear there. The main views cover the last 30 days, and available categories vary by subscription. [Account activity history](https://knowledge.hubspot.com/account-management/view-and-export-account-activity-history).

Use audit logs for user actions, property history for field changes and workflow evidence for automation paths. Correlate them using the record and time rather than expecting one page to provide the whole sequence.

## Integration Review

For every active connector, identify the source and destination objects, matching key, allowed direction, field mappings, exclusion rules and operational owner. Then select records that should sync and records that should remain excluded.

For apps using HubSpot data sync, the CRM syncs view distinguishes in-sync, failing and excluded records. Exclusion can result from filters or a missing matching identifier. HubSpot supports a targeted rerun for selected failed records. These controls apply to data sync connectors; other integrations have their own monitoring surfaces. [HubSpot data sync monitoring](https://knowledge.hubspot.com/integrations/connect-and-use-hubspot-data-sync).

Reconcile categories against the agreed population. In a hypothetical 500-record review, 450 in sync, 30 excluded and 20 failing account for all 500. The 30 exclusions still need classification. If ten should have qualified, they belong in the repair queue even though the connector has labeled them excluded rather than failed.

Inspect a destination record after a reported success. Confirm its identifier, associations, important values and modification time. A successful API request can still carry an unintended source value. Keep the expected field authority visible during this comparison.

Resolve the producer before replaying a large backlog. Start with a small set of affected IDs and confirm that a repeated run has the intended effect. The [HubSpot Salesforce sync guide](https://www.martechdevs.com/blog/hubspot-salesforce-sync) covers the additional matching and conflict choices for that specific integration.

## Reporting and Priority

Choose one business-critical report and reconcile it to a known record population. Record the date property, stage criteria, currency basis and exclusions. Check the result as an ordinary intended reader, then review any scheduled distribution separately.

Prioritize findings by business effect and scope. A broken exclusion that permits an unwanted send needs immediate containment. A misleading pipeline total needs a clear correction before the next decision meeting. A redundant property can wait until its dependencies have been checked.

Avoid combining everything into an unexplained portal score. A ten-point improvement could conceal an unresolved high-impact failure. Use a short register with the affected workflow, confirmed evidence, owner, next action and acceptance condition.

For example: twelve eligible enquiries have no assigned owner; the source form sends a region value absent from the routing map; the CRM owner will add the approved mapping; acceptance requires the twelve repairs plus new enquiries from that region to reach the intended queue. This is a hypothetical finding format, not a claim about a client portal.

## Audit Repair Flow

![Defined scope leads to evidence collection. Evidence gaps repeat collection; requirement failures return through producer and record repair before acceptance and recurring review.](https://www.martechdevs.com/assets/blog/hubspot-audit.svg)

Diagram connections:

- Process and population to Evidence collection. 
- Evidence collection to Evidence coverage. 
- Evidence coverage to Evidence gap and owner: Incomplete. 
- Evidence gap and owner to Evidence collection. 
- Evidence coverage to Record and workflow checks: Complete. 
- Record and workflow checks to Requirement agreement. 
- Requirement agreement to Producer and record repair: No. 
- Producer and record repair to Evidence collection. 
- Requirement agreement to Accepted findings: Yes. 
- Accepted findings to Recurring review

The repair loop returns to evidence collection so the reviewer checks the changed configuration and affected records. A finding closes after the acceptance case passes and the next operating owner is clear.

## HubSpot Audit Checklist

- [ ] The portal, workflow, population and review period are explicit.
- [ ] Access checks include ordinary users and integration identities.
- [ ] Important fields have a named source and modification evidence.
- [ ] Defect counts use unique records and a stated denominator.
- [ ] Workflow entry, exclusions, repeat behavior and completion have examples.
- [ ] Log coverage and retention gaps remain visible in findings.
- [ ] Integration failures and unintended exclusions have separate counts.
- [ ] Destination records agree with the approved source values.
- [ ] Business reports reconcile to record IDs and the intended audience.
- [ ] Each repair has an owner, acceptance condition and follow-up date.

Use the [CRM data hygiene audit skill](https://www.martechdevs.com/skills/crm-data-hygiene-audit) to structure the record review. Pair it with this broader portal checklist so access, automation and integration ownership receive the same attention as data cleanup.

## Frequently asked questions

### How often should a HubSpot portal receive a full audit?

Set the cadence around change and business risk. A stable portal may need a periodic full review plus smaller recurring checks, while a migration or major workflow release warrants immediate verification of the affected process. Keep assignment failures, sync errors and high-impact exclusions under regular monitoring between audits. The cadence should name both the reviewer and the evidence required.

### Can a HubSpot audit be useful without an Enterprise subscription?

Yes. A useful audit can combine the available record views, property history, permissions, integration evidence and process samples. Some centralized log categories and advanced tools depend on subscription, so record those limits in the evidence register. Do not label an unavailable control as passing. Define an alternative check where possible and retain the gap where evidence remains insufficient.

### Should duplicate records be merged during the audit itself?

Treat merging as a separate repair with an approved survivor and association policy. The audit should establish whether records represent the same entity, which values matter and which systems reference their identifiers. Preserve the evidence before making changes. Review a small representative set first so a cleanup does not break ownership, subscriptions, reporting or connected applications.

### What distinguishes a HubSpot audit from a data cleanup project?

A HubSpot audit evaluates whether the portal supports its intended work, including access, automation, integrations, reporting and ownership. Data cleanup repairs particular records. An audit may recommend cleanup, but it should also identify the form, mapping or workflow that produced the defect. Otherwise the same records can become unreliable again after the repair project ends.

### What belongs in the handover after a HubSpot audit?

Hand over a prioritized finding register, restricted evidence references, named repair owners and acceptance conditions. Include accepted exceptions and unresolved evidence gaps, not only completed fixes. Give the operating team a repeatable check for new records and a date for reviewing the original failures. The handover is useful when another person can explain and verify each finding.

## Sources

1. [HubSpot user permissions](https://knowledge.hubspot.com/user-management/hubspot-user-permissions-guide)

2. [HubSpot data quality tools](https://knowledge.hubspot.com/data-management/use-data-quality-tools)

3. [HubSpot record property history](https://knowledge.hubspot.com/records/view-record-property-history)

4. [HubSpot workflow details and history](https://knowledge.hubspot.com/workflows/understand-your-workflow-details-page)

5. [HubSpot account activity history](https://knowledge.hubspot.com/account-management/view-and-export-account-activity-history)

6. [HubSpot data sync](https://knowledge.hubspot.com/integrations/connect-and-use-hubspot-data-sync)
