Finding duplicates

The same person gets into a CRM more than once. They come in from a CSV, again from a Telegram chat, and once more when someone types them in by hand. Cavyro looks for those pairs and lets you merge them.

You’ll find it in Settings → Duplicates. It’s free on every plan.

What Cavyro looks at

Two records are paired when they share something that identifies them.

Signal	Applies to	What counts as a match
Same email	Contacts	The same address, whatever the capitalisation
Same phone	Contacts	The same number, however it’s punctuated
Same name	Companies	The name without its legal suffix, so Cherry IT and Cherry IT d.o.o. match
Same website	Companies	The same host, so cherry-it.rs and www.cherry-it.rs/contact match
Similar name	Both	Close spellings, like Aleksandar and Aleksandr

The first four are strong: an exact match on something that identifies the record. Similar name is a hunch, and the list says so with “Worth a look, not a certainty.”

Cavyro also knows when a signal means nothing. Twelve colleagues sharing one switchboard number aren’t duplicates, and neither are two companies whose only common ground is a Gmail address. Shared values like those get ignored rather than turned into dozens of false pairs.

When it checks

• Nightly, across the whole workspace.
• After every change to a record’s email, phone, name, or website.
• On demand, with Scan now at the top of the panel.

Reviewing a pair

1. Open Settings → Duplicates and pick the Contacts or Companies tab.
2. Each row names both records and shows why they were paired. Strongest evidence reads first.
3. Choose Review and merge to compare them, or Not duplicates to send the pair away for good.

Merging

The merge dialog asks one question: which record do you want to keep?

1. Pick the keeper. The comparison shows the email, phone, and website of both.
2. Read the After merging panel. It shows what the keeper ends up with, and marks anything it inherited from the other record.
3. Choose Merge.

What moves over

Everything attached to the archived record becomes the keeper’s:

• Comments and their reactions
• Files
• Tags, combined into one set rather than duplicated
• Deals and company links, with no duplicate link where both records were already on the same deal
• Custom field answers
• Activity history, so the two timelines become one
• Followers
• Mentions of it in comments and docs, which get repointed to the keeper

What happens to the fields

The keeper’s values win. Anything the keeper left blank is filled in from the other record. Nothing on the keeper is overwritten, so a merge can only add to it.

A merge can’t be undone

The archived record goes to the recycle bin marked “Merged into” the keeper, and it can’t be restored. Its comments and files moved rather than being copied, so restoring it would bring back an empty shell. Check the keeper before you confirm.

Warnings while you type

Creating a contact or a company checks as you go. Type a name or an email that matches something you already have, and a note appears under the form naming the existing record.

It never stops you. Open the existing record if it’s the same one, or carry on and create the new one if it isn’t. The API doesn’t block duplicates either, so imports and integrations keep working the way they always did.

Dismissing a pair

Not duplicates is permanent. Two people can share a surname and a phone number, and once you’ve said they’re different, Cavyro won’t ask again on the next nightly scan.

If you archive one record of a pending pair, the pair disappears on its own. There’s nothing left to merge.

Webhooks

A merge sends one contact.merged or company.merged event carrying the keeper and the record that was archived. Moving hundreds of comments and deals doesn’t fire an event each. See Webhooks for the full catalogue.

Good to know

• Phone numbers match on their international form. A number stored as 063/444-5566 with no country code won’t pair with +381 63 444 5566 yet.
• Merging needs permission to edit the keeper and to delete the other record.
• Deals aren’t checked for duplicates.
• Merging is one pair at a time, and you choose the keeper for the whole record rather than field by field.