Too many custom properties in HubSpot

Why it matters

Every extra property is another option in every filter, report builder, workflow action and import mapping. Users pick the wrong field, reports disagree, and new team members cannot tell which field is the real one.

Names such as test, old, backup or do not use are a sign that a past cleanup was started and never finished. Those fields can still feed workflows or integrations, which is why they need a careful review rather than a bulk delete.

How to find it in HubSpot

1. 1In Settings, open Properties and choose an object, such as Contacts.
2. 2Filter to custom properties only, if your portal shows that option, and note the total.
3. 3Search for words such as test, temp, old, copy, backup, deprecated and do not use.
4. 4Open each candidate and check where it is used. HubSpot shows dependencies, such as workflows, forms, lists and reports, for many properties.
5. 5Repeat for companies, deals and tickets.

How to fix it safely

1. 1Agree an owner for the property schema, usually a HubSpot admin or RevOps lead.
2. 2For each candidate, remove it from workflows, forms, lists, reports and integration mappings first.
3. 3Archive the property rather than deleting it outright, so you can restore it if something breaks.
4. 4Write a short rule for new properties: a clear name, a description, an owner and a reason. See the page on custom properties without a description.

Before you change anything: Integrations often write to properties that no workflow or report uses. Check with whoever owns each integration before you archive a field.

How Ancil checks this

Rule

ARCH-002

What it looks for

Counts active custom properties across the objects Ancil reads. It only runs when there are at least 80. It flags the portal when there are 250 or more custom properties, or when at least 5 have a name, label or description containing words such as test, temp, old, delete, unused, deprecated, backup, copy, do not use or ignore, or an internal name ending in _old.

Severity

Info. Warning at 500 or more custom properties, or 20 or more cleanup candidates.

Evidence shown

The custom property count, plus the object, internal name and label of up to 50 cleanup candidates.

Governed fix

Not automated. Ancil reports the evidence only. Your team, or an INSIDEA expert, reviews and archives properties. Ancil does not change property definitions automatically.

Related checks