Contact Data
Part of CRM maintenance and replacement
Reviewing unused fields and customisations
Check a CRM field's purpose, values and dependencies before hiding, changing or deleting it, including product recovery limits.
Before changing a CRM field that appears unused, check its purpose, values and dependencies. Low use is a reason to investigate, not proof it can be deleted. Apply the same test to layouts, validation rules and workflows that add work without helping a current decision.
Inventory the item and its uses
Start with configuration that users find confusing or that appears rarely used. For each item, record its object, purpose, owner, current values and known entry and reading routes. Ask which decision or handover it supports. A field used once a year may still matter; a highly populated field may hold obsolete imported values.
| Question | Evidence to inspect | Possible decision |
|---|---|---|
| Is its meaning clear? | Label, help text and real entries | Clarify or rename it. |
| Is the value still needed? | User task, report or handover | Keep it or remove it from an active screen. |
| What writes to it? | Forms, imports, workflows and integrations | Change the source before retirement. |
| What reads it? | Reports, filters, rules and connected systems | Change dependencies before retirement. |
| Is its history needed? | Prior values and the organisation's records rule | Retain the field or preserve an approved extract. |
Reviewing unused CRM fields and customisations safely
- Is its meaning clear?
- Is the value still needed?
- What writes to it?
- What reads it?
- Is its history needed?
Use product signals within their limits
HubSpot lets users export property definitions to review usage and identify outdated or redundant properties. Its Data Quality area offers property insights to help understand where and how properties are used, subject to the documented subscription and access conditions. HubSpot says a property can be archived if it is not being used in records or assets, such as segments, index pages or report filters.
For any CRM, treat available reference searches as a starting point. Check integrations and user practice separately before approving deletion.
Choose a proportionate change
If the value is needed but hard to enter, correct its definition, placement or timing. If old values remain useful but new entry is unnecessary, consider removing the field from active forms or making it read-only where the product supports that. If there is no approved continuing purpose, plan retirement after dependencies and retention have been reviewed.
HubSpot permanently deletes archived properties after 90 days. Before a destructive change, preserve any approved data and restoration information. For Salesforce, confirm the current deletion and recovery behaviour in product documentation before proceeding.
CRM field retirement considerations
- HubSpot archive retention
- Salesforce deletion recovery
- Recommended action
Check the affected work
Write expected results for a new record, an old value, a report and any import or integration that uses the item. Make one controlled change and inspect what an ordinary user can enter and retrieve. Resolve a failed dependency before extending the change. Finish with the decision, owner and remaining exception.
Safe change process for unused CRM fields
- Define expected outcomes
- Make one controlled change
- Resolve failed dependencies
- Finalise decision and ownership
