If your team is tracking onboarding in a spreadsheet because "HubSpot can't do that," someone told you wrong.
If your sales pipeline has records in it that aren't actually sales opportunities, and nobody can explain why, someone made a choice that didn't fit your business.
If you have dashboards full of numbers that don't match what your team sees day to day, and everyone has quietly stopped trusting them... that's not a data problem. That's a structural one.
We hear some version of this on almost every audit call. The system works, technically. Data goes in. Things move through stages. Reports generate numbers. But the team has built workarounds for half of it because the CRM doesn't match how the business actually operates. And nobody can pinpoint the moment it went sideways.
Here's what usually happened: the system was built by someone who knew one part of HubSpot really well and applied that knowledge to everything, including the parts where a different tool was the right answer.
What This Looks Like, IRL
We ran an audit recently where a client had two deal pipelines called "Customer Retention" and "Customer Launch." They were being used to track post-sale workflows. Onboarding steps. Renewal processes. Customer success activities.
None of that is a deal.
When we asked why these were built as deal pipelines instead of ticket pipelines (which is what HubSpot's Service Hub is designed for), the client said: "Our previous partner told us that was the only way to build them."
Ticket pipelines have existed in Service Hub for years. And this client already had a working ticket pipeline in their own portal for a completely different process. The infrastructure was right there.
The previous partner was a sales-focused shop. They knew Sales Hub. They knew deals. So when the client said "we need to track onboarding and retention," the partner reached for what they knew. Not because they were cutting corners. Because that was their expertise. And the client didn't have the platform knowledge to question it.
This is incredibly common. A marketing-focused agency solves operational problems with Marketing Hub tools. A sales consultancy builds service workflows in Sales Hub. A dev shop builds custom integrations before checking whether a native feature already does the job. Each one is solving your problem with the tools they're most comfortable with, which aren't always the right tools for your situation.
The Signs Are Already There
The tricky part is that a system built on the wrong foundation still functions. It just creates friction that builds so gradually nobody notices where it started.
Here's what it tends to look like from the inside:
Your team has spreadsheets that duplicate what the CRM should be tracking. Onboarding checklists in Google Sheets. Customer health tracked in a spreadsheet because the CRM version doesn't work the way they need it to. Manual trackers for things that should be automated. If your team maintains a system next to HubSpot to do the things HubSpot is supposed to do, something in the build doesn't fit.
Your pipeline numbers don't feel right, but you can't explain why. Deal count seems high. Pipeline value seems inflated. Win rates don't match reality. If non-revenue activities (onboarding, renewals, customer success steps) are living in a deal pipeline, they're polluting every sales metric you pull from it.
Reports generate numbers, but nobody acts on them. The data is there, but the team doesn't trust it enough to make decisions from it. So the reports exist for documentation, not for direction. That's usually a sign that the underlying data model doesn't reflect how the business actually works.
There are hundreds of properties and nobody knows what half of them do. In the audit we ran, the portal had 405 contact properties with no naming convention. Created by different people, different integrations, different partners over the years. No documentation. No way to tell which ones are active, which ones are legacy, and which ones are powering a workflow that will break if you touch them.
Integrations are creating records nobody asked for. This same portal had over 1,200 company records with no name. Created by a sync that nobody owned, mapping data without mapping the company name field. Those blank records were cluttering the database, associating with contacts, and showing up in reports.
Critical processes depend on one person. The client had built a customer health score (genuinely valuable). But only one team member had the permissions and the knowledge to update it. Her customer success manager couldn't edit it. Her CTO couldn't edit it. If she went on vacation, the health score was frozen. That's not a feature. That's a single point of failure.
Why It Happens
This isn't about having a bad partner. In many cases, the partner was good at what they did. The mismatch was between what they specialized in and what you needed.
HubSpot is a big platform. Sales Hub, Marketing Hub, Service Hub, Operations Hub, Content Hub, Commerce Hub. Each one has its own tools, objects, and logic. A partner who lives in Sales Hub every day might have surface-level familiarity with Service Hub but wouldn't instinctively reach for ticket pipelines when a client describes an onboarding workflow. They'd reach for deals. Because that's what they know.
And you, as the client, don't have the platform expertise to push back. If someone tells you "this is the only way to build it," you believe them. Not because you're not smart. Because you hired them to be the expert, and you trusted their answer.
The problem isn't trust. It's that the answer was limited by what they knew, not by what was possible.
The Real Cost
The cost isn't messy data or a few misused pipelines. It's what happens to your team over time.
When the system doesn't fit, the team learns to work around it. They build the spreadsheets. They create manual processes to compensate for automations that fire on the wrong objects. They stop looking at reports because the numbers stopped meaning anything useful.
And eventually, the workarounds become the process. "This is just how we do it" replaces "is there a better way to do this?" The CRM that was supposed to make operations easier becomes one more thing to manage around.
That's the expensive part. Not the cleanup (that's fixable). It's the months or years of a team operating below what the system could give them because nobody questioned the original build.
You Don't Have to Start Over
The good news is that fixing this doesn't mean burning it down. A proper audit identifies what's structurally wrong, what's cosmetically messy, and what's actually working fine. Then you prioritize.
Move the service workflows to Service Hub. Clean up the properties. Document what exists and who owns it. Fix the permissions so critical functions aren't dependent on one person. Set naming conventions going forward so the next 405 properties don't end up the same way. Audit the integrations creating records nobody asked for.
It's not glamorous work. But it's the work that turns a portal from "technically functional" into "actually trustworthy." And that's the difference between a system your team works around and a system your team works inside.
Questions Worth Asking About Your Own Portal
If any of the above sounds familiar, here are a few things to look at:
Are you tracking non-revenue activities in a deal pipeline? If your deal pipeline includes onboarding, implementation, renewal tracking, or customer success steps, those probably belong somewhere else.
Does your team maintain spreadsheets or trackers alongside HubSpot? If so, what are they tracking that HubSpot should be tracking? That gap is your roadmap for what needs to be fixed.
How many properties do you have, and can you explain what each one does? If the answer is "a lot" and "no," that's worth auditing.
Are there records in your portal that nobody created on purpose? Ghost companies, unnamed contacts, duplicate records from integrations running without filters.
Is there anything in your portal that only one person knows how to maintain? A health score, a workflow, a custom property with logic nobody else understands. If that person leaves, what happens?
When your partner built your system, did they specialize in the part of HubSpot you needed help with? This is the question nobody thinks to ask during the sales process. But it's the one that determines whether your system got built with the right tools or with the tools someone happened to know.
If you're looking at your portal and something doesn't feel right (even if you can't articulate exactly what), that's what we do.