Merging two constituent records sounds like the simplest cleanup job in Altru. Pick the record you’re keeping, pick the duplicate, confirm. Then an error appears, or a pop-up asks about stored credit card information, and the merge stops. Nobody wants to guess on a step that can’t easily be undone.
Merge failures almost always come from something attached to one of the two records, not from the merge tool itself. The fix is to find that attachment, deal with it, and try again. Below are the usual causes, how to check for each one, and how to handle the stored card prompt without losing a donor’s recurring payment.
Before you retry: pick the right surviving record
A lot of merge trouble starts with merging in the wrong direction. Before you touch anything, open both records side by side and note:
- Which record has an active membership, and whether it’s set to renew automatically.
- Which record has recurring gifts, pledges, or open balances.
- Which record is part of a household, and whether it’s the head of household.
- Which record has the stored payment method on file.
- Which email and address are current. Ask the guest if you can.
As a rule, keep the record that carries the most active, ongoing activity: the live membership, the recurring gift, the stored card. The record that only holds a few old ticket orders is usually the one to merge away. Choosing that direction avoids many of the conflicts described below.
Common reasons a merge fails
Altru’s error wording varies by situation, and we won’t guess at exact message text. If you get a message, read it closely. It usually points at the kind of data that’s blocking the merge. These are the usual culprits.
Conflicting memberships
If both records hold memberships, especially two current ones in the same program, the merge may not be able to combine them cleanly. Decide which membership is the real one. Cancel or correct the extra one according to your membership policy, then retry. Write down the dates and benefits on the membership you’re removing so you don’t shortchange the member.
Household and relationship conflicts
Duplicates often sit in two different households, or one is head of a household and the other is a member of another one. Relationships can also collide. For example, both records might be linked to the same spouse. Clean up the household on the record you’re merging away first: remove it from the household or reassign the head. Then try the merge again.
Mismatched record types
An individual and an organization record generally shouldn’t be merged with each other. If someone created a business donor as an individual, or the other way around, you may need to correct the record type or move the activity by hand instead of merging.
Open transactions or records in use
Revenue that hasn’t been posted, a batch that hasn’t been committed, or a record another staff member has open can all get in the way. Commit or clear pending batches that touch either constituent, and try again later if the record is being edited.
Permissions
Merging is usually limited to certain security roles. If the option is grayed out or fails right away for one person but works for another, check that user’s role before you dig into the data.
The stored credit card pop-up
When one or both records have a saved card, you may see a prompt during the merge about what happens to that payment information. Don’t click through it. Stored cards are often what keeps an auto-renewing membership or a monthly gift running, and handling this step badly is how a donor’s recurring payment quietly stops.
- Find out what uses the card. Before merging, check whether a recurring gift, a pledge, or an automatic membership renewal is charging that stored payment method.
- Merge toward the card when you can. If the record with the card and the recurring activity is the one you keep, there’s usually much less to untangle.
- Read the prompt’s options carefully. We aren’t going to describe the exact choices, because they can depend on your setup and Altru version. Pick the one that keeps the card tied to the active recurring commitment.
- Check after the merge. Open the surviving record and confirm that the recurring gift or auto-renewal still points to a valid payment method and that its next charge date looks right.
- Never copy card numbers into notes or screenshots as a workaround. If the card can’t be kept, contact the donor and have them update their payment the normal way.
If you’re not sure how your Altru instance handles stored payments during a merge, test it first. Create two test constituents with a test card in a sandbox, or ask Blackbaud support how the prompt behaves for your configuration. Testing takes ten minutes. Rebuilding a lapsed recurring gift takes a lot longer.
When it still won’t merge
If you’ve cleared memberships, households, batches, and permissions and the merge still fails, save the exact error text and the two constituent lookup IDs, then open a case with Blackbaud support. Meanwhile, mark the duplicate clearly, for example with an attribute or a note saying “duplicate of [ID], do not use.” That way staff stop selling to it and email lists don’t pick it up twice.
Cutting down on merges in the first place
Every merge you avoid is one less chance for these errors. Most duplicates come from online orders where a returning guest types a slightly different name or email, and from walk-up sales where staff create a new record instead of searching. A short search-first habit at the desk and a regular duplicate review help more than any single fix.
For the review step, Social Good’s Deduper finds duplicate constituent and email records in Altru and helps you fix them. That way cleanup happens in planned batches, not one surprise at a time when a member calls about a missing renewal.
