A dropdown value can become obsolete while remaining important to historical reporting. Removing its meaning from the CRM can make old deals or tickets harder to explain. Keeping it selectable indefinitely can create new inconsistent records.
The June HubSpot roundup described archiving enumeration options while preserving existing record values. That creates a useful distinction between stopping future selection and rewriting history.
Identify why the option is being retired
Different reasons need different treatment. A typo may call for an agreed correction. An old product category may need to remain historically distinct. A changed sales process may require a new interpretation from a particular date.
Record the decision before editing the property. “Clean up the dropdown” is too vague to determine what should happen to existing records.
Review the dependencies
Inspect workflows, segments, forms, reports and integrations that refer to the option. Check whether an external system still sends its internal value. Hiding a choice in a user interface does not establish that every writer will stop using it.
- Which records currently use the value?
- Which processes select or evaluate it?
- What should happen to records already in those processes?
- Which report needs the historical distinction?
Assign an owner to unresolved dependencies. The property administrator should not have to infer the business meaning from a workflow name.
Choose preservation or migration explicitly
For an illustrative loss-reason change, an old “Other” category might remain on historical deals while new deals require a more useful reason. Reclassifying every old record would require reliable evidence, not a guessed mapping.
Where a migration is justified, define the source values, destination values, affected population and validation approach. Keep a recoverable record of the approved transformation appropriate to the project.
Test both old and new records
Check creation and editing paths, a workflow that evaluates the value, an integration update and a historical report. Validate whether the option is still displayed appropriately on existing records and whether users understand what to choose going forward.
Also check exports and downstream consumers. A report outside HubSpot may use an internal option value even when the visible label changes.
Document the cutover
Record the retirement date, reason, replacement guidance and the treatment of existing records. Include a short explanation in the property documentation where available. Review the affected workflows after the change to catch unexpected new use of the retired value.
See the data-quality foundation and migration validation guide for the wider process.
Keep the data model understandable.
I can help review property dependencies and implement a documented cleanup that respects reporting history.
Explore data & process design →