Half her history on each record
Her gifts split across two records, so neither one looks like the major donor she is.
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.
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.
Her gifts split across two records, so neither one looks like the major donor she is.
Two records get two appeals and two receipts, and the donor wonders whether you know her at all.
Every duplicate inflates your constituent and donor counts, all the way to the board report.
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
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.
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
Merge 2 records?
Merge Ellen M. Park into Ellen Park. The merged-away record is kept as an inactive record. This can't be undone.
Contacts dropped
Moves to Ellen Park
Gifts: 3
Giving: $2,750 combined. Donor tier and engagement are recalculated.
Consent: Active suppressions are kept. Each email and phone keeps its most restrictive consent.
Kept record
Ellen M. Park ·
· merged away:
Listed in History
Merged 2 records.
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.
Every door into your database uses the same engine, so a match scores the same way wherever it turns up.
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.
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.
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.
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.
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.
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.
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.
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.
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.
What was kept and what moved, counted by record type. The message after each merge links straight to it.
Each one turns inactive, and old links to it open the kept record.
A not-a-duplicate decision keeps its reason, and Allow again returns the pair to matching.
Merging and changing the rules are separate permissions. Administrators and the Data Manager role hold both by default.
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.
| Signal | What it catches | How it counts |
|---|---|---|
| The same email on both records, even a secondary one | Every email on the record is compared, primary or not | |
| Phone | The same person with a matching number | Every number is compared. A near match on the last seven digits counts for less. |
| Name | Sound-alikes, typos and preferred names | An exact name on its own lands in Name only. Sound-alikes and typos need other evidence. |
| Date of birth | Same-name records that are one person, or two | A match adds weight. A different date of birth lowers the score or rules the pair out. |
| Suffix | A senior and a junior with the same name | A different suffix lowers the score |
| Organization name | One organization written two ways | Matched by sound and by abbreviation |
| Tax ID (EIN) | The same organization | Strong enough to match on its own |
| Website | The same organization | Supporting evidence, compared by web or email domain |
| Address | Records in the same area | Same 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.
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 | Ignite CRM | |
|---|---|---|
| When duplicates are caught | Once a year, after they pile up | At entry, edit and import, plus scheduled runs |
| How a match is explained | A spreadsheet of name pairs | A score and the evidence that matched |
| What you see before a merge | Usually just the fields that survive | Every value kept or removed, and everything that moves |
| Gifts and consent | Checked by hand afterward | Every gift and related record moves or none do, and the strictest consent wins |
| Working the backlog | One pair at a time | Every group at 95% or more in one step, and groups of three or more |
| The audit trail | Whatever the project team saved | One History and an audit record for every merge |
Proven foundation
Ignite is a new platform, built by the team nonprofits have trusted with their constituent and financial data for over 15 years.
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.

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
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 sessionIgnite 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.
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.
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.
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.
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.
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.
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.
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.
See the entry check and a full merge in a 30-minute working session.