How to safely clean up unused HubSpot properties

Updated 2026-11-22

Most HubSpot portals that are a few years old have hundreds of custom properties nobody can explain: lead_source_v2, webinar_q3_attended, mql_date_old. Cleaning them up makes forms, reports and imports easier, but deleting the wrong one can quietly break a workflow or a list. Here's a careful way to do it.

1. Start with fill rate

A property that is almost never filled is the safest candidate. In Settings → Properties, check each property's usage, or build a quick view or report counting records where the property is known. Sort your candidates by fill rate and last update. Properties below 1% fill with no recent writes go first.

2. Find every place the property is used

Fill rate isn't enough: an empty property can still be referenced by:

  • Workflows: enrollment triggers, branches, "set property" actions
  • Lists and segments: filters
  • Forms: hidden or visible fields
  • Reports and dashboards: filters, breakdowns
  • Sequences, templates and personalization tokens
  • Integrations that sync the field

HubSpot shows some of these dependencies on the property's details. Check each category above before archiving, especially workflow branches and report filters, which are easy to miss.

3. Export before you archive

Export the property's values (even sparse ones) together with record IDs, so you can restore them if someone needs the data later.

4. Archive in small batches

Archive 10–20 properties at a time, keep a short log (property, owner, date, reason), and wait a week before the next batch so anything that breaks shows up while the change is fresh.

5. Prevent the mess from returning

Agree on naming conventions and a description for every new property, and review new properties monthly.

We're building a tool for step 2

Disclosure: I'm building a read-only tool that maps every custom property to the exact workflows, lists, forms and reports that use it, with fill rates, so you can see each property's "blast radius" before archiving. It isn't live yet. There's an example report and an early-access list here: see the example.