To Merge RE Databases or Not to Merge?
Options
Our agency will be merging with another in 2021. There is ongoing discussion as to how, when and if we should merge our two distinct RE databases into one. Please let me know your thoughts, experiences and Pros/Cons for doing so or not. Any and all comments / recommendations welcome and appreciated.
Tagged:
0
Comments
-
If you're truly going to be operating as one agency, my first thought would be to merge them.
- how will you determine which db to enter a record / gift into?
- if duplication of records between db, will you manually sit and dedup large lists for mailings/solicitations?
- are you going to keep duplicate records updated in both db?
- if you're using both, you'll need to duplicate every query, report, export to get accurate picture of activity/donations?
- would you be paying BB for each orgs db?
1 -
I would merge them. However BEFORE doing the merge, I would update your constituent ID's (if possible) to have them indicate the "source". Once you merge them, then all new constituent ID's would have just numbers. I like the constituent ID use because it's "front and center" and not "hidden" in attributes (we have a ton of attributes)
So for example
Database1 - constituent ID = DB01-1001, DB1-1002, etc
Database2 - constituent ID = DB02-1001, DB2-1002, etc.
After merge - constituent ID = 2020-1001, 2020-1002, etc.
You can set up all the new cons id's to be automatically generated with a year prefix in business rules.2 -
I would merge, it will be a lot of organizing in the beginning but will be very worth it in the long run. I agree with the others so clearly mark which database the donor came from and such.2
-
Our org merged with another one effective January 1, 2020. One of the first things that we did was merge the two donor databases (although one was not RE). While we are still cleaning up data (the two orgs tracked donors, gifts, etc very differently), it was the best thing we could have done. It has allowed us to communicate better with donors and understand which donors/corporations/funders supported both orgs. I highly recommend the idea of tracking which record came from which database on both constituents and gifts. For gift records, we added attributes that show which org received the gift. On constituent records, we added a constituent code to all of the records in the RE database identifying the original org and added a different one to all of the records that came into RE. This way, as we merged records, fundraisers are able to easily tell which donor/funder supported which org of if they supported both orgs without sifting through attributes. In addition, we added attributes that tied back to the original database including the ID# they had in the old database. We are hoping to run reports at 1 year, 3 years and 5 years post-merger on donor retention.
I highly suggest that you begin thinking of how the new org will operate post-merger and develop your database processes and reports to fit. In our case, it was not just a case of deciding whose processes to keep but how should it be done in the new org. We went from being two mid-size orgs to one very large organization. Things like changes in the GL coding (we link directly to FE) all played a part in how gifts and donors are tracked. It is a great time to start fresh with a new look at how the database is put together. Almost a year in, and we are still evolving our processes and data management.1 -
Elaine Tucker:
I would merge them. However BEFORE doing the merge, I would update your constituent ID's (if possible) to have them indicate the "source". Once you merge them, then all new constituent ID's would have just numbers. I like the constituent ID use because it's "front and center" and not "hidden" in attributes (we have a ton of attributes)
So for example
Database1 - constituent ID = DB01-1001, DB1-1002, etc
Database2 - constituent ID = DB02-1001, DB2-1002, etc.
After merge - constituent ID = 2020-1001, 2020-1002, etc.
You can set up all the new cons id's to be automatically generated with a year prefix in business rules.Along this same line of thought, I'd use constituent code markers instead of this, which are also viewable the instant a record is opened - a letter to indicate which database they came from, for example. "A - Individual" and "B - Individual" or something like that. I agree that attributes can hide to easily to be the only place you mark something like this, but I like that notes and dates can be entered with attributes.
I've had 2 merges into an existing RE database, and we used constituent codes to mark the different locations and then in the attributes, we entered what former database they came from, what the former record ID# was, and dates, and notes, etc. The Alias field also held the former record ID#.0
Categories
- All Categories
- Shannon parent
- shannon 2
- shannon 1
- 21 Advocacy DC Users Group
- 14 BBCRM PAG Discussions
- 89 High Education Program Advisory Group (HE PAG)
- 28 Luminate CRM DC Users Group
- 8 DC Luminate CRM Users Group
- Luminate PAG
- 5.9K Blackbaud Altru®
- 58 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 409 bbcon®
- 2.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- donorCentrics®
- 1.1K Blackbaud eTapestry®
- 2.8K Blackbaud Financial Edge NXT®
- 1.1K Blackbaud Grantmaking™
- 527 Education Management Solutions for Higher Education
- 1 JustGiving® from Blackbaud®
- 4.6K Education Management Solutions for K-12 Schools
- Blackbaud Luminate Online & Blackbaud TeamRaiser
- 16.4K Blackbaud Raiser's Edge NXT®
- 4.1K SKY Developer
- 547 ResearchPoint™
- 151 Blackbaud Tuition Management™
- 61 everydayhero
- 3 Campaign Ideas
- 58 General Discussion
- 115 Blackbaud ID
- 87 K-12 Blackbaud ID
- 6 Admin Console
- 949 Organizational Best Practices
- 353 The Tap (Just for Fun)
- 235 Blackbaud Community Feedback Forum
- 55 Admissions Event Management EAP
- 18 MobilePay Terminal + BBID Canada EAP
- 36 EAP for New Email Campaigns Experience in Blackbaud Luminate Online®
- 109 EAP for 360 Student Profile in Blackbaud Student Information System
- 41 EAP for Assessment Builder in Blackbaud Learning Management System™
- 9 Technical Preview for SKY API for Blackbaud CRM™ and Blackbaud Altru®
- 55 Community Advisory Group
- 46 Blackbaud Community Ideas
- 26 Blackbaud Community Challenges
- 7 Security Testing Forum
- 3 Blackbaud Staff Discussions
- 1 Blackbaud Partners Discussions
- 1 Blackbaud Giving Search™
- 35 EAP Student Assignment Details and Assignment Center
- 39 EAP Core - Roles and Tasks
- 59 Blackbaud Community All-Stars Discussions
- 20 Blackbaud Raiser's Edge NXT® Online Giving EAP
- Diocesan Blackbaud Raiser’s Edge NXT® User’s Group
- 2 Blackbaud Consultant’s Community
- 43 End of Term Grade Entry EAP
- 92 EAP for Query in Blackbaud Raiser's Edge NXT®
- 38 Standard Reports for Blackbaud Raiser's Edge NXT® EAP
- 12 Payments Assistant for Blackbaud Financial Edge NXT® EAP
- 6 Ask an All Star (Austen Brown)
- 8 Ask an All-Star Alex Wong (Blackbaud Raiser's Edge NXT®)
- 1 Ask an All-Star Alex Wong (Blackbaud Financial Edge NXT®)
- 6 Ask an All-Star (Christine Robertson)
- 21 Ask an Expert (Anthony Gallo)
- Blackbaud Francophone Group
- 22 Ask an Expert (David Springer)
- 4 Raiser's Edge NXT PowerUp Challenge #1 (Query)
- 6 Ask an All-Star Sunshine Reinken Watson and Carlene Johnson
- 4 Raiser's Edge NXT PowerUp Challenge: Events
- 14 Ask an All-Star (Elizabeth Johnson)
- 7 Ask an Expert (Stephen Churchill)
- 2025 ARCHIVED FORUM POSTS
- 322 ARCHIVED | Financial Edge® Tips and Tricks
- 164 ARCHIVED | Raiser's Edge® Blog
- 300 ARCHIVED | Raiser's Edge® Blog
- 441 ARCHIVED | Blackbaud Altru® Tips and Tricks
- 66 ARCHIVED | Blackbaud NetCommunity™ Blog
- 211 ARCHIVED | Blackbaud Target Analytics® Tips and Tricks
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- Luminate CRM DC Users Group
- 225 ARCHIVED | Blackbaud eTapestry® Tips and Tricks
- 1 Blackbaud eTapestry® Know How Blog
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)
- 1 Blackbaud K-12 Education Solutions™ Blog
- 280 ARCHIVED | Mixed Community Announcements
- 3 ARCHIVED | Blackbaud Corporations™ & Blackbaud Foundations™ Hosting Status
- 1 npEngage
- 24 ARCHIVED | K-12 Announcements
- 15 ARCHIVED | FIMS Host*Net Hosting Status
- 23 ARCHIVED | Blackbaud Outcomes & Online Applications (IGAM) Hosting Status
- 22 ARCHIVED | Blackbaud DonorCentral Hosting Status
- 14 ARCHIVED | Blackbaud Grantmaking™ UK Hosting Status
- 117 ARCHIVED | Blackbaud CRM™ and Blackbaud Internet Solutions™ Announcements
- 50 Blackbaud NetCommunity™ Blog
- 169 ARCHIVED | Blackbaud Grantmaking™ Tips and Tricks
- Advocacy DC Users Group
- 718 Community News
- Blackbaud Altru® Hosting Status
- 104 ARCHIVED | Member Spotlight
- 145 ARCHIVED | Hosting Blog
- 149 JustGiving® from Blackbaud® Blog
- 97 ARCHIVED | bbcon® Blogs
- 19 ARCHIVED | Blackbaud Luminate CRM™ Announcements
- 161 Luminate Advocacy News
- 187 Organizational Best Practices Blog
- 67 everydayhero Blog
- 52 Blackbaud SKY® Reporting Announcements
- 17 ARCHIVED | Blackbaud SKY® Reporting for K-12 Announcements
- 3 Luminate Online Product Advisory Group (LO PAG)
- 81 ARCHIVED | JustGiving® from Blackbaud® Tips and Tricks
- 1 ARCHIVED | K-12 Conference Blog
- Blackbaud Church Management™ Announcements
- ARCHIVED | Blackbaud Award Management™ and Blackbaud Stewardship Management™ Announcements
- 1 Blackbaud Peer-to-Peer Fundraising™, Powered by JustGiving® Blogs
- 39 Tips, Tricks, and Timesavers!
- 56 Blackbaud Church Management™ Resources
- 154 Blackbaud Church Management™ Announcements
- 1 ARCHIVED | Blackbaud Church Management™ Tips and Tricks
- 11 ARCHIVED | Blackbaud Higher Education Solutions™ Announcements
- 7 ARCHIVED | Blackbaud Guided Fundraising™ Blog
- 2 Blackbaud Fundraiser Performance Management™ Blog
- 9 Foundations Events and Content
- 14 ARCHIVED | Blog Posts
- 2 ARCHIVED | Blackbaud FIMS™ Announcement and Tips
- 59 Blackbaud Partner Announcements
- 10 ARCHIVED | Blackbaud Impact Edge™ EAP Blogs
- 1 Community Help Blogs
- Diocesan Blackbaud Raiser’s Edge NXT® Users' Group
- Blackbaud Consultant’s Community
- Blackbaud Francophone Group
- 1 BLOG ARCHIVE CATEGORY
- Blackbaud Community™ Discussions
- 8.3K Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions
- 5.7K Jobs Board