Your HubSpot account probably has properties your team barely thinks about anymore. Some came built into HubSpot. Others were added to track campaign activity, qualify leads, or support processes that have since changed.
But an outdated field isn’t necessarily an unused one.
A property that nobody updates might still determine which contacts enter a workflow, feed a report, or receive data from an external integration. It may have disappeared from your team’s daily routine without disappearing from the processes that depend on it.
So, how do you tell which properties are safe to retire and which still have a job to do?
The answer starts with knowing what you’re actually using before deciding what you no longer need.
1. Identify Properties That Are Genuinely Ready to Retire
Start by looking beyond properties with low activity or empty values. Neither automatically means a property is unnecessary.
Compare similar fields’ values and usage, verify workflows use any replacement, and ask process owners whether discontinued campaign data is still needed for reporting.
In the property editor, review usage, fill rate, and data sources under Monitor. Distinguish changes to a property’s settings from changes to its values on records; use property history exports for the latter. [1]
An older lead-source field, for example, may no longer receive new values but still contain attribution data needed for historical reporting. Confirm its purpose and ongoing value with the team using it.
2. Map Every Dependency Before Changing Anything
In Settings, open Properties, select the object, and find the property. From More, choose Export property definition. Its usage file identifies HubSpot tools using the property and links to those assets. [2]
Check these areas before proceeding:
- Workflows: Review enrollment and re-enrollment criteria, exclusions, branches, delays, and actions that read or update the property.
- Segments (lists) and forms: Check audience filters and fields collecting prospect information.
- Reports and dashboards: Identify filters, groupings, and historical reports that rely on its values.
- CRM views and record layouts: Check whether teams still use the property to qualify, prioritise, or manage records.
- Other properties: Check calculations that reference its values.
- Integrations and APIs: Identify external systems that read or write the property.
APIs and integration apps use properties’ internal names. Check integration settings, API mappings, custom code, and middleware separately. HubSpot’s usage information does not cover every external dependency. [3]
3. Plan the Replacement Before Retiring the Original
If a replacement is needed, first establish whether it serves exactly the same purpose. Compare its field type, available values, data format, and the rules used to populate it.
Before switching over:
- Export existing values and available history, retaining Record IDs.
- Map old values to their corresponding new values, including blanks and exceptions.
- Populate the replacement for relevant records and redirect incoming updates.
- Update affected workflows, forms, segments, reports, and connected systems. Creating a replacement does not redirect these references automatically.
- Test the replacement before archiving the original.
Check enrollment settings before populating the replacement: newly matching values can trigger automation. Review records already in affected workflows, including those waiting in delays, before changing their remaining steps. [4]
Property history exports include current and previous values, timestamps, and optional update sources.
For each record, property history is limited to 45 revisions for contact properties and 20 for company, deal, ticket, and custom object properties. Keep these exports separately; copying current values does not preserve the old field’s reporting history. [5]
4. Archive First. Delete Only When You’re Certain.
HubSpot distinguishes between archiving and permanently deleting properties. Archived properties can be restored before the 90-day deadline, after which HubSpot permanently deletes them. And permanent deletion cannot be undone.
Resolve the archive panel’s blocking dependencies first. Review its other listed usages too: archiving can remove a property from those assets, such as a column in a record view. [6]
Archive only after validating affected processes and preserving necessary data. Set a review date well before the restoration deadline. If historical reporting still needs the original field, keep it until that dependency is resolved.
5. Monitor Processes After Archiving
After archiving the property, check that the processes you updated continue to work as expected:
- Workflow activity: Review enrollment history and action logs for unexpected entries, skipped actions, or failures. [7]
- Property updates: Confirm forms and connected systems populate the replacement field correctly. Investigate missing values or sync errors.
- Reports and segments: Compare totals and membership against a baseline captured before the change.
Investigate unexpected differences before the original property’s restoration deadline. [8]
Keep Your HubSpot Data Changes from Disrupting Automation
The cleanup is complete when the processes that depended on the old property work correctly without it.
If you’re retiring outdated HubSpot properties but aren’t sure which workflows, reports, or integrations still depend on them, email us at info@growthnatives.com.
Through our HubSpot managed services, we can help you identify hidden property dependencies, update affected workflows and validate connected systems before retiring old fields.
Your CRM should evolve with your business. Your automations shouldn’t have to start from scratch every time it does.
Sources cited
[1] https://knowledge.hubspot.com/properties/understand-the-property-editor
[2] https://knowledge.hubspot.com/properties/organize-and-export-properties
[3] https://knowledge.hubspot.com/properties/understand-the-property-editor
[4] https://knowledge.hubspot.com/workflows/create-workflows
[5] https://knowledge.hubspot.com/properties/export-property-history
[6] https://knowledge.hubspot.com/properties/organize-and-export-properties
[7] https://knowledge.hubspot.com/workflows/create-workflows
[8] https://knowledge.hubspot.com/properties/organize-and-export-properties

