RevOps + HubSpot 8 min read

HubSpot build went wrong? How to rescue it

Most stalled HubSpot portals can be repaired in about 30 days. Fix access and licence first, then data, pipelines, workflows, reports and adoption, in that order.

Head of Client Success

Most stalled HubSpot implementations can be repaired without starting again. Work through the portal in a fixed order: who has admin access and who owns the account, what your licence tier actually includes against what you were promised, the state of your data, your pipelines, your workflows, your reports, and only then adoption. Each step depends on the one before it, so fixing reports before the data is clean just gives you wrong numbers faster.

Rebuild only when the data model itself is wrong: the objects, pipelines and properties do not match how you actually sell. If the structure is sound and the problems are broken workflows, messy records and a team that never got trained, repair it in place.

Use HubSpot support for "how does this feature work" and "is this a HubSpot bug". Use a partner, or your own admin, for anything that needs a decision about your business: how your pipeline should run, what should be automated, and who is accountable for it. Most portals can be back in daily use within 30 days if one named person owns the rescue.

What does a stalled HubSpot implementation look like?

On our discovery calls this year the story repeats. A partner, or HubSpot's own onboarding, built the portal, handed it over, and moved on.

One prospect we spoke with in October described their partner building workflows and handing them over with a "go and test it and use it", and no ongoing involvement. When the sales and revenue features did not do what they expected, the partner and HubSpot each pointed at the other over what the licence tier allowed. In their words, they were "caught in between".

Others told us the same thing in different shapes:

  • Paying for a lot, using a little. The subscription is Professional or Enterprise, and the team uses contacts, a deal board and email logging.
  • Activity outside the CRM. Deals are tracked in a spreadsheet, quotes go out from Word, and follow ups sit in personal inboxes.
  • Workflows nobody trusts. Something fires twice, or not at all, and nobody remembers why it was built.
  • Reports that start arguments. Sales and marketing each bring a different number to the same meeting.
  • The partner has gone. The person who built it has left, or the engagement ended and the knowledge went with them.

If two or more of those are true, you have a rescue on your hands. Our post on what a bad HubSpot implementation actually costs puts numbers on why it is worth doing now.

The triage order: seven checks, in this sequence

Do these in order. Each one takes between an hour and a day for a 50 to 250 person business.

StepWhat to checkWhere in HubSpotRed flag
1. Access and ownershipWho holds Super Admin, who holds billing permissions, which users have left the businessSettings, Users & TeamsThe only Super Admin is a former employee or the old partner
2. Licence against promisesWhich hubs, tiers and seats you pay for, and what was promised in the original proposalAccount & Billing, Overview and SubscriptionsA feature you were sold needs a tier or seat type you do not have
3. DataDuplicates, blank owners, companies with no contacts, lifecycle stages that never changeContacts and Companies, Manage duplicatesThousands of duplicate pairs, or most records with no owner
4. PipelinesStages match how deals actually move, required fields at each stage, deals that have not moved in 90 daysSettings, Objects, Deals, PipelinesStages named after the partner's template, or 40% of open deals stale
5. WorkflowsWhat is on, what errors, what nobody can explainWorkflows dashboard, Review automation issuesLive workflows with errors, or two workflows editing the same property
6. ReportsWhich dashboards the leadership team actually opens, and whether the numbers match financeReporting, DashboardsRevenue in HubSpot does not match the invoices in your accounting system
7. AdoptionWho logs in, who logs activity, where the work actually happensUsers & Teams, activity reportsReps work from spreadsheets and update HubSpot on Friday afternoons

Access comes first because you cannot fix anything you cannot open. If the only Super Admin is the old partner, add a second Super Admin from inside your business before you do anything else, then remove or downgrade the partner's user.

The licence check is where the blame game usually ends. Open Account & Billing and write down every hub, its tier and its seat count. Then put the original proposal next to it. HubSpot now sells seats by type: a Core seat gives the core features of what you bought, and a Sales seat gives the full Sales Hub Professional or Enterprise feature set. If a rep only has a Core seat, some sales tools will not be there for them, however the workflows were built. HubSpot also notes that removing a seat from a user does not stop the billing: you have to remove the unassigned seat as well.

Data before pipelines, pipelines before workflows. Workflows act on records and stages. If records are duplicated and stages are wrong, every automation you fix will do the wrong thing reliably. HubSpot's duplicate management tool, on Professional and Enterprise, compares contacts on name, email, phone and company, and companies on domain and name. Our adoption audit you can run yourself covers step 7 in more detail.

Not sure which step your portal is stuck on?

We will look at it with you and tell you where to start.

Rebuild or repair: how do you tell?

A rebuild costs more, takes longer and tests your team's patience. Most of the time a repair is the right call. Here is how we decide:

Repair it in place whenRebuild when
Your pipeline stages are roughly right and need renaming or tighteningYou sell in ways the pipelines cannot represent, for example projects, renewals and one-off sales all forced into one pipeline
Data is messy but the properties existKey information is in free text notes or the wrong object, so no report can ever use it
A handful of workflows misfireDozens of workflows overlap, nobody can explain them, and turning one off breaks three others
Integrations sync the right objects with some field errorsThe integration syncs the wrong objects or the wrong direction, and history is corrupted
The team never got trainedThe team was trained on a process the business no longer runs

Even a rebuild rarely means a new portal. It usually means a new pipeline and property set inside the same portal, migrating records across, then archiving the old structure. You keep your contact history, email engagement and attribution.

This video from our YouTube channel walks through the first ten things to do when setting up a HubSpot CRM.

HubSpot CRM setup guide 2026: the first 10 things you must do, from our YouTube channel. Watch it on YouTube.

