Platform module
Properties & Data Architecture
9 automated checks across contact, company, and deal properties for unused fields, naming issues, and configuration problems.
Audit results
9 checks · live
Unused properties
47 contact properties haven't been written to in 6+ months.
Naming convention issues
Inconsistent naming detected: 'Lead_Source', 'lead_source', and 'leadSource' coexist.
Missing field options
3 dropdown properties have orphaned values used by contacts but missing from the option list.
+6 more findings
Why does property architecture matter?
Property sprawl is one of the most common HubSpot problems. Unused fields clutter forms and views. Inconsistent naming makes automation fragile. Missing field options break dropdown-dependent workflows. Keeping properties clean is the foundation of everything else.
Sample findings
Examples from a real properties audit
Every check produces a finding with severity, an impact estimate, and a step-by-step fix.
Unused properties
47 contact properties haven't been written to in 6+ months.
Estimated Impact
Property sprawl cluttering forms, views, and workflow editors.
Solution
Archive unused properties or hide them from forms and views.
Naming convention issues
Inconsistent naming detected: 'Lead_Source', 'lead_source', and 'leadSource' coexist.
Estimated Impact
Automation fragility from inconsistent property references.
Solution
Standardize on snake_case across all custom properties.
Missing field options
3 dropdown properties have orphaned values used by contacts but missing from the option list.
Estimated Impact
Reporting bucketing breaks for orphaned values.
Solution
Add the missing options or migrate orphaned contacts to valid values.
All 9 checks in this module
Featured findings above are 3 of the most impactful. Here's the complete list.
Questions
Properties audit questions
How do I clean up unused HubSpot properties?
Identify fill rate before deleting anything. A property with no values across your database is safe to archive; a property with low fill that automation reads is not. RevTrace reports fill rate per property along with whether it is referenced by any workflow, form, or report, so you can archive without breaking something downstream.
How many custom properties is too many in HubSpot?
There is no hard number — the problem is unused properties rather than total count. Property sprawl shows up as cluttered record views, forms nobody can navigate, and automation that references fields no one maintains. The practical test is what share of your properties have meaningful fill rates.
Why do property naming conventions matter?
Inconsistent names make automation fragile and reporting ambiguous. When you have both Industry and industry_type with different values, every workflow and report has to pick one, and different teams pick differently — which is how two dashboards end up disagreeing. RevTrace flags naming inconsistencies and near-duplicate properties.
Properties module
9
automated checks
Ready to audit your HubSpot?
Connect your portal, run your first audit, and get actionable fixes in under ten minutes.
Start Free Audit