A check arrives from “Riverbend Community Health Partners.” Nobody on staff recognizes the name, so whoever processes it creates a new organization record in Altru. Three months later someone notices that Riverbend is the same foundation that has given to you for a decade under its old name, and now its giving history is split across two records, its board contact is linked to the wrong one, and your annual report is about to list it twice.
Organizations rename themselves all the time: rebrands, mergers, a family foundation becoming a community foundation, a local bank absorbed by a regional one. The work in Altru isn’t hard, but it goes better if you decide up front what kind of change you’re dealing with.
First, decide: rename or new organization?
This question drives everything else, and it’s a judgment call your development team should make, not the person entering the gift.
- Same entity, new name. A rebrand or legal name change where the organization, its leadership, and usually its tax ID carry on. Treat this as an edit to the existing record. You want one record with one continuous giving history.
- Merger into an existing organization. Two organizations you may already have in Altru combine. Usually you keep the surviving organization’s record, update its name if needed, and decide whether to merge the other record into it or leave it as a historical record that’s marked inactive or deceased.
- Acquisition or genuinely new entity. If a corporate sponsor was bought and the new parent has its own giving program, its own decision-makers, and its own budget, it’s often cleaner to keep the old record as history and create (or use) a separate record for the new company, then connect the two with a relationship.
When in doubt, ask the organization directly. Their grants or community relations contact can tell you whether prior commitments, pledges, and matching programs carry over, which is the practical question underneath the legal one.
Handling a straight rename
1. Search before you touch anything
Look for records under both the old and new names, plus likely variations (abbreviations, “The,” “Inc.,” “Foundation” vs. “Fund”). Search by address, phone, website, and email domain as well. If someone already created a second record under the new name, you’ll need to merge it into the original rather than simply renaming.
2. Update the name on the original record
Edit the organization name on the constituent record that holds the long history. That record keeps its lookup ID, its revenue, and its relationships, so nothing downstream has to be re-pointed.
3. Preserve the old name somewhere searchable
This is the step most often skipped, and it’s the reason duplicates get created later. Staff, volunteers, and the organization’s own people will keep using the old name for a year or more. Depending on how your Altru database is set up, you might record the former name as an alias, a constituent attribute, or at minimum a dated note. If you’re not sure whether alternate names on organization records are included in your constituent search, test it: add the old name, then search for it from the screen your gift processors actually use. If it doesn’t come up, a note alone won’t stop the next duplicate, and you should ask Blackbaud support what your options are.
4. Update the details that usually change with the name
- Mailing address and phone, if they moved or consolidated offices
- Website and email addresses, especially if the email domain changed
- Contacts and relationships: confirm your main contact still works there and still has the same role
- Any recognition or acknowledgment name fields, so donor listings and thank-you letters use the new name going forward
5. Merge any duplicate
If a second record exists, merge it into the original so the new-name gifts join the existing history. Before merging, check which record has the more accurate address, contacts, and communication preferences, since you’ll want to keep the best data from each. If your organization restricts merges to certain users, route it to them rather than working around it.
Decisions that are easy to miss
How should the organization appear in past recognition? Your annual report for a prior year listed the old name, and that was correct at the time. For historical honor rolls and printed materials, most teams leave the old name alone. For anything going forward, including multi-year cumulative giving lists, use the new name, possibly with “formerly” in parentheses for the first year.
What about open pledges and recurring gifts? Confirm with the organization that open pledge balances or scheduled payments still stand under the new name. Since the revenue lives on the same constituent record after a rename, the commitment itself doesn’t move, but the person authorizing payments might have changed.
Are there corporate memberships or matching gift programs? If the organization holds a corporate membership or runs an employee matching program, check that the benefits, eligible employees, and matching rules still apply. Acquisitions in particular tend to change matching policies.
Do reports or queries filter by name? Any saved query, report, or smart field criteria that look for the organization by name text rather than by record will quietly stop catching it. Search your saved queries for the old name and update them to reference the record instead.
Make it easier for the next one
Write a short internal procedure covering who decides rename vs. new entity, where former names get recorded, and who handles merges. Then give gift processors one simple rule: if an organization name is unfamiliar but the address, contact person, or email domain looks familiar, flag it before creating a new record. That single habit prevents most split histories.
It also helps to run a periodic check for organization records created in the last few months that share an address or email domain with an older record. Rename-driven duplicates tend to show up there.
Quick answers
Will renaming the record change past gift receipts or acknowledgments?
Documents that were already generated and sent stay as they were. New letters and receipts will pull whatever name is on the record when they’re produced, so update the name before running your next acknowledgment batch.
Should I create a new record so the history “looks clean” under the new name?
Usually not. Splitting a continuing donor across two records undercounts lifetime giving and makes it harder for the next gift officer to see the relationship. Keep one record unless the organization truly became a different entity.
