You are running HubSpot when your team knows which features it uses, your reports get trusted without a spreadsheet double-check, and people do not need private trackers to fill gaps in the portal. When those things fail, you are still paying for HubSpot. You just are not getting the value you bought.
HubSpot releases faster than most teams maintain their portals. The Spring 2026 Spotlight delivered more than 100 updates on April 14. Commerce Hub became Revenue Hub in June. Agent Hub and Agent Builder entered public beta in July. HubSpot's Q2 2026 results also point to growing adoption of its AI capabilities and agents.
A portal configured at go-live and left alone can quickly become disconnected from the product HubSpot has become. That gap widens with every release, unused feature, outdated workflow, and workaround your team adds outside the system.
What follows is a diagnostic. Each section answers a question worth asking about your own portal, starting with how to tell if it has drifted and ending with the cadence that keeps it from drifting again.
Five behavioral signals indicate an underused portal. You will notice most of them in meetings before an admin finds them in settings, and each one has a specific place in HubSpot where you can confirm it in under five minutes.
Leadership asks someone to rebuild a report in a spreadsheet because the dashboards never look right. The reporting layer has quietly stopped serving as the source of truth. You can confirm it by asking your finance or ops lead which number they trust more, the dashboard or their own export. The answer is usually immediate.
Workflows created by former employees may still be running and enrolling contacts every day. Over time, the business changes, but the automation does not. Open Automation, sort workflows by last modified date, and count how many active workflows have not been updated in the past year.
A contact is marked as a Customer even though they still have an open deal because deal stages are not updated consistently across systems. Create a list of contacts with a Customer lifecycle stage and an associated open deal. If the list contains more than a handful of contacts, your funnel reporting may be inaccurate.
Property sprawl is an early sign that a portal has started to drift. Over time, teams often create hundreds of custom properties, many of which are no longer used or serve overlapping purposes. Go to HubSpot Settings → Properties and filter for custom contact properties. Anything above 50 deserves a review.
Nobody on the team can name the last new HubSpot tool they turned on. Compare your subscription line items with the tools your team touched last quarter, and note any differences.
One signal is normal maintenance. Two or three means the portal has drifted and reporting is already affected. Four or more means the system has stopped functioning as a system of record, and every downstream decision built on it carries risk.
An underused HubSpot portal can create five hidden monthly costs: inflated contact tiers, unused seats, duplicate software, poor data-driven decisions, and staff time spent on manual work.
Poor data hygiene can create duplicate records and increase the number of contacts counted for billing. Because Marketing Hub pricing is based on marketing contacts, duplicate records marked as marketing contacts can increase your bill. Reviewing and cleaning duplicate records can help prevent unnecessary contact tier increases.
HubSpot's seat structure includes Core Seats and View-Only Seats. Users who only need to view information may not need a paid Core Seat. Reviewing seat assignments before renewal can identify licenses that no longer match how your team uses the portal.
This is the highest and least visible cost, because each tool looks small on its own. Before renewing anything, check the overlap against what you already own.
Four or five of these at $40 to $300 a month each turns into a five-figure annual line that duplicates capability you already bought.
Gartner puts the average annual cost of poor data quality at $12.9 million per organization and reports that 59% of organizations do not measure data quality at all. Forecasts built on incomplete records produce hiring plans and budget commitments that were wrong before anyone approved them.
When dashboards lose credibility, someone starts exporting and reconciling by hand every month. That work is invisible on any budget because it hides inside salaries already being paid, and it grows quietly as reporting confidence declines.
Stack those together, and the underused portal frequently costs more than the fully operated one.
Your team avoids the CRM because logging work costs them more time than it gives back. Reps lose roughly eight hours a week to admin and data entry, and much of that goes into fields nobody reads. When entry feels like a tax, and the record returns nothing useful, skipping it is the rational choice.
This is a behavior problem, not a training problem. Poor user adoption causes 43% of CRM failures, bad data quality 34%, and insufficient training 22%, and more than 60% of failures come down to people and process. Retraining a team on a configuration that wastes their time changes nothing, because week two looks the same as week one.
The workload is the part leaders underestimate. Eight hours a week per rep adds up to more than 4,400 hours a year across a team of ten. Broader research puts the number higher, with the average rep spending close to two full days each week on administrative work.
If your portal was configured before April 2026, you are missing a substantial release, two renames, and a mandatory interface change. The Spring 2026 Spotlight introduced HubSpot AEO for tracking brand visibility inside AI answer engines, Smart Deal Progression, a rebuilt Prospecting Agent, expanded Customer Agent coverage, Data Studio, and general availability for the HubSpot MCP server.
Operations Hub became Data Hub at INBOUND 2025, with pricing carried over unchanged. The Data Quality Command Center and custom code actions are available starting at Professional, which surprises teams who assumed both were Enterprise-only and priced their cleanup project accordingly.
Then on June 16, 2026, Commerce Hub became Revenue Hub, expanding from billing and payments into full quote-to-cash with CPQ, a native contract object, price books, subscription billing, and payments. Existing setups carried forward with no migration required, and the Commerce Seat is now the Revenue Seat.
Agent Hub and Agent Builder entered public beta on July 23, 2026. Agent Builder is a no-code workspace for creating custom agents using the data and context already available in Smart CRM. Prospecting Agent access also expanded to all paid portals, with user-level permissions controlling who can access and use it.
HubSpot is moving Agent pricing toward outcomes. Prospecting Agent costs $1 per lead, while Customer Agent costs $0.50 per resolved conversation. Both use HubSpot Credits, so costs are tied to agent activity rather than additional seats. This changes the activation math for teams that previously ruled out AI because of per-seat costs. A team can estimate spend based on the number of leads the agent works or conversations it resolves.
Readiness comes from your data and not from your license. The day you turn on Breeze is not the day your portal is ready for it. Two portals with identical Breeze access can produce measurably different results, because AI agents read what is already in your CRM. Thin records and broken associations give them nothing solid to work from.
Four things carry the most weight.
Consistency counts as much as volume. Records structured the same way across your database support reliable scoring and summarization. Records filled in five different ways by five different teams do not.
Start with Breeze Assistant drafting under human review. That surfaces your gaps before an agent acts on them unsupervised, and it gives your team a clear read on where the data needs work.
Our breakdown of AI readiness as an architecture problem covers the full picture, and the HubSpot AI Readiness Index scores a portal across five dimensions in a few minutes.
Review these weekly in your pipeline meeting:
Review these quarterly, ahead of budget cycles:
Build all eight as saved dashboards owned by one person. Metrics that require manual assembly are likely to get skipped during a busy week and eventually forgotten.
Fix your current CRM when the platform still meets your business needs. A new CRM does not solve duplicate records, inconsistent data, missing fields, weak processes, or poor adoption. Those problems can follow you into the new system while adding migration costs and disruption.
CRM problems often come from data and processes rather than the platform itself. A migration also creates new work. Integrations need to be reconnected, users need to adjust to new workflows, and historical associations and activity data require careful mapping. Consent and compliance records also need to be reviewed as part of the transfer.
CRM cleanup should happen before a migration. Duplicate records, inconsistent naming, missing fields, and broken associations become easier to spot during migration preparation. Cleaning those issues in your current portal can solve the same problems without the cost and disruption of changing platforms.
A CRM switch makes sense when the platform has reached a genuine capability ceiling. Common reasons include:
For most teams, a better sequence is to clean the current portal, operate it properly for 90 days, and then reassess. You can make the migration decision using clean data and actual performance evidence.
Run the Data Quality Command Center and record your duplicate rate before and after merging. Export a property inventory for each object, including fill rate and asset usage, then archive properties used by no assets. Create a field dictionary that identifies the master property for each data point to prevent future sprawl. Compare assigned seats with login activity. Then, review every active workflow, its owner, and last modified date, and flag anything with no clear owner. Expect to find more issues than planned. That is the point.
Define every lifecycle stage and deal stage in writing with an entry criterion someone can verify. Find and fix contacts with no lifecycle stage. Audit workflows for enrollment conflicts and for multiple automations writing to the same property. Turn off automation nobody can justify, and archive rather than delete so you keep the history. This is also the right window to review integration field mappings.
Rebuild core dashboards on the cleaned model and have leadership confirm the numbers match reality before you publish them. Convert idle Core Seats to View-Only ahead of renewal and right-size your marketing contact tier. Cancel the point solutions your subscription duplicates. Then activate the AI capability that has been waiting, starting with internal use cases like enrichment and sales productivity before anything customer-facing.
TELUS Health is one example of the payoff. Attribution there ran on more than 60 conflicting Lead Source values, and MQL routing was spread across 200 workflows. The rebuild turned those into 15 standardized categories and a single routing property, with 350,000 records cleaned along the way. Marketing could report ROI again, and the digital team went back to strategy work. See the full breakdown.
Open Data Management, then Data Quality, and write down three figures. Your duplicate rate, your count of unused properties, and how many active workflows nobody on the current team can explain. Those three answers tell you within ten minutes where your portal sits between owned and operated.
If you want the full version of that review, our HubSpot Portal Audit Checklist walks through every area to inspect and what good looks like in each one. When you need help interpreting what those numbers mean for your revenue reporting, our team is happy to take a look.