Skip to content

Retroactive one-time normalization pass for existing records (batch enrollment)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Contact3 stepsUpdated for HubSpot seat pricing
OutcomeEvery existing contact gets a normalization rule applied once in a single controlled run, instead of only new records benefiting while the historical backlog stays inconsistent.
Workflow mapdata-quality-031
Manually enrolled from Legacy records list leads to Custom code: apply standing normalization rule. Custom code: apply standing normalization rule leads to Set normalized property value. Set normalized property value leads to Remove from Legacy records list. Manually enrolled from Legacy records list Custom code: apply standing normalization rule Set normalized property value Remove from Legacy records list
Manually enrolled from Legacy records list leads to Custom code: apply standing normalization rule. Custom code: apply standing normalization rule leads to Set normalized property value. Set normalized property value leads to Remove from Legacy records list. Manually enrolled from Legacy records list Custom code: apply standing normalization rule Set normalized property value Remove from Legacy records list

When to use it, when not to

Use it

  • Use it when you add or change a normalization rule (a country picklist, a phone format, name casing) after go-live and need it applied to records created before the rule existed.
  • Use it when you want a one-time correction, not a permanent recurring scan of the same records; see data-quality-048 for the recurring maintenance version.
Read more on when to use itShow less

Skip it

  • Do not use it as your only pass if new records keep arriving during the run. Pair it with the standing event-based workflow that already normalizes new and edited records, so the two do not fight over the same field.
  • Do not use it on a property whose normalization rule you have not already tested on new records. Confirm the standing rule works first, then reuse the exact same logic for the backlog.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 3 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 1 case, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Data quality spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library