HubSpot CRM Data Hygiene
Identify cleanup needs across contacts, companies, deals, and tickets. Follow ../hubspot/SKILL.md for access, URLs, pagination, and write approvals.
Workflow
- Call
get_user_details and confirm read access to the requested object types.
- Clarify issue classes: missing fields, stale records, duplicate-like records, owner gaps, associations, lifecycle/stage issues, or imports.
- Discover properties with
search_properties: contact email/phone/company/owner/lifecycle; company name/domain/website/owner; deal stage/pipeline/amount/close date; ticket subject/stage/priority/category/owner.
- Use
get_properties for enums, then search_crm_objects count queries with NOT_HAS_PROPERTY, HAS_PROPERTY, filters, and associatedWith.
- For duplicate-like checks, prefer strong keys: contact email, company domain/website, phone, or deal name plus associated company. If aggregation is unavailable, sample and say so.
- Fetch examples with
get_crm_objects only when current values affect cleanup.
Issue Classes
- Missing routing or identity fields.
- Stale activity, old modified dates, past close dates, or unresolved ticket age.
- Broken associations, inconsistent lifecycle/stage values, or duplicate-like records sharing strong identifiers.
Output
Return coverage, top issues with counts, example URLs, why each issue matters, recommended fix, cleanup backlog, human-review items, and caveats. Do not auto-merge duplicates or overwrite fields. For writes, use the core confirmation table.
1---2name: hubspot-crm-data-hygiene3description: Use when auditing HubSpot data quality for missing fields, stale records, duplicates, associations, owners, or cleanup tasks.4---56# HubSpot CRM Data Hygiene78Identify cleanup needs across contacts, companies, deals, and tickets. Follow [../hubspot/SKILL.md](../hubspot/SKILL.md) for access, URLs, pagination, and write approvals.910## Workflow11121. Call `get_user_details` and confirm read access to the requested object types.132. Clarify issue classes: missing fields, stale records, duplicate-like records, owner gaps, associations, lifecycle/stage issues, or imports.143. Discover properties with `search_properties`: contact email/phone/company/owner/lifecycle; company name/domain/website/owner; deal stage/pipeline/amount/close date; ticket subject/stage/priority/category/owner.154. Use `get_properties` for enums, then `search_crm_objects` count queries with `NOT_HAS_PROPERTY`, `HAS_PROPERTY`, filters, and `associatedWith`.165. For duplicate-like checks, prefer strong keys: contact email, company domain/website, phone, or deal name plus associated company. If aggregation is unavailable, sample and say so.176. Fetch examples with `get_crm_objects` only when current values affect cleanup.1819## Issue Classes2021- Missing routing or identity fields.22- Stale activity, old modified dates, past close dates, or unresolved ticket age.23- Broken associations, inconsistent lifecycle/stage values, or duplicate-like records sharing strong identifiers.2425## Output2627Return coverage, top issues with counts, example URLs, why each issue matters, recommended fix, cleanup backlog, human-review items, and caveats. Do not auto-merge duplicates or overwrite fields. For writes, use the core confirmation table.
ConcertoNotes