Bulk property cleanup via scheduled recurring workflow

Outcome. A defined set of common formatting problems, stray whitespace, inconsistent casing, stale placeholder values, gets swept and corrected across the active contact database on a fixed schedule, instead of relying only on point-in-time fixes at creation that miss records edited outside HubSpot's own forms.

Workflow map Enrollment, branches and actions at a glance data-quality-048

flowchart TD
    A[Weekly scheduled sweep of active contacts] --> B[Custom code: trim, case-normalize, check placeholders]
    B --> C[Set Last cleanup pass date]
    C --> D{Changes made?}
    D -->|yes| E[Set cleaned field values]
    B --> F{Placeholder flagged?}
    F -->|yes| G[Add to placeholder review list + create task]

When to use it, when not to

• UseUse it as ongoing maintenance once you already have event-based normalization running on new and edited records, data-quality-003 through data-quality-005 for example, but still see drift creeping in from bulk imports, API writes, or edits that do not pass through the properties your event-based workflows watch.
• UseUse it as a complement to, not a replacement for, the one-time retroactive pass in data-quality-031. That fiche is for a single deliberate backfill when a rule changes; this fiche is a standing recurring job that keeps running indefinitely.
• SkipDo not use it if your only source of dirty data is form submissions already covered by event-based workflows. A recurring full-database sweep spends execution allowance checking records that are already clean on every single run.
• SkipDo not use it with a schedule tighter than your actual data-drift rate. If new dirty data only appears from a monthly batch import, a daily sweep wastes executions rechecking records that have not changed since the last pass.