Approve and merge a pair

Merging combines a duplicate pair into a single record in Attio while preserving notes, tasks, files, list memberships, and relationships.

The two-step flow

Merging a pair takes two actions:

1. Approve the pair (keyboard a) — this marks it Confirmed and saves your merge choices as a draft.
2. Execute merge (keyboard m) — this runs the merge. Only confirmed pairs can be merged.

Splitting approval from execution means you can review a batch first, then merge them all when you're ready.

Which record survives

In the side-by-side comparison, the first record (record 1) is the primary — the one that survives the merge. The second record is retired, and any of its data that fills a gap on the primary is carried over.

For any field where the two records disagree, you pick which value wins in the Merge result column. See Resolve field conflicts for the details.

Simulate first

Before a merge commits, DeDupe shows a simulation — a preview of the resulting record and any warnings. This "simulate-first" step lets you catch problems before anything changes in Attio.

After the merge

Merges are queued and processed in the background; you'll see the status update when each completes. Every merge is recorded in merge history and can be undone within 30 days.

To merge many pairs at once, see Merge in bulk. To let high-confidence pairs merge automatically, see Automate merges.