You finally agree on how mail should be addressed. Maybe it’s “Ms. Jane Smith” instead of “Jane Smith,” or “The Smith Family” for household members, or first-name salutations for your friendly member letters. You update the default name formats in Altru, run a test letter, and nothing changes for the thousands of people already in the database. Only new constituents pick up the new format.
As far as we’ve seen, that’s how Altru behaves by design, not a glitch. Below is why it happens and the realistic options for getting existing records in line.
Defaults apply going forward, not backward
In Altru, a name format (an addressee or salutation line) lives on each constituent record. The defaults you configure determine which formats a record gets when it is created. In our experience, changing the default later doesn’t reach back and rewrite records that already exist, because each of those records already carries its own format. If you want to see it for yourself, change a default and then open an older record and a brand-new one side by side.
There’s a reasonable logic to it. Some of your existing formats were set by hand on purpose: a board member who wants “Dr. and Mr.,” a donor who asked to be listed anonymously, a widow who still wants her late husband’s name on the envelope. A blanket overwrite would wipe out those choices. The cost is that a policy change leaves you with two populations: new records on the new format, and everyone else on the old one.
Your options for existing records
1. Check whether a bulk tool covers name formats in your environment
Altru includes some bulk-update and import capabilities for constituent data, but we’re not going to tell you with certainty that any of them will add or replace name formats across existing records, because that depends on what’s available in your version and permissions. Before you plan around a bulk option, confirm it: try it on a handful of test records (or in a sandbox if you have one), or ask Blackbaud support directly whether name formats can be updated in bulk for existing constituents. Ask specifically whether the update adds a new format or replaces the primary one, since those produce very different results.
2. Fix the records that actually get mail
You probably don’t need every record fixed. A one-time visitor from 2019 who bought a single ticket isn’t getting your annual appeal letter. Build a query for the people who do receive printed mail or formal correspondence: current and recently lapsed members, donors in the last few years, board and volunteers, major prospects. That list is often a small fraction of the database, and it may be small enough to update by hand in shifts, especially with a volunteer or intern and a clear written rule for each case.
3. Build the greeting at export time instead
For mailings, you can sidestep stored formats entirely. Export first name, last name, title, and household or spouse fields from a query, then construct the addressee and salutation in your spreadsheet or mail-merge tool with a formula. This gives you full control over the result for that mailing, which makes it a practical stopgap for a big appeal while the underlying records are still mixed.
The drawbacks: it only fixes that one export, anyone who pulls a list later has to know to use the same formula, and receipts or acknowledgments generated from inside Altru will still use the stored formats.
4. Clean up as records are touched
Add “check the name format” to the routine steps for processing a renewal, gift, or address change. It’s slow, but over a membership cycle it covers most of your active people without a project. If your query fields expose the addressee or salutation, pair it with an audit query of active members whose format doesn’t match the new pattern, so you can watch the count shrink.
Before you change anything
- Write the rules down first. Cover individuals, couples with the same and different last names, households, organizations, and people with professional titles. Most inconsistency comes from staff guessing at the edge cases.
- Protect intentional exceptions. If records were customized at a constituent’s request, find a way to flag them (a constituent attribute or a note works) so no one “corrects” them later.
- Snapshot the current state. Export the existing formats for the records you plan to change, with constituent IDs, so you can see what was there before.
- Test where the formats show up. Check letters, receipts, email greetings, and any exports to outside tools after the change, not just the constituent record.
- Look at duplicates and households too. A tidy name format on one of two duplicate records still produces two envelopes. If household membership is inconsistent, household-level addressees will be wrong no matter what format you choose.
A realistic plan
For most organizations the practical sequence is: set the new defaults so the problem stops growing, confirm with Blackbaud whether a bulk update is possible for you, and if it isn’t, fix the mailing population first and let routine processing catch the rest. In the meantime, build greetings at export time for any mailing that can’t wait.
Quick answers
Why do new constituents look right but old ones don’t?
Defaults are applied when a record is created. Existing records keep the formats they already have until someone changes them.
Will editing a constituent’s name update their addressee?
It depends on how that format was set up on the record. Check a test record after a name change rather than assuming, especially for formats that were typed in by hand.
Is there one setting that resets everyone?
We’re not aware of a single switch that rewrites all existing name formats. Confirm with Blackbaud support for your environment before planning a large mailing around it.
