16 HubSpot problems owners bring us, and what fixes each one
Owners don't call us about "HubSpot implementation." They call about what hurts: the numbers don't match, reps won't use it, nobody believes the pipeline. These are the 16 HubSpot problems we hear most, in the words owners use, with the cause we usually find and what fixes it.
Jump to: reporting · adoption · ERP · leads and data · pipeline stages · healthcare, automation and AI
HubSpot reporting problems
1. "Our HubSpot numbers don't match the ERP."
Usually the sync is fine. The two reports answer different questions: they filter on different dates, define revenue differently, or count deals where the ERP counts lines.
Fix: write down what booked, billed and invoiced mean, filter on the ERP's dates, and reconcile one full cycle before anyone trusts the dashboard. Why your HubSpot revenue doesn't match your ERP →
2. "The pipeline says millions. Nobody believes it."
Old bids and multi-option quotes never get closed out, and stalled deals sit in a stage that means "maybe someday." The total grows every month while the real pipeline doesn't.
Fix: close replaced bids by rule, require a reason on every other lost deal, and drop the "Future Opportunity" stage. Why your HubSpot pipeline is inflated →
3. "Our renewal and churn numbers make no sense."
Reps edit last year's deal instead of creating a renewal, which erases the history. Or a multi-year contract is booked as three deals, so years two and three look like renewals.
Fix: every renewal is a new deal, created before the contract ends, and a multi-year contract is one deal with a line item per year. HubSpot renewal tracking →
When reps won't use HubSpot
4. "Our reps won't use HubSpot. They still do everything in the ERP."
For the job reps do most, entering orders, the ERP screen is faster than a deal card. And nobody requires the CRM.
Fix: ask reps for fewer fields, only at the stage that needs them. Where order entry is the job, build a screen as fast as the ERP that writes to both systems. Then the sales leader has to require it. Why your sales team doesn't use HubSpot →
5. "Our last partner took a year and never finished."
The usual pattern: nobody decided up front which system owns which data, nothing went live along the way, and the scope kept growing while nothing shipped.
Fix: decide which system owns every field in week one, and see the build running on real data early, not at a big reveal. HubSpot rescue →
HubSpot and ERP integration problems
6. "We want real-time, two-way sync on every field."
It sounds safest and breaks first. Many ERPs read well but don't announce changes or deletions, so a sync that assumes they do drifts.
Fix: give every field one owning system, sync on a schedule, and reconcile deletions. When to integrate HubSpot with your ERP →
7. "We're replacing our ERP next year, but we want the integration now."
An integration with the ERP you're leaving gets thrown away within months.
Fix: get reps working in HubSpot now and connect it once, to the new ERP. Replacing your ERP? What to do with HubSpot first →
HubSpot lead and data problems
8. "Leads fall through the cracks. Follow-up is slow."
Leads are assigned by hand, routing rules are buried in workflows nobody can read, and nothing fires when a lead sits untouched.
Fix: route from a territory sheet your team keeps, and move lead stages on activity, not on owner changes. At Plant Tours, new leads followed up within an hour rose from 41% to 84%. How to route HubSpot leads by territory →
9. "We can't tell where our leads come from."
One source field is answering two questions: how the contact found you, and how they got in touch. Forms drop UTMs, and leads entered by hand have no source at all.
Fix: split the field in two and require a source on every record a rep creates. Your Contact Source field is answering two questions →
10. "HubSpot is full of duplicates."
More than one tool creates records, nothing stores a unique ID from the other system, and imports create a company per contact.
Fix: find every tool that creates records, store each external system's ID on the record, and standardize before you merge. Standardize before you deduplicate →
11. "Emails aren't logging, or the email sync floods the CRM."
Per-rep inbox connections miss anyone who hasn't signed in, and turning on contact creation without rules imports every vendor and newsletter.
Fix: before anything syncs, decide which senders are allowed to create a contact. Otherwise every invoice robot ends up in the CRM. Request your free HubSpot audit →
HubSpot pipeline stage problems
12. "Our MQLs live in a deal pipeline."
Marketing built its funnel on deals, so leads show up as won deals and the history is unreadable.
Fix: move leads to the Lead object going forward. Keep the old reports for the quarters before the switch and the new ones after, on one dashboard. Lead Status vs the Lead object →
13. "Closed Won doesn't mean anything for us."
Common in service businesses running a pipeline built for software sales. Signed isn't served, and the person who pays isn't always the person who chose you.
Fix: decide what won means for your business and move the stage to match, then track active clients by recent service, not by deal stage. Your Closed Won stage is lying →
Healthcare, automation and AI
14. "Can we keep patient data in HubSpot?"
Yes, on Enterprise with HubSpot's BAA in place, decided field by field. Clinical records stay in the EHR, and HubSpot runs the engagement.
Fix: classify every field before anything is built, because the sensitive setting can't be changed later. How to set up HubSpot for HIPAA →
15. "Our Zapier bill keeps growing."
Zapier charges per task, and flows that poll and loop burn tasks.
Fix: move the flows to n8n, billed on volume rather than per task. At California Mobility, the bill went from $253 to $120 a month at the same volume. Zapier to n8n migration →
16. "We want AI agents."
Usually the step that needs judgment hasn't been named, so "AI" is standing in for a missing process.
Fix: build the integration first, then put AI where a person would otherwise have to think. At Fowler, HubSpot's Customer Agent handled 70% of incoming tickets without escalation in its first month. HubSpot AI agents →
Which HubSpot problem do you have?
Most portals have two or three of these at once, and they feed each other. The free audit finds which ones you have, fixes the quick wins, and prices the rest.
Request your free HubSpot audit →
Not on HubSpot yet, or not sure where to start? Book a free 30-minute review
FAQ
What are the most common HubSpot problems?
Reps working around the CRM instead of in it, reports that don't match the ERP or finance, an inflated pipeline, duplicate records, and lead sources nobody trusts. Most come from how the portal was set up, not from HubSpot itself.
Is it HubSpot or how it was set up?
Usually how it was set up. Stages nobody defined, too many required fields, and several tools writing to the same records cause most of what owners blame on HubSpot. Check the setup before you switch CRMs.
How do I fix a HubSpot portal that nobody uses?
Cut what reps are asked to fill in, require fields only at the stage that needs them, and make HubSpot the fastest way to do the job. Then the sales leader has to require it. A free audit shows which of these your portal needs.