External ID properties

To connect your source-app data with HubSpot objects, create a custom property in HubSpot that stores the primary ID from the source system.

For example, when syncing customer data to HubSpot contacts, define a property (e.g., external_customer_id) to hold the customer ID from the source app. This enables workflows to look up and match HubSpot records using that unique identifier.

Unique properties

HubSpot also allows you to enforce uniqueness on custom properties across a given object type. By setting your customer ID property to be unique, HubSpot will prevent duplicate contacts from being created with the same ID—ensuring data integrity and supporting reliable record lookups in workflows.

When setting up a new property you can select "Require uinque values for this property" on the Rules page

Once a property is created in HubSpot, you cannot retroactively set it as unique. To enforce uniqueness, you’ll need to create a new property with the unique setting enabled, then use a workflow to copy values from the original property to the new one.

As an integrator, using unique properties in HubSpot offers several advantages:

• Secondary Identifier: Unique properties can serve as secondary IDs when importing data manually or through the API

• Streamlined API Updates: Certain HubSpot APIs—such as the Deals API—allow you to update records directly using a unique property, eliminating the need for additional lookup steps