Key takeaway
Deduplication looks like a data-cleanliness task. It's actually an associations task: every contact you merge carries deals, tickets, emails, and enrollment history, and the merge decides which of those survive. Pick the surviving record by a rule, automate only the conflict-free cases, and log every merge so you can trace it later.
Pick the surviving record on purpose
HubSpot keeps the primary record and folds the secondary into it. Most of the properties resolve predictably, but associations and enrollment state do not always behave the way you'd hope.
Watch out
A contact enrolled in an active workflow keeps its enrollment on merge — but the secondary contact's in-progress enrollments are dropped. If your nurture logic matters, check enrollment state before you merge, not after.
Decide your survivor by a rule, not by whichever row you clicked first. The record with the earliest createdate, the most complete lifecycle stage, or the active deal association is usually the one to keep.
Automate the safe cases, review the rest
Not every duplicate is equal. Two contacts with the same email and no deals? Merge them in bulk. Two contacts where both carry open deals with different owners? That's a human decision — merging silently reassigns pipeline.
Tip
Split your duplicates into two buckets: "no deal conflicts" (safe to automate) and "deal or ownership conflict" (route to a human). The second bucket is small and it's where the expensive mistakes hide.
Build the safe-case merge as an operations routine with a dedupe key you trust — usually email, normalized to lowercase and trimmed — and log every merge so you can answer "what happened to that contact?" six weeks later.
Governed, repeatable data operations like this are exactly what a HubSpot instance needs to stay trustworthy as it scales — not a one-time cleanup that decays the moment forms start creating records again.
Related tipReplace one manual handoff with a governed syncMore Bytes
PlatformsMarketo templates that survive a team handoff
The person who built your Marketo programs will eventually leave. Build templates and tokens so the instance doesn't leave with them.
PlatformsYour CRM isn't the problem — your lifecycle definitions are
Before you migrate platforms or blame the tool, get four teams to agree on what a lead, an MQL, and an opportunity actually mean.
PlatformsInspect a Salesforce Platform Event before you blame middleware
When a downstream integration goes quiet, verify Salesforce actually published what you think it did — before you spend a day debugging the wrong system.