It rarely happens all at once. A sales rep keeps a "quick" spreadsheet of hot leads. A manager starts asking for pipeline updates on WhatsApp because the dashboard looks wrong. Six months later, HubSpot is the place where data goes to be forgotten, and the business is paying for a system nobody trusts.
Key takeaways
Low adoption is easy to miss, because HubSpot keeps running whether people use it properly or not. These are the signs that come up in our conversations with teams whose setup isn't working:
Side spreadsheets. People keep their own lists of leads, deals or customers because they find them faster or more reliable than HubSpot.One or two of these on their own is normal. Three or more usually means the team has quietly decided the CRM isn't worth the effort.
People don't abandon a CRM because they dislike software. They abandon it because, for them, it makes their job harder than the alternative. The underlying causes tend to be a combination of the following.
If the first account a sales rep opens has three versions of the same company, or a contact list full of outdated emails, they conclude the system is wrong. Often the root cause is a migration that moved data in without cleaning or mapping it first. Once trust is gone, people stop entering new data too, and the problem compounds.
Pipelines and lifecycle stages were set up from a template, or for how the business worked two years ago. Sales has a stage that doesn't exist in HubSpot; marketing calls something a "lead" that sales would never call one. When the system doesn't reflect reality, people work around it.
Marketing hands over a lead it considers qualified; sales disagrees; neither definition is written in the CRM. The result is arguments about numbers and reports nobody believes. HubSpot can only enforce definitions the teams have actually agreed.
Too many required properties, too many steps to log a call, too many pipelines. Every extra field is a small cost to the person entering data, and busy people stop paying it.
The project ended at launch. There's no internal owner to answer questions, adjust workflows, check data quality or train new joiners, so small problems pile up until the system feels broken.
Everyone sat through a session at launch, then forgot most of it. New staff were never trained at all. Without follow up, people use the five features they remember and work around the rest.
If the same information has to be typed into HubSpot and into accounting, ecommerce or another tool, the CRM loses. People enter data where they're forced to and skip it everywhere else.
A team subscribes to HubSpot expecting it to organise their sales and marketing, but nobody has the time or knowledge to configure it. It ends up partially configured, which can be worse than not set up at all.
Before deciding what to fix, it helps to be honest about where the problem sits.
It's probably the setup if HubSpot can do what you need but the structure, fields, pipelines or automations don't reflect how your teams work, or your data is messy. This is the most common case, and the most fixable.
It's probably the people side if the setup is reasonable but nobody owns it, training was a single session, or teams were never asked to agree on definitions. This is also fixable, but it needs commitment from leadership, not just configuration.
It may be the tool or the subscription if you genuinely need something your current HubSpot subscription doesn't include, such as features from a higher tier or a hub you don't have, or something HubSpot doesn't do at all. Check this carefully before concluding it: many "HubSpot can't do that" complaints turn out to be features that were never set up.
In our view, a true tool problem is the least common of the three. Most teams that switch CRMs without fixing their setup, data and ownership find the same problems waiting for them in the new system.
Answer yes or no for your own portal:
If you answered no to three or more, the setup needs attention. If most answers are no, it's worth a structured review before the habits of working around HubSpot set in further.
Fixing an existing portal follows a different order from a new implementation. You're working with live data and people who have already formed opinions about the system, so the aim is to restore trust quickly while fixing the causes underneath.
The order matters. Cleaning data before definitions are agreed means cleaning it again later; retraining before simplifying means teaching people a setup you're about to change.
Most portals can be fixed in place. A rebuild means redesigning the structure and migrating existing data, so it's worth it only when the foundations are wrong.
A portal improvement is usually enough when:
A rebuild is worth considering when:
Even a rebuild doesn't mean losing your history. A carefully planned rebuild maps existing data into the new structure, the same way a migration from another system would. Our CRM implementation roadmap explains how that process runs.
Woven is a HubSpot Diamond Solutions Partner in Singapore. When a team's HubSpot isn't working, we start with a health check of the portal, then advise your team on the data cleaning needed, rebuild pipelines, properties and workflows where needed, and retrain each team on the simpler setup, working within your existing HubSpot account. Your team usually carries out the data cleaning. Hands on data cleaning is generally outside our development scope unless separately agreed.
After that, our retainers keep the portal healthy with regular CRM health checks, automation updates, content updates and support for your admins and users. If your team has started working around HubSpot, book a HubSpot consultation and we'll help you work out whether it needs a portal improvement or a rebuild.
CRM implementations usually fail because the system doesn't match how the business works, the data isn't trusted, teams never agreed shared definitions, or nobody owns the CRM after launch. Training that happens only once and missing integrations make it worse. The software itself is rarely the main cause.
Yes. Fixing an existing HubSpot portal works with your current account and data. Woven advises your team on reviewing duplicates, correcting records and assigning owners while preserving important information and history. Your team usually carries out these updates and decides which outdated records to retain or remove. Hands on data cleaning is generally outside the development scope unless separately agreed. Even a full rebuild maps your existing data into the new structure.
Make HubSpot easier than the alternative. Have your team clean the data with guidance so people trust it, remove fields and steps they don't need, make sure new enquiries are assigned automatically, give leaders dashboards they rely on, and retrain each role on the simplified setup. Then name an owner who keeps it that way.
Usually not, unless you've confirmed you need something HubSpot can't do. Switching moves the same data, process and ownership problems into a new system. Fix the setup first; if a genuine gap remains, you'll then know exactly what the next system needs to do.
The scope depends on the condition of your portal, the pipelines, workflows and integrations that need attention, and the training your team needs. Woven starts with a health check and recommends the appropriate configuration changes, training and ongoing support. We also advise your team on the data cleaning required, which your team usually carries out. Hands on data cleaning is generally outside the development scope unless separately agreed.