Issue
When running a Segment ReverseETL sync to HubSpot, your sync fails to update existing fields and returns an error message similar to the following:
"A property named '<property_name>' already exists."
This error is accompanied by the category OBJECT_ALREADY_EXISTS and the subcategory Properties.PROPERTY_WITH_NAME_EXISTS.
Product
Segment Reverse ETL
Cause
This error originates from HubSpot's Properties API (OBJECT_ALREADY_EXISTS / Properties.PROPERTY_WITH_NAME_EXISTS). It occurs when an integration attempts to create or register a custom property schema definition whose internal API name already exists in your HubSpot portal (including properties currently in HubSpot's deleted/archived property bin)
Resolution
To resolve this issue, you must adjust the sync mode for your HubSpot destination to ensure it updates existing properties rather than attempting to create new ones.
Check the Internal Name in HubSpot:
In HubSpot, navigate to Settings (Gear Icon) > Data Management > Properties.
Locate the field mentioned in the error (
<property_name>).Open the property and click the
</>(Internal Name) icon to verify the exact system name versus the label.
Update the Segment Mapping:
In your Segment workspace, open the relevant Reverse ETL model mapping.
Ensure the destination field maps directly to HubSpot's internal API name, not the display label.
Check for Soft-Deleted Properties:
If the property was recently deleted in HubSpot, it may still exist in the Archived/Deleted Properties recycle bin with the same internal name. Permanently restore or purge the property from the trash bin before re-running the sync.
Test the Sync:
Run a manual test sync or preview to verify that data maps cleanly to the existing property without triggering schema creation errors.
If you need to isolate the issue during troubleshooting, you can temporarily remove the affected fields from your mapping, save, and then re-add them.