What to ask HubSpot support, and what to ask a partner

This is the question that leaves people "caught in between". HubSpot publishes its scope of support, and it is clearer than most people realise.

HubSpot support gives full help with how the software works, troubleshooting HubSpot software issues, and advice on using HubSpot to reach your goals. It is limited on custom code: it will not write or edit it, and if your code is at fault it will send you back to the developer. For third-party integrations, HubSpot says support has no visibility and you should contact the app's builder. Chat and email support come with Starter and above, and phone support with Professional and Enterprise. On accounts created from March 2024, the person asking needs an assigned Core, Sales or Service seat.

  • Ask HubSpot support: "Is this feature included in our tier and seat type?", "Why did this workflow action error?", "Is this a bug?" Ask for the answer in writing.
  • Ask a partner or your own admin: "How should our pipeline be set up for how we sell?", "Which of these 60 workflows should we keep?", "Why does our revenue report not match finance?", anything involving custom code or a third-party integration they built.

The fastest way out of a blame loop is a written answer from HubSpot on what your licence includes. Once that is settled, the partner has a clear brief. If your current partner cannot or will not take it on, our guide to switching HubSpot partners without losing momentum covers the handover, and the 9 types of HubSpot onboarding partners helps you work out which kind you had and which kind you need.

Two kinds of question, two places to take them
Which questions go to HubSpot support and which go to a partner or your own adminA portal problem is either a software question or a business decision. Software questions, such as how a feature works, whether something is a bug, or what your tier and seat include, go to HubSpot support, with the answer in writing. Business decisions, such as how the pipeline should run, which workflows to keep, custom code and built integrations, go to a partner or your own admin. The written answer from support becomes the partner brief. A portal problemsort it into oneof two kinds first Software questionhow does this feature work?is this a HubSpot bug?does our tier and seat include it? Business decisionhow should our pipeline run?which workflows do we keep?custom code or a built integration HubSpot supportanswers how the software worksget the answer in writing Partner or your adminmakes the setup decisionswith a clear brief

Based on HubSpot's published scope of support. The written answer on your licence is what gives the partner a clear brief.

A 30-day rescue plan

Name one person inside the business who owns this. They need about four hours a week, plus an hour a week from each sales and marketing lead.

WeekFocusDone means
1Access, licence, and a list of what is brokenTwo internal Super Admins, a written record of hubs, tiers and seats, a written answer from HubSpot on any disputed feature, and a ranked list of problems from the triage table
2Data and pipelinesDuplicates merged, every open deal and active contact has an owner, pipeline stages match how you sell, stale deals closed out
3Workflows and reportsEvery live workflow has an owner and a one-line purpose, workflows with errors fixed or turned off, one leadership dashboard whose revenue figure matches finance
4AdoptionSpreadsheets retired, a 45-minute training per team on the process as it now works, and a weekly check on who is logging activity

Turn workflows off before you delete them. Leave them off for a fortnight and see if anyone notices. If nobody does, archive them.

Four weeks, one focus a week, back in daily use
  1. Week 1Two internal Super Admins, every hub, tier and seat written down, and HubSpot's answer in writing on any disputed feature.
  2. Week 2Duplicates merged, an owner on every open deal and active contact, and pipeline stages that match how you sell.
  3. Week 3Every live workflow has an owner and a purpose, errors fixed or switched off, and one leadership dashboard that agrees with finance.
  4. Week 4Spreadsheets retired, a 45-minute training per team, and a weekly check on who is logging activity.

The 30-day plan above, for a 50 to 250 person business with one named owner giving about four hours a week.

Keep a simple change log: date, what changed, who changed it, why. The single biggest reason portals stall a second time is that nobody can explain the last round of changes.

How do you stop it stalling again?

Implementations stall after handover because a portal needs ongoing decisions and nobody was given the job of making them. Three things keep it moving:

  • An internal owner with time in their week. They decide what gets built, and they say no to new properties nobody will report on.
  • A monthly review against the numbers leadership uses. If a dashboard has not been opened in a month, either fix it or delete it.
  • Someone to call when it breaks. An in-house admin, or a monthly partnership with a partner who knows your portal.

Frequently asked questions

Can a failed HubSpot implementation be fixed without starting again? Usually, yes. If your pipelines and properties roughly match how you sell, repair the data, workflows and reports in place. Rebuild only when the data model cannot represent how your business works.

Will HubSpot support fix our portal setup? HubSpot support helps with how features work, software troubleshooting and advice on using HubSpot. It will not write or edit custom code, and it has no visibility into third-party integrations, so setup decisions and custom builds sit with a partner or your own admin.

Why can my sales team not use features we were promised? Often it is the tier or seat type. HubSpot sells Core, Sales and Service seats, and some Sales Hub Professional or Enterprise features need a Sales seat. Check Account & Billing against your original proposal.

How long does a HubSpot rescue take? For a 50 to 250 person business with a sound structure, about 30 days: access and licence in week one, data and pipelines in week two, workflows and reports in week three, and training in week four.

What should we do first if our HubSpot partner has left? Make sure at least two people inside your business have Super Admin access, then remove or downgrade the old partner's user. Nothing else can be fixed safely until you control the account.

Sources


Want a second pair of eyes on a portal that has stalled? See our RevOps and HubSpot work and HubSpot implementation, or talk to us.

Is your portal worth repairing, or does it need a rebuild?

Book a short call and we will tell you which, and where to start.

Neighbourhood

Neighbourhood is a HubSpot Diamond Partner in Brisbane. We build AI systems and the revenue operations they run on, for businesses across Australia and New Zealand.