❌

Normal view

Received — 14 October 2026 ⏭ CRM - Customer Relationship Managment

Before merging duplicate contacts, what do you preserve so a bad merge can be reversed?

Suppose a small B2B team finds two contact records that appear to be the same person. One has the meeting notes and an open task; the other is linked to an active opportunity. Someone merges them, then a rep discovers they were two different people with similar names.

Exporting the contact fields before the merge seems necessary, but not sufficient. Restoring two names and emails doesn't automatically put the notes, tasks and opportunity links back where they belonged.

I'd want a pre-merge record of both IDs, the conflicting fields, and which activities/relationships belonged to each. The merge review would also show those relationships, rather than just ask which phone number to keep. I wouldn't let the merge silently decide which active follow-up should continue.

For teams that have had to undo a mistaken merge, what information made recovery possible? Is a pre-merge export plus an activity/relationship map enough, or do you require a native unmerge option before allowing routine merges? I'm asking about the recovery process, not recommendations for a different CRM.

submitted by /u/Normal_Succotash_520
[link] [comments]
❌