Field notes
How to clean up a messy HubSpot CRM
Everyone starts by merging duplicates. That’s why the duplicates come back. Here’s the order that actually holds.
On this page
Most HubSpot cleanups start in the wrong place. Someone exports the contacts, finds four thousand duplicates, and starts merging. Two weeks later the duplicates are back and the export looks exactly the same.
The duplicates aren't the problem. They're a symptom. A messy CRM is almost never a data problem — it's a model problem, the shape of the thing underneath the data. Fix the shape and the data mostly cleans itself. Merge records without fixing the shape and you're mopping the floor with the tap still running.
Here's the order I actually work in, on every messy HubSpot I've inherited.
1. Map how the mess gets in
Before touching a single record, find the doors. Where does data enter HubSpot? Forms, imports, a Salesforce sync, a Zap someone built in 2023 and forgot, reps typing free text into fields that should be dropdowns. Every door is a place the mess regenerates. List them. Most teams have more than they think, and half of them nobody owns.
2. Kill the fields nobody uses
Open your properties. You'll find three hundred. You use forty. The other two hundred and sixty are half-filled, contradictory, and quietly wrong — and every one is another box a rep can put garbage in. Archive the dead ones. A field that isn't required and isn't reported on is just a liability with a label.
3. Fix the doors, then fix the data
Turn free text into dropdowns. Add validation to forms. Standardise the sync so two systems stop arguing about the same contact. Then dedupe — because now the duplicates stop coming back. Do it in that order or don't bother; deduping first is just scheduling the next cleanup.
4. Decide what "good" means, once
A lifecycle stage should mean the same thing to marketing and to sales. Usually it doesn't. "MQL" means "raised a hand" to one team and "has a pulse" to the other. Write the definitions down. Put them where people work — on the record, in the view — not in a doc nobody opens.
5. Govern it, or watch it rot
Clean data has a half-life. HubSpot's own data puts B2B decay at about 22.5% a year — a quarter of your database goes wrong in twelve months on its own. Without a weekly check — new duplicates, stale records, fields drifting out of format — you'll be back here in a quarter. The cleanup is the easy part. Keeping it clean is the actual job, and it's the part everyone skips. It's also most of what the ongoing work is.
The uncomfortable truth: most "messy HubSpot" was built on purpose, one reasonable-sounding request at a time. Someone needed a field. Someone needed a workflow. None of it was wrong on the day. It's wrong now.
You can clean a CRM in a weekend. Keeping it clean is what separates a system your team trusts from a database people quietly work around in spreadsheets. If the second one sounds familiar, the model's the problem — and the GTM diagnostic will tell you how deep it goes. Start there.
If your CRM is a database your team works around instead of a system they trust, that’s the work we do.
Get the next one
New field notes twice a month. We don’t do newsletters — follow RevOps XL on LinkedIn instead.
Follow on LinkedIn ↗