dx0
← All articles

HubSpot

You inherited a messy HubSpot account. Here's what to do first.

Pablo Gonzalez

Pablo Gonzalez

Founder, dx0 · Author of Clean Apex Code

Published · 6 min read

A tangled pile of black cables and plugs on a white surface.

You just took over HubSpot.

The previous admin left. There are hundreds of workflows, custom properties nobody can explain, and integrations with applications you didn't even know the company was using.

Some things work. Others don't. And nobody seems to know why certain decisions were made.

Meanwhile, your sales and marketing teams are already asking for changes.

Where do you even start?

The good news is that you probably don't need to rebuild everything. But you do need to understand what you've inherited before you start changing it.

Here's how we'd approach it.

1. Don't start cleaning things up

Your first instinct might be to delete old workflows, merge duplicate properties, or reorganize everything.

Don't. At least not yet.

That workflow called "Old Lead Assignment - DO NOT TOUCH" might look like something you can safely remove. But what if it's still assigning leads from a form that only gets used twice a month?

Or perhaps there's a custom property called "Customer Type 2" that nobody remembers creating. It might be used by an integration that sends customer information to your billing system.

Just because something looks unnecessary doesn't mean it is.

Your first job is to understand what exists, not to fix it.

2. Find out what's actually running

Start by making an inventory of your HubSpot account.

You want to understand:

  • Workflows: Which ones are active? What triggers them? What properties do they update?
  • Properties: What custom fields exist? Which ones are still being used?
  • Pipelines: How are deals and tickets moving through the business?
  • Users: Who has access? Are former employees or agencies still active?
  • Integrations: What other applications are connected to HubSpot?
  • Reports: Which dashboards does the business depend on?

HubSpot has built-in tools to help with this. You can review workflows, property usage, connected apps, and data quality from within your account.

But don't spend weeks trying to document every single setting.

Start with the things that matter to the business. Lead assignment, deal creation, lifecycle stages, customer onboarding, and anything that moves data between systems.

These are the areas where an unexpected change can cause real problems.

3. Understand how HubSpot connects to everything else

This is where things usually get more complicated.

HubSpot rarely works alone.

Your company might use Salesforce for sales, HubSpot for marketing, Zapier for automations, and Workato to connect other business applications.

Now imagine someone asks you to change how leads are assigned.

You find a HubSpot workflow that looks responsible. Easy enough.

But what if Salesforce is also updating the lead owner? Or a Zapier automation changes a property after a form submission?

You could spend hours investigating HubSpot and still miss the thing that's actually causing the problem.

Understanding HubSpot isn't enough. You need to understand how HubSpot works with the rest of your systems.

For each important integration, try to answer three questions:

  1. What data moves between these applications?
  2. Which application is responsible for updating it?
  3. What would happen if we changed or removed this connection?

If nobody knows the answers, that's something you need to investigate before making changes.

4. Find the people who know why things were built

Not everything can be explained by looking at configuration.

Sometimes a workflow looks unnecessarily complicated because it was built around a business requirement that no longer exists.

Other times, that strange setup is the only thing preventing an important process from breaking.

Talk to the people who use HubSpot every day.

Ask your sales team how leads get assigned. Ask marketing how contacts move through their campaigns. Ask finance how customer information reaches their systems.

And if the previous admin or implementation partner is still available, ask them about the decisions that aren't documented.

The goal isn't to interview everyone in the company.

It's to find the missing information that you can't get from the system itself.

Then write it down somewhere your team can find it.

5. Pick one problem and trace it from start to finish

You don't need to understand every corner of HubSpot before you can start improving things.

Pick a real problem that people are already complaining about.

For example:

"Why are some leads being assigned to the wrong salespeople?"

Now investigate the whole process.

Where do these leads come from? Which properties determine ownership? What workflows update those properties? Are any integrations involved?

Follow the process until you can explain what's happening.

You'll probably discover other things along the way. Maybe two workflows are updating the same property. Maybe an old integration is still active. Maybe the original lead assignment rules were never updated after a team restructure.

That's useful information.

Document what you find, fix the problem, and move on to the next one.

This approach is much more manageable than trying to clean up the entire account in one go.

6. Make sure you can understand the impact of changes

Eventually, someone will ask you to make a change that sounds simple.

"Can we remove this property?"

"Can we change how deals are created?"

"Can we stop syncing these contacts to Salesforce?"

The hard part isn't always making the change.

It's knowing what else might break.

Before changing an important property or workflow, check where it's used. Look at other workflows, forms, lists, reports, and connected applications.

If you're not sure what depends on something, don't assume it's safe to remove.

And make sure your team can repeat that investigation the next time someone asks for a change.

You shouldn't have to spend half a day investigating the same setup every time.

7. Use tools to make the investigation easier

HubSpot has useful tools for understanding your account. But investigating a large environment manually can still take a lot of time, especially when multiple applications are involved.

This is one of the reasons we built dx0.

dx0 connects to business applications like HubSpot, Salesforce, Zapier, and Workato, and helps your team understand how they're configured and connected.

Instead of opening dozens of workflows and settings pages, you can search across your systems, investigate dependencies, and understand where things are used.

You can also use dx0 with Claude, giving it context about your actual business systems instead of asking it to guess how they're configured.

That matters when you're responsible for an environment built by people who are no longer around.

You still need to decide what to change. But you can spend less time finding out how everything works.

8. Document what you learn as you go

Once you've started understanding your HubSpot account, don't let that knowledge disappear again.

You don't need a 200-page document explaining every workflow.

Start with the important things:

  • What each major business process does.
  • Which applications are involved.
  • Who owns each process.
  • Why important customizations exist.
  • What needs to be checked before making changes.

Keep this information somewhere your team can access and update.

Otherwise, you'll eventually end up in exactly the same situation as the person who inherited the account before you.

You don't need to fix everything today

Inheriting a messy HubSpot account can feel overwhelming, especially when the business expects you to start delivering changes immediately.

But remember that the account probably took years to become this complicated.

You're not going to understand everything in a week.

Start with the important processes. Find out what's running. Understand the integrations. Document what you learn.

And most importantly, don't make changes until you understand what depends on them.

The goal isn't to have a perfectly clean HubSpot account. It's to have a system your team understands well enough to change safely.

If you've inherited HubSpot, Salesforce, or a collection of business applications that nobody fully understands, take a look at dx0.

We built it for exactly this problem.

Are you dealing with complex business systems?

See what we can do