Change primary key


Its been over a year since i was on this forum. Im praying there has been some development since then.

We really need to be able to create multiple contacts with the same email address - this is specific for brokers who work on behalf our other clients.

Please let me know what is happening with this - ive searched around and there have been alot of queries around this,

It would be great if we could turn on/off the duplicate check?
or assign the duplicate check to another contact field (Whether default or custom)

Any feedback on if this has been done? will it ever be done? will be great


Hi @carolynebrownlee,

I sympathize with your frustration; that use case is legitimate.

That said, this is unlikely to ever change. Email addresses are not just the identifying property of contacts, but the foundation upon which most of the CRM is built. Removing the deduplicating power of email would affect every other tool and necessitate restructuring all HubSpot products.

If you do need "duplicate" contact records to work off as brokers, however, you could create a new contact with the original contact's email as long as you append +something before the domain.

For example, if the original contact is, HubSpot would allow you to create a contact with the email, as well as, etc. Gmail (and I believe other mail servers) will still deliver these emails to


thanks for feedback. ok then i could store anything in that field but i want to store the registration number then in that field and then the duplication check can still occur - anyway i can take off the validation on that field so it doesnt check for domain?


Hi, @carolynebrownlee.

Apologies for the delayed response; I have been out of the office since January 9.

I've tried creating contacts without an email domain a few different ways, but I unfortunately can't find a way to bypass the formatting check.

If you were to append a dummy domain like to the value, you should be able to store whatever values you wish in the property, but the domain would have to be manually or programmatically removed before you can use the true registration number preceding the @ symbol.