Help CenterLearn
Development / Fundraising track

Lesson 9 of 24

Reviewing and merging duplicate patrons

Venue AdminSuper Admin

Noctern proposes possible duplicate patrons for you to review — it never merges anything automatically. You decide which records, if any, are actually the same person.

Before you start

Venue Admin or Super Admin.

Reviewing candidates

Go to AdminVenuesPatronsDuplicates.

Possible duplicates page listing a candidate group flagged by a shared-email signal
1Possible duplicates
2Shared email signal
Possible duplicates page listing a candidate group flagged by a shared-email signal

Candidate groups are flagged by one of four signals, shown as a badge on each group:

  • Same name — an exact first + last name match.
  • Shared email — two patrons with the same email address.
  • Name + address — the same last name, the same street address, and the same first-name initial. (Couples living at the same address with different first initials are deliberately not flagged by this signal.)
  • Nickname match — a common nickname variant of the same name (Bob/Robert, and similar).
  1. Use the Open / Snoozed / Resolved tabs, the search box, or a signal chip to find a group.

  2. For each group, choose Merge…, Keep separate (dismisses the pairing for good), or Snooze 30d (revisit later).

  3. If you've just finished an import or a batch of manual entries, click Recompute candidates to refresh the list.

Merging

  1. Click Merge… on a group. Pick which patron is the survivor and which will be merged away.

  2. For each conflicting field (name, email, phone, address), choose which record's value wins. Tags are combined from both records, and every external system id is kept on the survivor — nothing is dropped.

  3. Review the dry-run plan — it lists exactly how many purchases, donations, pledges, recurring gifts, interactions, and other records will move to the survivor before anything happens.

  4. Click Confirm — merge into [survivor's name].

Once merged, the losing patron's page redirects visitors to the survivor automatically, and every purchase, gift, pledge, and interaction re-points to the survivor. Giving and ticket rollups recompute afterward.

If a merge fails partway through (a network blip, for example), reopening it shows a Resume merge button — it's safe to resume, since each step only runs once.

Watch out

A merge is not reversible by default. Undo-within-30-days exists as a feature, but it isn't a self-serve setting — Noctern support turns it on for your venue if you want it.

Try it yourself
  • Open the demo venue's duplicate review queue and find the "Shared email" group.
  • Open the merge dialog and check the dry-run counts before confirming anything.
  • Practice Keep separate on a group you don't intend to merge — confirm it drops out of the Open tab.

Open this topic in the help center

Try it

Open Admin → Venues → [venue] → Patrons → Possible duplicates, read the signal badge on one group, open its merge dialog and study the dry-run counts per collection — then choose Keep separate rather than merging a real pair.

Checkpoint

Answer all 3 questions correctly to mark this lesson complete.

  1. 1. Two people share a street address but have different first initials. Does the name+address signal flag them?

  2. 2. What happens to the losing record's external system IDs after a merge?

  3. 3. What does the merge dialog show before you commit?