Additional Custom Duplicate Detection Rules Guardrails

HubSpot's native duplicate management keeps getting better. Third-party tools like Koalify, Insycle and Dedupely still have more sophisticated rules and automation, but the default matching model has always been a black box, and custom rules let you say which properties actually define a duplicate in your portal. A word of caution from experience: the first time this page appeared it felt like the greatest thing that ever happened, and then a client found it and two weeks disappeared into merging. Nothing here merges automatically, and that is a feature. Automated merge rules have cost truly countless hours of undoing.

Chris's point is that rules are a layer of managing HubSpot that most teams have never run before, and they are harder than they look. The way most portals get built is in the moment: a problem comes up, someone adds a property or a calculation or a report, nobody documents it, and it works for the one user who asked. Build a duplicate rule the same way and every other team that follows a different flow inherits it. An ed tech client had a rule that an email domain containing college meant higher ed, and this week it surfaced a pile of preparatory schools, which are K through 12, tagged wrong. Good intentions, real data, and no way for one person to see every effect. So, as Chris put it, talk to Breeze first, solve from the process you expect to see rather than from the pile of purchased data that created the duplicates, and please do not build rules that let a domain name decide what a company is supposed to look like in your portal.