Ability to decide what the unique field should be at Company Level

HubSpot Ideas
1

It would be really, REALLY helpful to be able to decide what the over-riding Unique property should be at Company level
Domain is great until you get into the realms of any customer base that has a Trust or similar (also with Parent/Child Companies)
For those of us in the UK (and I would assume a similar issue occurs elsewhere) this is a massive stumbling block for anyone who has a Customer base in Education or Healthcare
Education has a URN which is unique to each school (at subdomain level) but data management is a minefield when you need to keep the data governance of Domain in place
Happy to be corrected on an easy work around but every suggestion so far just feels like sticking a plaster on it

2

Hi @MarzerSolutions ! Thanks for reaching out :slightly_smiling_face:

I’m curious if you’ve ever created properties in the CRM that require unique property validation? For example, you could create that “URN” property and set validation on the property that each record must have a unqiue value for this property. If done correctly, that property can be used within tools like import to update existing records instead of the company domain name property.

More info here!

3

Yes but this doesn’t help from HubSpot’s default deduplication/data import
issues perspective

4

Makes sense. Even if you’re able to import using a custom unique ID to deduplicate records upon ingestion, the duplicates tool is still flagging two records with the same domain as a duplicate, and you have to then go through and triage them still.

I wanted to flag two additional things for you…

  • We currently have a beta running for custom deduplication rules for all Data Hub Professional or Enterprise customers. This feature allows you to define up to 3 properties that you want to use to identify duplicates in your portal. We have plans to expand the number of properties you can reference in these custom rules soon.
  • We’re also working on building ‘merge rules’ that will help you create rules around how two records should be merged, and we also want to re-introduce automation. Creating an automated rule that rejects duplicate pairs if they only share the same domain is excellent feedback that we can account for as we build this out.