cleanup-properties

This Skill inventories all HubSpot properties across contacts, companies, and deals, classifies them by usage and dependencies, and applies a safe archival-first workflow to remove obsolete custom fields and reduce property sprawl.

The safest approach uses an archival-first deletion workflow with dependency validation, fallback archiving, and rollback logging to ensure an auditable and reversible cleanup process for obsolete contact fields.

Yes, a HubSpot API token is required to inventory properties, validate workflow dependencies, classify Salesforce sync fields, and execute the archival or deletion workflow across your portal.

Yes, the cleanup process specifically identifies Salesforce sync properties, test/temp properties, and obsolete form fields to determine whether they are safe candidates for archival or deletion.

If active workflow dependencies are detected, the process applies safeguards and dependency validation to prevent breaking automations, defaulting to fallback archiving rather than permanent deletion.

Property sprawl degrades data quality by cluttering forms and automations with obsolete fields; you fix it by inventorying all object properties and archiving unused ones to simplify portal governance.