Can HubSpot please revert back to the original import logic for Contact Imports? The recent changes have made the process far more restrictive, reducing flexibility and customization—which feels like a step backward. Background: Previously, HubSpot’s contact import logic allowed users to match and update records using unique custom properties (skys the limit!) without requiring additional fields. This was highly customizable and efficient. Since then, HubSpot’s contact import validation logic has changed, and the documentation was updated afterward to reflect this. This happened January 2026. Current Behavior: For Contact imports, HubSpot now requires that at least one of the following fields be included before allowing any custom property to be used as the matching identifier: Email First Name Last Name Even if you prior had used a field as a unique property, it cannot be used on its own to match existing Contact records during an import after the change in import logic. Impact: At this time, there is no supported way to update Contacts via import using a unique property without also including Email, First Name, or Last Name. This behavior is enforced by the import system and cannot be overridden. Request: Please revert the import logic to allow the use of unique identifiers (as chosen by clients) as the sole matching property again. This sudden change has made imports far more constrained and inconvenient compared to the flexibility HubSpot users have come to expect. This change impacts workflows for teams that rely on custom identifiers—restoring the previous logic would greatly improve efficiency and user experience.
...その他を表示