25 HubSpot portal health checks every RevOps leader should run

Start with the operating model

A HubSpot portal can look busy while still producing unreliable reporting and inconsistent customer handoffs. A useful health review begins with the business process, then verifies whether the CRM reflects it consistently.

Use these checks as a prioritization tool. Do not change production configuration simply because a check fails. Confirm ownership, business intent, downstream dependencies, and a safe rollback path first.

CRM data and ownership

• Measure duplicate contacts and companies using the identifiers your business actually trusts.
• Find records without an active owner and confirm the routing rule that should assign them.
• Review required properties that are frequently empty at lifecycle or pipeline transitions.
• Compare lifecycle stage values with the documented customer journey.
• Check whether former employees still own active records, lists, workflows, or reports.

Pipeline and revenue integrity

• Confirm every active deal stage has a clear entry rule, exit rule, and accountable owner.
• Find open deals with no next activity or no recent engagement.
• Review deals missing amount, close date, source, or primary company association.
• Compare closed-won revenue with finance or billing records at an agreed reporting grain.
• Identify automation that moves deals without preserving an audit trail or human review point.

Automation and communications

• Inventory active workflows without a named business owner.
• Review disabled workflows that still represent a required operating process.
• Find overlapping enrollment logic that can update the same property in conflicting ways.
• Check workflow error history, suppression behavior, and unenrollment rules.
• Verify subscription types, consent capture, and suppression logic before sending communications.

Lists, forms, and acquisition

• Archive or document stale lists that no longer have an active operational purpose.
• Review forms for owner assignment, lifecycle updates, consent, and follow-up behavior.
• Confirm lead-source fields survive imports, integrations, and offline conversion paths.
• Test campaign and UTM attribution from conversion through qualified pipeline.
• Verify test records and internal submissions are excluded from decision-making reports.

Reporting and governance

• Confirm executive reports use documented definitions and consistent date fields.
• Identify dashboards that silently exclude teams, pipelines, currencies, or business units.
• Review super admin access and remove privileges that are no longer required.
• Document connected apps, the data they access, and the person accountable for each one.
• Confirm every production change has evidence, approval, validation, and a rollback plan.

Turn findings into governed work

A health check is useful only when findings become owned decisions. Rank issues by customer impact, revenue impact, compliance exposure, and operational effort. Keep the evidence with the decision so the next team member understands why a change was approved.