Why Property Bloat Matters
Most HubSpot portals accumulate hundreds of unused properties over time. We've seen portals with 400+ contact properties where fewer than 50 are actually used. This bloat causes:
- Slower page loads in HubSpot (especially record views)
- Confused users who don't know which fields to fill
- Reporting errors from duplicate or conflicting properties
- Integration issues when syncing with other tools
- Higher risk of bad data entering the system
In our audits, we typically find that 50-70% of custom properties can be archived without any impact on operations. The trick is identifying which ones.
The 5-Step Property Audit Process
Go to Settings → Properties and export all properties for each object (Contacts, Companies, Deals). Include: property name, internal name, type, created date, and group.
Create a list in HubSpot for contacts where each property "is known." Properties with <5% population rate across your database are candidates for removal.
Before archiving, check if the property is used in any integrations (Salesforce sync, Zapier, native integrations). Search the property internal name in your integration settings.
Search for the property in Workflows, Forms, Lists, and Reports. HubSpot's property detail page shows some of this, but manual verification is safer.
Archive properties in batches of 10-20, then wait a week. This gives your team time to flag if something breaks. Archived properties can be restored if needed.
Properties You Should Never Delete
Some properties look unused but are actually critical:
- Original Source properties — even if not displayed, these power attribution
- Lifecycle Stage — core to HubSpot's funnel logic
- Lead Status — required for sales handoff
- Associated Company/Deal IDs — powers object relationships
- Any property with "hs_" prefix — HubSpot system properties
Quick Wins: Common Bloat Sources
1. Old Integration Properties
Previous integrations (Drift, Intercom, old forms) often leave behind dozens of properties. If the integration is disconnected, these are safe to archive.
2. Duplicate "Same Meaning" Properties
We often find: "Job Title", "job_title", "Contact Job Title", "Title" — all meaning the same thing. Consolidate to one and map the others.
3. Campaign-Specific Properties
Properties created for one-off campaigns ("Webinar_2023_Attended") that are no longer needed. Archive these and use lists/campaigns for historical data.
4. Test Properties
Properties with names like "test", "temp", "delete_me", or developer names. These are always safe to remove.
The Audit Spreadsheet Format
When auditing, we track each property with these columns: