Skip to content

One donor. One record. Every time.

Ignite CRM catches duplicate donor records when they’re saved, when they’re imported and on a schedule, then merges them on one screen where nothing is lost by accident. Your team works a short queue instead of waiting for the next cleanup project.

  • Checked at entry, edit and import
  • Evidence on every match
  • An audit record for every merge

Your best donor might be two people.

Every event registration, online gift and list import is another chance to record someone you already know. Most teams know the duplicates are there. They put off merging because nobody can see what a merge will do.

Half her history on each record

Her gifts split across two records, so neither one looks like the major donor she is.

The double ask

Two records get two appeals and two receipts, and the donor wonders whether you know her at all.

Counts that drift

Every duplicate inflates your constituent and donor counts, all the way to the board report.

The button nobody presses

Which values survive? Where do the gifts go? What happens to her opt-out? Without answers, the cleanup waits for a project that never comes.

Try it here

Merge a duplicate record, start to finish.

These two records share an email and a phone, and Ignite recommends which one to keep. Both addresses stay unless you drop one. Ellen moved in May, so drop the old address, then merge and confirm.

  1. Drop the old address
  2. Merge, then confirm
Duplicate review · 2 recordsMatched on email and phone
Kept record
Address

Email and phone are the same on both records, and the middle initial M. is filled in from CON-000003907.

Keeps Ellen Park and merges 1 record into it.

3 related records move · $2,750 giving combined

Sample workspace. Every name and number is fictional.

In a working session, we run the workflows you care about live in an Ignite demo workspace.

One matching engine at every door.

Every door into your database uses the same engine, so a match scores the same way wherever it turns up.

At entry and edit

When someone saves a new record or changes a name or contact detail, Ignite checks for a match first and shows the evidence. They open the existing record, save it as not a duplicate with a reason, or save it and flag the pair for review. A profile waiting in the review queue carries a Possible duplicate banner, so staff see it before they work the record.

At import and online giving

By default, imports hold probable matches for review instead of creating new records, and online gifts go through the same matching check. If the check is down, both wait rather than create a record.

On a schedule

Detection runs sweep all constituents or one segment, on demand or after hours on a schedule you set. A scheduled run can notify your data managers in Ignite when it finishes, and a repeat run updates the groups it already found instead of adding them twice.

Merges you can check before they happen.

When every match shows its evidence and every merge shows its result first, merging stops being a once-a-year event and becomes part of the week.

Every match shows its evidence.

Ignite sorts likely duplicates into Ready to merge, Needs a look and Name only. Each group shows its score and the evidence behind it, such as Same EIN or Sounds alike. A different date of birth or suffix pulls the score down.

  • Ready to merge holds groups at 95% or more, and only those can merge in bulk.
  • Pairs that share an exact name and nothing else sit in their own bucket, so name-only imports still get checked without crowding the queue.
  • By default, members of the same household aren’t flagged against each other.
  • Work the queue from the keyboard: J and K move, M, N and D open the merge, not-a-duplicate and dismiss steps, and S skips.
See every signal Ignite matches on

See every difference before you merge.

The records sit side by side. Ignite recommends the record to keep and names the reason, such as most gifts and payments or most complete record. Every value where the records differ is marked Keep or Will be removed, and one click changes a choice.

  • Every distinct email, phone and address starts kept. Untick one to drop it.
  • Keep this one instead switches the kept record without undoing your field choices.
  • Suggest values fills in every choice at once from the kept record or the most complete one. You can change any pick before you merge.

Every gift moves. Every opt-out stays.

Gifts, payments, pledges, recurring plans, soft credits, opportunities, relationships and activities all move to the record you keep. So do tags, segment memberships and list subscriptions. Lifetime giving, donor tier and engagement are recalculated on the kept record, and duplicate soft credits are combined.

  • The strictest consent wins, and active suppressions stay in place.
  • If anything can’t move, the merge changes nothing. Both records stay as they were, and Ignite names the record types that blocked it.
  • Records with different primary fundraisers don’t merge until someone settles who owns the relationship.
How gifts, pledges and recurring plans work

Clear a backlog in one pass.

Merge every ready group in one step. A confirmation first shows how many records merge away and how many gifts and dollars move. Merge three or more records at once, and split off a record that belongs to a different person. You can also start from a constituent profile and merge it with another record.

  • Bulk merge takes only groups at 95% or more, and each group merges into its recommended record.
  • A split-off person is marked not a duplicate with a required reason, such as Spouse/partner, and the pair isn’t flagged again.
  • A dismissed group can come back on the next run, so a dismissal never hides a duplicate for good.

Every decision, on the record.

Merges, not-a-duplicate decisions and dismissals live in one History, and every merge has an audit record of what was kept and what moved. Months later, anyone with access can answer “what happened to this record?” from one place. The same safeguards are set out for IT reviewers on the Trust & Security page.

An audit record per merge

What was kept and what moved, counted by record type. The message after each merge links straight to it.

Merged-away records stay on file

Each one turns inactive, and old links to it open the kept record.

Decisions you can revisit

A not-a-duplicate decision keeps its reason, and Allow again returns the pair to matching.

Access by role

Merging and changing the rules are separate permissions. Administrators and the Data Manager role hold both by default.

What Ignite matches on.

Matching runs on deterministic rules. The strongest signal sets the score, and a match that rests on a single kind of evidence is marked down. Supporting evidence such as a postal code or website adds a little but never makes a match alone. People and organizations each have their own signals.

The signals Ignite duplicate detection matches on, what each catches, and how each counts toward a score
EmailThe same email on both records, even a secondary oneEvery email on the record is compared, primary or not
PhoneThe same person with a matching numberEvery number is compared. A near match on the last seven digits counts for less.
NameSound-alikes, typos and preferred namesAn exact name on its own lands in Name only. Sound-alikes and typos need other evidence.
Date of birthSame-name records that are one person, or twoA match adds weight. A different date of birth lowers the score or rules the pair out.
SuffixA senior and a junior with the same nameA different suffix lowers the score
Organization nameOne organization written two waysMatched by sound and by abbreviation
Tax ID (EIN)The same organizationStrong enough to match on its own
WebsiteThe same organizationSupporting evidence, compared by web or email domain
AddressRecords in the same areaSame postal code and country. It supports a match and never makes one alone.

Ignite CRM

Watch a duplicate backlog clear in a working session.

A 30-minute working session in the live platform, on real data.

A cleanup project, or a clean record every day.

An annual cleanup project is stale before it finishes. Ignite keeps the file clean as part of the daily work. For the habits that keep duplicates out in the first place, read how to fix common nonprofit data mistakes.

An annual cleanup project compared with duplicate detection in Ignite CRM, by dimension
An annual cleanup projectIgnite CRM
When duplicates are caughtOnce a year, after they pile upAt entry, edit and import, plus scheduled runs
How a match is explainedA spreadsheet of name pairsA score and the evidence that matched
What you see before a mergeUsually just the fields that surviveEvery value kept or removed, and everything that moves
Gifts and consentChecked by hand afterwardEvery gift and related record moves or none do, and the strictest consent wins
Working the backlogOne pair at a timeEvery group at 95% or more in one step, and groups of three or more
The audit trailWhatever the project team savedOne History and an audit record for every merge

Proven foundation

Built for nonprofit work.

Ignite is a new platform, built by the team nonprofits have trusted with their constituent and financial data for over 15 years.

G2 reviews

4.5/5

Average on G2.

20M+

Constituent profiles managed across the StratusLIVE platform family.

$1B+

In annual giving processed across the StratusLIVE platform family.

National FFA Foundation

33%

Increase in average gift amount

18%: increase in total fundraising contributions.

Read the National FFA Foundation storyOn the StratusLIVE platform family
"One source of the truth about our contacts, donors, and partners that is easily kept up to date."

Robert W.

Director of Fundraising Operations & Digital Solutions

Verified review · G2

What data managers ask first.

Straight answers about matching, merging and who can do what. For the rest of the constituent record, see the Ignite CRM page.

Book a working session
How does Ignite detect duplicate donor records?

Ignite checks for a match when someone saves a new record or changes a name or contact detail, when an import or online gift arrives, and in detection runs on demand or on a schedule. Deterministic rules score each likely pair from shared emails and phones, exact or sound-alike names, dates of birth and tax IDs, with postal codes and websites as supporting evidence. Groups land in Ready to merge, Needs a look or Name only for a person to review.

Does Ignite use AI to match duplicate records?

No. Ignite has AI teammates elsewhere, but duplicate matching and the recommended record run on deterministic rules, so every score shows the evidence behind it. No two records merge until a person confirms it.

Can a merge in Ignite be undone?

No. A merge is final, so Ignite shows everything first: the values that will be removed, the emails, phones and addresses you dropped, what moves and the combined giving. If any related record can’t move, nothing changes. The merged-away record is kept as an inactive record, and the audit record lists what moved.

What moves to the kept record when Ignite merges duplicates?

Gifts, payments, pledges, recurring plans, soft credits and opportunities, plus relationships, household membership, communication preferences, salutations, activities and form submissions, portfolio assignments, research, tags, segment memberships and list subscriptions. Lifetime giving, donor tier and engagement are recalculated on the kept record.

Will Ignite flag spouses or family members as duplicates?

Not when they share a household. By default, members of the same household aren’t flagged against each other. If a group still holds a different person, split them off as not a duplicate with a reason such as Spouse/partner. The pair isn’t flagged again.

Does Ignite catch duplicates in imports and online gifts?

Yes. By default, imports hold probable matches for review instead of creating new records, and online gifts go through the same matching check as records your staff save. If the check is down, imports and online gifts wait rather than create a record, so a busy day doesn’t leave a pile of copies to clean up later.

Can we change how strict duplicate matching is?

Yes. Start from Strict, Balanced or Relaxed, or set your own thresholds: one for the entry check when staff save records, and one for detection runs. By default, members of the same household aren’t flagged against each other, and you can also leave out coworkers at the same organization.

Who can merge duplicate records in Ignite CRM?

Your security roles decide. Merging and changing the rules are separate permissions, and Administrators and the Data Manager role hold both by default. Staff who enter records see the entry check, which never merges anything.

Keep one donor on one record.

See the entry check and a full merge in a 30-minute working session.