Tag: data hygiene

  • How to Clean Up HubSpot Data: A Step-by-Step Guide

    HubSpot data cleanup is the process of auditing your CRM, backing it up, fixing properties and formats, merging duplicates, filling gaps, tidying lists and deals, and putting rules in place so bad data stops coming in. Done in that order, it turns a CRM people work around into one they trust.

    You probably know the symptoms. The same company appears three times with different spellings. Half your contacts have no owner or lifecycle stage. Reports disagree with each other, lead scores look random, and reps keep a private spreadsheet because they don’t trust the CRM. Almost every other RevOps project, from forecasting to attribution to automation, depends on getting this right.

    This guide walks through a practical cleanup sequence, with the HubSpot tools that help at each step.

    Before you start: define clean and protect yourself

    “Clean” means different things to different teams, so decide what you’re fixing. Pick the ten or so fields that drive decisions, such as lifecycle stage, owner, lead source, industry, company size, country, email, deal amount, close date, and closed-lost reason. Then name one owner for the project and agree with sales and marketing on a quiet window, so people aren’t editing records while you merge them.

    Also be careful with irreversible actions. In HubSpot, merged records cannot be reverted, so treat every merge as final. You can roll back rejected duplicate pairs for a limited time, but not merges. A backup is your safety net.

    Step 1: Audit what you have

    Start with HubSpot’s data quality tools, found under Data Management, then Data Quality. The overview page summarizes duplicate issues, formatting issues, and enrichment gaps, and the property insights show where properties are unused, empty, or duplicated. Set up the weekly data quality digest while you’re there, so changes show up in your inbox. Then build your own scorecard.

    Check How to find it Why it matters
    Duplicate contacts and companies Manage duplicates tool, plus exports Splits history, inflates counts, breaks reports
    Contacts with no owner or lifecycle stage A saved filter or list Leads go unworked; funnel reports are wrong
    Contacts with no company association A filter on associated company Account-level reporting and scoring fail
    Formatting problems Data quality formatting issues Breaks segmentation and personalization
    Empty key fields Property insights and filtered views Lead scoring and routing lack inputs
    Unused or duplicate properties Property insights Clutter and confusion
    Stale deals Open deals with past close dates Inflates pipeline and distorts the forecast

    Step 2: Back up before you change anything

    Export contacts, companies, deals, and any other objects you plan to touch, including the properties you’ll edit. Record the counts for each object. Export your lists and workflows’ configuration notes too, since you’ll want to know what depends on what. Store the files somewhere the team can find them, and keep them until the cleanup has been validated.

    Step 3: Fix the structure first

    Cleaning records before fixing the properties underneath them means doing the job twice. Review your properties for these issues:

    • Free text where a dropdown belongs. “USA,” “U.S.,” and “United States” are the same value to a human and three values to a report.
    • Duplicate or overlapping properties, such as two fields for lead source.
    • Unused properties with no data and no dependencies.
    • Unclear names and missing descriptions, which lead people to guess.

    Before you delete or merge any property, check where it’s used in workflows, lists, forms, and reports. For guidance on when to create your own, see our explanation of custom vs. default properties.

    Step 4: Standardize formats and values

    The data quality tool flags formatting issues, such as a name stored as “LORELAI GILMORE” that should read “Lorelai Gilmore,” and you can accept or reject its suggestions individually or in bulk on eligible plans. Data Hub Professional and Enterprise also let you set automation so new records with the same issue are fixed automatically. One caveat from HubSpot’s documentation: if a record is later overwritten, for example by an API or integration, with the same bad format, the tool may not flag it again, so fix the source too.

    For values that need consolidating, such as country names, industries, and job titles, use bulk edit or a cleaned import file to map the variants to one standard value. Then change the property to a dropdown so the problem doesn’t return.

    Step 5: Deduplicate carefully

    HubSpot’s duplicates manager compares record properties and surfaces likely pairs, with a daily scan. By default, contacts are compared on properties like name, email, phone, and company name, and companies on domain, name, country, and similar fields. Eligible plans can create custom rules with their own matching criteria. Work in this order:

    1. Companies first. Merging companies consolidates the contacts and deals attached to them, which makes later contact merges cleaner.
    2. Contacts next. Email is the usual unique identifier.
    3. Deals last, reviewing any that look like repeats of the same opportunity.

    Test on a small batch and review associated records before you merge in bulk. Use the similarity score to prioritize, and when you reject a pair, remember that it won’t reappear unless one of the records changes. Decide your merge rule in advance, such as keeping the record with the most recent engagement or the oldest create date, so you keep the best data and the original source.

    Step 6: Fill the gaps

    • Owners: assign owners to unowned records, using routing rules where possible.
    • Lifecycle stage: fix blanks and wrong values, using your agreed definitions. Our guide to HubSpot lifecycle stages explains the rules and the forward-only behavior to plan around.
    • Company associations: associate orphaned contacts with companies, by domain where it’s reliable.
    • Enrichment: the data quality tool shows enrichment coverage by property, which helps you see which fields enrichment can fill.
    • Required fields: make the key fields required on forms and, where your plan supports it, on deals.

    Step 7: Clean your lists, contacts, and deals

    Lists. Audit your lists for stale static lists, duplicates, and unused ones. Consider whether a static list should be an active one that updates itself, and check dependencies before deleting. Our post on active vs. static lists covers when to use each.

    Contacts. Review hard bounces, unsubscribes, and long-unengaged contacts. If you pay by marketing contacts, setting unengaged ones to non-marketing can reduce cost, and archiving or deleting old records should follow your retention and consent policy.

    Deals. Find open deals with past close dates, no amount, or inactive owners, and close, update, or reassign them. Make closed-lost reason a required dropdown. See our guide to HubSpot deal stages for the stage rules that keep pipelines honest, and deal slippage for why stale close dates matter.

    Step 8: Recheck scoring, routing, and reports

    Cleaning changes the inputs to your automation. After the cleanup, review your lead scoring model, since fit scores depend on filled-in fields like industry and company size. Retest routing rules, and spot-check key reports against your pre-cleanup exports. If you’re also planning a platform move, finish the cleanup first, as our Salesforce to HubSpot migration checklist explains.

    A before-and-after snapshot

    Track a handful of measures so you can show the result. These numbers are illustrative.

    Measure Before After 30 days
    Duplicate contact pairs 4,100 150
    Contacts with no owner 9,800 600
    Contacts with no lifecycle stage 12,500 1,200
    Companies missing industry 35% 12%
    Open deals with past close dates 240 20
    Unused properties 112 of 380 20 of 270

    Step 9: Stop the mess from coming back

    • Prevent at the source. Use dropdowns, required form fields, and validation instead of free text.
    • Automate formatting on new records, where your plan allows.
    • Control imports. Use a checklist: clean the file, match on a unique identifier, map fields deliberately, and test a small batch.
    • Review integrations. Check which system writes each field and whether syncs create duplicates.
    • Limit who can create properties and edit key fields.
    • Keep a data dictionary with each property’s meaning, owner, and allowed values.
    • Review quarterly. Use the data quality digest and add the check to your RevOps meeting cadence.

    Mistakes to avoid

    • Merging in bulk with no backup and no test batch
    • Cleaning records before fixing properties and dropdowns
    • Deleting properties or lists that workflows and reports still use
    • Fixing formats in HubSpot while an integration keeps writing bad values
    • Running the cleanup during active campaigns or pipeline reviews
    • Treating it as a one-time project with no owner
    • Deleting contacts without checking consent and retention rules

    Summary

    HubSpot data cleanup works best in a fixed order: define what clean means, audit with the data quality tools, back up, fix properties and dropdowns, standardize formats, deduplicate companies then contacts then deals, fill gaps in owners, lifecycle stages, and associations, clean lists, contacts, and deals, and then recheck scoring, routing, and reports. Because merges can’t be undone, test small batches and keep exports.

    The cleanup only lasts if you prevent the mess at the source with dropdowns, required fields, automated formatting, import controls, integration reviews, and a data dictionary, then review the results every quarter. Track a few before-and-after measures so the effort is visible.

    FAQ

    What is HubSpot data cleanup?

    It’s the process of auditing and fixing your CRM data: merging duplicates, standardizing formats, filling gaps, tidying lists and deals, and adding rules so errors don’t come back.

    Can I undo a merge in HubSpot?

    No. Merged records cannot be reverted. You can undo a rejected duplicate pair for a limited time, so back up and test on a small batch before merging in bulk.

    Where are HubSpot’s data quality tools?

    Under Data Management, then Data Quality. They cover duplicates, formatting issues, enrichment, and property insights. Some capabilities, such as custom duplicate rules and formatting automation, require Data Hub Professional or Enterprise.

    How does HubSpot find duplicates?

    It compares property values on a regular scan, such as email, name, and phone for contacts and domain, name, and country for companies, and assigns similarity scores. Eligible plans can create custom matching rules.

    How often should we clean our HubSpot data?

    Run a full review at least quarterly, and use the weekly data quality digest and automation to catch issues in between. After a migration, a large import, or a new integration, check sooner.

    Should I delete or keep old contacts?

    It depends on your retention and consent policies and applicable privacy rules. Many teams suppress or set unengaged contacts to non-marketing first, then delete according to a documented policy. Check with legal if unsure.

    Do I need to clean data before migrating or adding AI tools?

    Yes. Migrations, scoring, and AI features all inherit the quality of the data underneath them, so cleanup first is cheaper than fixing the same problems in a new system.

    Who should own data quality?

    Usually RevOps owns the standards, tooling, and reviews, while sales, marketing, and customer success own the accuracy of the data they enter. Name one accountable person.

  • HubSpot Custom Properties vs Default: When to Add One

    A HubSpot property is just a field on a record, like Email or Deal Amount. Default properties ship with the CRM out of the box. Custom properties are ones you build yourself. The rule of thumb: use a default property if it already captures what you need, and only create a custom one when there’s a genuine gap in what HubSpot gives you.

    If you’ve ever stared at the “Create property” button in HubSpot and wondered whether you actually need it, you’re not alone. New admins tend to swing one of two ways: they either never touch properties at all, or they go overboard and build a custom field for every little thing the sales team asks for. Neither approach ends well.

    This post breaks down the actual difference between default and custom properties, gives you a simple framework for deciding when a new one is warranted, and shows you the mess that happens when teams skip that step.

    What’s the difference between a default property and a custom property?

    A property in HubSpot is a data field attached to a record, whether that’s a contact, company, deal, or ticket. Think of a contact record like a form: Name, Email, and Phone are all separate fields, and each field is a property.

    Default properties (sometimes called standard properties) are pre-built by HubSpot and come with every account. They cover the basics: contact name, email address, phone number, company name, deal stage, and so on. The contacts object alone ships with more than 160 of these built-in fields, and companies, deals, and tickets each have their own sets on top of that.

    Custom properties are fields you create yourself to store information HubSpot doesn’t already track. Say you sell industrial equipment and need to log which certification a customer’s facility holds. There’s no default field for that, so you’d build a custom property to capture it.

    Here’s the part people miss: you can’t delete or edit a default property’s core behavior. You can edit some things, like the dropdown options on a picklist, but the underlying field itself stays put. If you want a cleaner version of an existing field (say, a dropdown instead of free text), you’re usually building a custom property alongside it, not replacing the default one.

    It’s worth being specific about what “can’t edit the core behavior” actually means in practice, since it trips people up. You can rename a default property’s label, move it to a different property group, and adjust certain field-level settings. What you can’t do is change its underlying field type (turning a free-text field into a number field, for instance) or delete it outright, even if your team never uses it. That permanence is exactly why checking before you build matters so much, a custom property you regret creating is far easier to walk back than a default one you’re stuck with forever.

    Why does the distinction actually matter?

    It matters because default and custom properties don’t play the same role in your CRM. Default fields are what most of HubSpot’s native reporting, workflows, and integrations expect to see. When you build a parallel custom field instead of using the one that’s already there, you split your data across two places and nobody’s quite sure which one is “correct.”

    That’s how property sprawl happens. It’s rarely a case of teams needing more features. Most of the time, it’s someone creating a new field before checking what already exists in the portal.

    Honestly, most of the CRM messes I’ve seen in these situations aren’t a properties problem at all, they’re a “nobody checked first” problem. A rep needed to track something, didn’t know a field for it already existed, and created a duplicate. Multiply that across a sales team for a year and you’ve got a properties list nobody trusts.

    The fix isn’t more governance software. It’s a five-minute habit: search the existing property list before you build anything new.

    Property sprawl also tends to compound in a specific, predictable way, which is worth understanding so you can spot it early. The first duplicate field rarely causes any visible problem, one rep uses it, nobody else notices. The damage shows up months later, once a report or workflow was built referencing the “wrong” one of the two fields, and now half your contacts have data in the field the report ignores. Untangling that after the fact means auditing every record, deciding which field actually holds the correct data, and migrating values, a cleanup job that’s entirely avoidable if someone had just searched the property list first.

    When should you actually create a custom property?

    Here’s a simple framework. Ask these questions in order before you hit “Create property.”

    1. Does a default property already capture this? Search the property list for the object (contact, company, deal, or ticket) first. If it’s there, use it instead of duplicating it.
    2. Is the default field the wrong format, not missing entirely? If the data exists but as free text when you need a dropdown, that’s an editing job, not necessarily a new-property job. You can often adjust the field type or the picklist options on many default properties without building a duplicate.
    3. Is this data unique to how your business operates? Things like a renewal date tied to your specific contract terms, a product tier that only your company sells, or an internal lead score your team built are all fair game for a custom property.
    4. Will this field feed a report, workflow, or segmentation you actually plan to use? If you can’t name the report or automation that will use this data, you probably don’t need the field yet.
    5. Have you checked with other teams who touch this object? A field that makes sense to sales might duplicate something marketing already tracks under a different name.

    If you get through all five and there’s still a genuine gap, go ahead and build the custom property.

    Pro tip: before creating a picklist-style custom property, check whether the default version of that field already exists with different options. Editing the existing dropdown to match your business (say, trimming HubSpot’s long default industry list down to the five or six industries you actually sell into) is usually faster and cleaner than building a parallel custom field.

    Question four deserves a bit more weight than the others, since it’s the one most often skipped in practice. It’s tempting to create a field because it feels like useful information to have on hand, even without a specific report or workflow in mind yet. The problem is that “might be useful someday” fields are exactly the ones that sit empty, half-filled, or forgotten a year later, cluttering the property list for everyone else without ever earning their keep. If you genuinely can’t name what will use the data, it’s usually fine to wait until the actual need shows up.

    What are the technical limits on custom properties?

    HubSpot caps how many custom properties you can create, and the limit depends on your subscription tier. If you’re not sure which tier your company is on or should be on, it’s worth reading through a comparison of HubSpot’s Free, Starter, and Professional tiers before you commit to a properties strategy, since the tier you’re on affects what you can build.

    Free accounts are capped at a small number of custom properties, while paid Professional and Enterprise plans allow far more per object. That ceiling exists for a reason: HubSpot wants you to actually use the fields you create, not hoard them.

    Dropdown-style (enumeration) properties also have their own internal limit on how many options a single field can hold. If you’re building a picklist with thousands of options, you’ll eventually hit that ceiling too.

    These limits matter more for growing teams than they might initially seem to. A company that starts with a handful of custom fields on a Free or Starter plan can hit its ceiling surprisingly fast once multiple teams start adding properties independently, which is yet another reason the “search before you build” habit pays off, since every unnecessary duplicate field is also quietly eating into a limited, finite budget of properties you’re allowed to create.

    A quick checklist before you create a new property

    • Searched the existing property list for this object and confirmed nothing similar exists
    • Named the specific report, workflow, or segment this new field will support
    • Picked the right field type (single-line text, dropdown, number, date, etc.) instead of defaulting to free text
    • Written a short description so other users know what the field is for
    • Confirmed with any other team that touches this object that they don’t already track this somewhere else
    • Assigned the property to a logical group instead of leaving it uncategorized

    Properties feed directly into automation, so once you’ve got your fields sorted, it’s worth understanding how a HubSpot workflow actually uses that data to trigger emails, tasks, or updates. A clean property setup is what makes those workflows reliable instead of flaky.

    Worth adding to that same checklist habit: revisit your property list periodically, not just at the moment of creating something new. A quarterly pass through each object’s property group, checking for fields that have sat empty for months or clearly duplicate another field under a slightly different name, catches the sprawl that accumulates even when everyone individually followed the checklist above in the moment.

    Summary

    Default HubSpot properties ship with every account, over 160 on the contacts object alone, and can’t be deleted or have their core field type changed, though you can edit things like dropdown options. Custom properties exist to fill genuine gaps, data unique to your business that no default field captures, but creating one before checking whether a default property already covers it is the single biggest cause of property sprawl and the “messy CRM” complaints that follow.

    The five-question framework, checking for an existing default field, confirming it’s a format problem rather than a missing field, verifying the data is genuinely unique to your business, naming the specific report or workflow that will use it, and checking with other teams first, catches most unnecessary custom properties before they’re built. HubSpot’s per-tier limits on custom properties make this habit matter even more for growing teams, since every unnecessary duplicate field eats into a finite budget shared across the whole organization.

    FAQ

    Can I delete a default HubSpot property I don’t like?

    No. Default properties can’t be deleted or fundamentally changed, though you can often edit dropdown options or move them into a different property group to reduce clutter.

    How many custom properties can I create in HubSpot?

    It depends on your plan. Free accounts have a much smaller cap than paid Professional and Enterprise accounts, which allow up to 1,000 custom properties per object.

    What happens if two teams create separate custom properties for the same data?

    You end up with duplicate, half-filled fields and reports that don’t match. This is the single biggest cause of “messy CRM” complaints, and it’s almost always solved by checking existing properties before building new ones, not by adding more fields.

    Should I use a custom property or a custom object?

    A custom property adds a new field to an existing record type like contacts or deals. A custom object creates an entirely new type of record with its own properties and pipeline logic, and it requires an Enterprise-tier subscription. Most beginner use cases only need a custom property.

    Is it ever okay to create a custom property that duplicates a default one?

    Sometimes, but only when the default field’s format genuinely doesn’t work for you and can’t be edited to fit. Even then, name the custom version clearly so your team knows which field is the one to trust.