Cross-object & reference matching

Duplicates rarely stay inside one object. If a company exists twice, the people attached to it are usually duplicated too — but they don't look like duplicates, because they sit under two different company records with two different domains. Two features handle that.

Use company matches as evidence for people

A checkbox in the Automation card on the Scan page. When it is on, companies you have already flagged as duplicates are treated as one company while people are being matched, so someone at acme.com and someone at acme.co become comparable and a near-identical name across the two is caught.

• It uses duplicate company groups that are still pending — the evidence comes from the review queue, so you don't have to merge the companies first.
• Freemail domains (gmail.com, yahoo.com, outlook.com and the like) are excluded. Two people on Gmail share a domain and nothing else.
• Groups found this way carry a Cross-object badge on the Duplicates page, with a tooltip explaining the evidence, so you always know why the group exists.
• It is a Pro feature, and it takes effect on the next scan — turning it on does not re-group existing results.

The badge is worth attention when you review. Cross-object matching deliberately loosens the bar for people at companies you have said are the same, so it finds duplicates a same-domain rule cannot — and it depends on your company groups being right.

Reference keys resolve through duplicates

When a match key is a record reference — the Company attribute on a deal, say — Deduptio does not compare the raw linked record IDs. It resolves each reference through your pending duplicate groups first, so two deals pointing at two copies of the same duplicated company count as pointing at the same company.

This has no toggle. It applies whenever a reference attribute is one of your keys, and it is what makes deduplicating deals, opportunities and other linked objects work while their parent records are still duplicated. Clean up companies first if you can — but you do not have to.

A sensible order

1. Scan and merge companies first: they are the evidence everything else leans on.
2. Turn on cross-object matching, then scan people.
3. Scan objects with reference keys (deals and custom objects) last, when their parents are clean.

You can run it in any order — pending groups are used as evidence either way — but this order produces the fewest surprises.