Loading
A duplicate does not just clutter a list. It splits a relationship in half: the renewal team sees one history, support sees the other, and neither knows the account is at risk.
And every report is wrong until they are merged, which is why cleanup should come before anything else in a data project.
Matching runs on entry, on import and on demand, with rules you can tune. A merge asks which value wins per conflicting field, then moves every deal, ticket, invoice and note onto the surviving record.
Nothing is discarded with the losing record — the history goes across, and the merge itself is one audit entry.
It will not merge on a partial match. Two similar companies at one address are sometimes one customer and sometimes two, and that judgement stays with a person.
And a merge is not designed to be reversed. It is recorded in full, but the safety mechanism is the review before it, not an undo after.
Reporting becomes trustworthy, because one customer is counted once. Support and finance see the same account as sales.
And because matching also runs at entry and on web forms, the population stops regrowing — a one-off cleanup on unchanged entry is a treadmill.
No. Deals, tickets, invoices and notes move to the surviving record.
It is recorded in full, but reversal is a support operation rather than a button. Review before merging.
Not if matching runs at entry and on forms. Cleanup alone is a treadmill.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.