Standardize date property format across import sources

Outcome. A date property fed by multiple import sources in inconsistent formats reads and sorts correctly everywhere in HubSpot, instead of storing some records as text-parsed garbage or the wrong day from a day and month swap.

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

flowchart TD
    A[Contract start date raw known] --> B[Format Data: parse into date]
    B --> C{Parse succeeded and unambiguous?}
    C -->|yes| D[Set Contract start date, status Converted]
    C -->|no| E[Status: Ambiguous, create review task]

When to use it, when not to

• UseUse it when a date property, a contract start date, a renewal date, is fed by more than one source, an import, a form, a native integration, each of which may format the raw date differently, DD/MM/YYYY versus MM/DD/YYYY versus a plain text string.
• UseUse it right after import, before the date property is relied on by a report or another workflow's delay or branch logic that assumes a correct date.
• SkipDo not use it on a property that is already a native HubSpot date field populated only through the UI's own date picker. The picker already prevents ambiguous entry; this fiche targets fields that started life as text or arrive through an unmanaged import path.
• SkipDo not use it to guess a date format silently when the source format is genuinely ambiguous, a two-digit day and month both under 12. Flag those for manual confirmation instead of assuming one convention.