Source Fields With Similar Names Appear to be Missing or Merged

Issue

When fields contain similar names, some appear to be missing or merged into a single column in the destination. For example, data from the fields tier_1_ and tier_1___ appear in the same column.

Environment

Connector: HubSpot

Resolution

To resolve this issue, create a new custom field in HubSpot with a distinct name that will remain unique after normalization. Avoid creating HubSpot fields that differ only by underscores or special characters.

Cause

For Fivetran SaaS connectors, our naming convention normalizes field names by removing or adjusting special characters and underscores, including converting multiple consecutive underscores to a single underscore.

When two source fields normalize to the same name, we treat them as duplicates and sync only one field to the destination. For the exampe above, we normalize both tier_1_ and tier_1___ to tier_1_.