TeamRaiser Transition from Shere
Linda Allen
Comments
-
Linda Allen:
Can anyone share how they moved their data from Sphere to TeamRaiser? At the BBCon presentation I attended they discussed a migration tool which no one seems to know about or seems to have any advice on how you move records from Sphere to TR. I only want to take active names and emails no gift information although it would be good to know who was a team leader, participant and donor. I can't be the only one making this transition and am a little frustrated but the passing the buck message I am getting from all the transition folks. Any advice would be greatly appreciated.
Linda AllenHi Linda. I just wanted to chime in and apologize that you're having such a frustrating experience. I will leave this open for others to chime in, but I will also bring this post to my team and make sure we find a solution asap. Have you already opened any cases with support?
0 -
Amy,
I called support and they showed me how to run
reports and export the information. I have talked with my Luminate
person and my TeamRaiser consultant, plus when we started this
project my account rep told me it wouldn’t be a problem. There
isn’t anyone who understands all the pieces to tell me how it
should work as a whole and here are the steps.I have asked if I should take the emails from
Sphere and put them in RE but then how would they get into TR, so
that’s my frustration is understanding how they work together to
know what will work best. Also why would a presenter at BBCon say
there was a migration tool to make it easy and then no one seems to
know about this tool.To be clear I am not looking for any gift
information to be brought over just constituents and emails, my
understanding is for luminate to not create a duplicate it needs to
match RE which all would be duplicates of RE and the addresses are
not all up to date in Sphere.Linda
Allen
Data
Administrator
MaineGeneral Office of Philanthropy
PO Box 828, Waterville, ME 04903
linda.allen@mainegeneral.org
Phone:
207-626-7237 Fax: 207-626-19150 -
Hi Linda,
Which connector are you using between LO and RE? That will help everyone on the boards help you a little more. We will know how you are transferring data between the two systems.
Then we can go from there.
Thanks,
Phil
0 -
I don’t know the answer to that. We are
transitioning to NXT and being fully hosted, the connection to LO
will happen after that transition.Linda
Allen
Data
Administrator
MaineGeneral Office of Philanthropy
PO Box 828, Waterville, ME 04903
linda.allen@mainegeneral.org
Phone:
207-626-7237 Fax: 207-626-19150 -
Linda Allen:
I don’t know the answer to that. We are transitioning to NXT and being fully hosted, the connection to LO will happen after that transition.
Linda Allen
Data Administrator
MaineGeneral Office of PhilanthropyThe answer Phil's question can make a big difference. If you're using RELO, the built-in (Blackbaud) integration between RE and LO, or a third party integration tool like OMatic's LO - RE integration or JMG's Super Importer-Exporter the response is different.
0 -
We only use BB products no 3rd
party tools at all.Linda
Allen
Data
Administrator
MaineGeneral Office of Philanthropy
PO Box 828, Waterville, ME 04903
linda.allen@mainegeneral.org
Phone:
207-626-7237 Fax: 207-626-19150 -
Linda Allen:
We only use BB products no 3rd party tools at all.
Linda Allen
Data Administrator
MaineGeneral Office of Philanthropy
PO Box 828, Waterville, ME 04903
linda.allen@mainegeneral.org
Phone: 207-626-7237 Fax: 207-626-1915Hello Linda, I was the speaker at the Sphere to LO migration session at BBCON and I discussed the Sphere Upgrade Manager tool that we have used to move constituent data and donation records from Sphere to LO/TR. The tool is most effective when a customer does not also have RE. If you had your Sphere site linked to RE, then RE is your database of record and your Sphere constituents and donations are stored there. When you turn on integration between LO/TR and RE, the constituent data would typically populate in LO/TR so you don't need to use the SUM tool. I say "typically" because there could be configuration or other implementation choices you make that could alter it, but we have not usually recommended the SUM tool for use with RE customers. If you are not storing data like team captains or other FAF specific fields in RE, then you may need to manually bring that data over as part of your implementation. If you are stlil in the process of undergoing your LOTR implementation, your project manager should be able to validate if this is the case for you.
1 -
Betsy,
We have only brought gift information from
Sphere to RE, we were told early on we could not bring email over
and email to constituents unless they agree on its use for that
purpose. I did not have data flowing from RE into Sphere to keep
addresses up to date. There is no data on captains, participants vs
donors from thon events that came into RE that I am aware of. We
have the events module so if information came into there we might
have and I am not aware, it wasn’t a module we used but had to have
for Sphere to work.So it sounds like I should manually bring
emails into RE and put on the record then it will be pushed from RE
to LO when we integrate.Thanks for clarifying on the management tool,
that was not part of the one I heard (BBCon 2016). I know we have
to make the move from Sphere just disappointing there isn’t a way
to make the transition and not have to start from scratch.Linda
Allen
Data
Administrator
MaineGeneral Office of Philanthropy
PO Box 828, Waterville, ME 04903
linda.allen@mainegeneral.org
Phone:
207-626-7237 Fax: 207-626-19150 -
Hi Linda-
We're also brand new to Team Raiser. I have not tried to import constituents into LO/TR, but unless I'm missing something the task of getting constituents and email addresses into Team Raiser is pretty simple. I haven't heard you conclusively answer if you have RELO or not, so assuming you do not have RELO all you have to do is export your constituent data from Sphere (CONTROL -> REPORTS -> PAYMENT DETAIL REPORT is the one I use), log into Team Raiser, and use Data Management -> Import/Export to import your constituents and email addresses into Luminate Online. As far as I can tell it's as simple as that. Keep in mind the downside to doing this is if a Team Raiser participant tries to register with an email address you've imported, the participant will be told they cannot use that email address because it's already in use and they may not know what to do next (use the Forgot User Name or Password link). Again, I haven't tried this myself, but I discussed it with a Team Raiser Virtual Administrator from the Interactive Services group and he confirmed this is all there is to it.
Sphere/Kintera Export (Reports)
Luminate Online -> Data Management -> Import/Export -> Create Custom Constituent Import
0 -
Linda Allen:
Can anyone share how they moved their data from Sphere to TeamRaiser? At the BBCon presentation I attended they discussed a migration tool which no one seems to know about or seems to have any advice on how you move records from Sphere to TR. I only want to take active names and emails no gift information although it would be good to know who was a team leader, participant and donor. I can't be the only one making this transition and am a little frustrated but the passing the buck message I am getting from all the transition folks. Any advice would be greatly appreciated.
Linda AllenHi Linda:
When we moved from Sphere to TeamRaiser over four years ago we chose to take the data from RE instead of Sphere. I wanted to do the same thing, but the more I thought about it, I decided against it for many reasons. Since all of the data from Sphere went in to RE it was the better option for us. My reason for doing it this way was our Sphere data was not clean. People would create duplicate records, don't know how to spell their names, use their nicknames, etc. So when the data was coming down in the connector, I would clean it all up and link the records and merged duplicate records. Since RE is our primary database, I know the data was up-to-date, clean and free of dups. I also didn't want those Sphere records uploaded to Luminate because they would then sync down to RE which would have become a nightmare. We worked with Blackbaud on planning the data migration to Luminate. All of my records in RE are connected to Luminate and when we update RE, those changes are immediately updated to Luminate. So unless you don't have RE or never used the Sphere connector to bring in the data in to Re, I don't see why you wouldn't just migrate your RE data.
Patti Posey
Stamford Hospital Foundation
1 -
Patti,
The scenario you gave is exactly where we are and I follow your reasoning which were my concerns. We had been told we couldn't bring email into RE from Sphere without permission but now I will manually update those record. So did htye do a push from RE to create those luminate records. If I go this route trying to understand how the data gets into LO so we can email from there for our first TR event. As Aaron noted below does it recognize peoples emails and tell them they are already in the system? Part of me wants to send the initial emails for the event from Sphere and let me create new in TR. Still trying to wrap my head around TR/LO I thought it was like NetCommunity so am disappointed there will be 2 databases to maintain going forward. Like you I did not maintain Sphere in the past only RE. Appreciate your assistance. Hopefully my LO person can help me with the planning too but that wont come until TR has already been done and we transition to NXT so lots of moving parts.0 -
Aaron Rothberg:
Hi Linda-
We're also brand new to Team Raiser. I have not tried to import constituents into LO/TR, but unless I'm missing something the task of getting constituents and email addresses into Team Raiser is pretty simple. I haven't heard you conclusively answer if you have RELO or not, so assuming you do not have RELO all you have to do is export your constituent data from Sphere (CONTROL -> REPORTS -> PAYMENT DETAIL REPORT is the one I use), log into Team Raiser, and use Data Management -> Import/Export to import your constituents and email addresses into Luminate Online. As far as I can tell it's as simple as that. Keep in mind the downside to doing this is if a Team Raiser participant tries to register with an email address you've imported, the participant will be told they cannot use that email address because it's already in use and they may not know what to do next (use the Forgot User Name or Password link). Again, I haven't tried this myself, but I discussed it with a Team Raiser Virtual Administrator from the Interactive Services group and he confirmed this is all there is to it.
Sphere/Kintera Export (Reports)
Luminate Online -> Data Management -> Import/Export -> Create Custom Constituent Import
Thanks Aaron its the duplicate thing that I was trying to avoid folks already had trouble with Sphere after we provided their username and email reset. Support did give me the information on exporting that you show, I will use this to update RE and take it from there.
0 -
Linda Allen:
Patti,
The scenario you gave is exactly where we are and I follow your reasoning which were my concerns. We had been told we couldn't bring email into RE from Sphere without permission but now I will manually update those record. So did htye do a push from RE to create those luminate records. If I go this route trying to understand how the data gets into LO so we can email from there for our first TR event. As Aaron noted below does it recognize peoples emails and tell them they are already in the system? Part of me wants to send the initial emails for the event from Sphere and let me create new in TR. Still trying to wrap my head around TR/LO I thought it was like NetCommunity so am disappointed there will be 2 databases to maintain going forward. Like you I did not maintain Sphere in the past only RE. Appreciate your assistance. Hopefully my LO person can help me with the planning too but that wont come until TR has already been done and we transition to NXT so lots of moving parts.
I don't understand why you have to do this. When we purchased Luminate/TeamRaiser, Blackbaud had a whole team that I worked with and we planned this RE/Luminate integration. We had to do a RE/LO Pre-integration survey, RE/LO Field Mapping, RE/LO Phone Mapping.
I don't understand why your emails didn't come through the Sphere connector? Weren't they mapped in the connector? That's how we go all of our emails! If they opted out in Sphere, that was also in the connector and it would mark RE.
Once your records in RE are integrated in to Luminate, you will only have to maintain the RE database as that will sync up to Luminate in real time. We only sync RE to Luminate in real-time. All Luminate/TeamRaiser registrations, donations, changes,, updates come in to the RE/LO for processing.
Just so you understand, the database that is linked to RE is in Luminate - Constituent 360 not TeamRaiser. TeamRaiser is like a Raiser's Edge module. So when you create a TeamRaiser, there is no database in it. The database is created from people who register or donatate. I would highly recommend when you send out your first email that you include their username in Luminate (which is automatically created when the records are integrated) and a link to reset their password. By doing this, when they register for TeamRaiser, they will not be creating duplicate records. They will be using their record already in Luminate. This also helps in the RE/LO connector and cuts down on duplicates!
Hope some of this helps. I have had my share of issues over the past four years and if I can pass along any advice to make the transition easier for anyone starting out, I am happy to! Feel free to contact me if you have any questions.
Patti Posey
Stamford Hospital Foundation0 -
You have been a big help and I think I better understand the questions to ask. Much appreciated.0
-
Linda, I would add that given what I have learned so far about the RELO connector, I would strongly suggest you forego that software and create your own import process to get gifts and constituents into Raiser's Edge. I spent the past few days designing a solution in LO Report Writer and have a report that almost perfectly matches Raiser's Edge import requirements. As such there is minimal editing I need to do to prepare the LO report for import into RE. By following a similar process, you can save money/headaches and have better control over the data updates that happen in RE.
This is a partial screenshot of my LO report to export constituents and gifts in an importable format for Raiser's Edge.
0 -
Thanks Aaron as with all BB upgrades, there is a learning curve. Not having the right answers when we started with Sphere and how the connector "was just going to make it all work and I didn't have to worry" makes me cautious with a new connector. I have been since 09 still cleaning up bad and duplicate records that came through that first year. No matter how many times I think I must have them all still find another one here and there.0
-
Aaron Rothberg:
Linda, I would add that given what I have learned so far about the RELO connector, I would strongly suggest you forego that software and create your own import process to get gifts and constituents into Raiser's Edge. I spent the past few days designing a solution in LO Report Writer and have a report that almost perfectly matches Raiser's Edge import requirements. As such there is minimal editing I need to do to prepare the LO report for import into RE. By following a similar process, you can save money/headaches and have better control over the data updates that happen in RE.
This is a partial screenshot of my LO report to export constituents and gifts in an importable format for Raiser's Edge.
Hi Aaron,
Just curious, is this a one time import or do you plan on using this instead of the connector going forward?
Patti Posey
Stamford Hospital Foundation
0 -
Hi Patti-
I use that LO report every week to import gifts and constituents into the Raiser's Edge instead of using RELO. Each week I get a deposit slip from our business office with a deposit amount. I log into BBMS and find the disbursement report matching that deposit amount and note the gifts that make up that deposit. I then log into LO, run my custom report, delete any of the payments I'm not interested in and that report is the basis for my Raiser’s Edge import file.
A couple of things I'm doing to help manage the process: I'm using the Team Raiser Id as both the Import Id for my constituents and I'm adding a constituent attribute called Team Raiser Id so that I can quickly see which constituents are already in RE and which constituents need to be imported. I'm also importing the Transaction Id as a Gift Attribute so if the business office has any questions about a gift I can find the gift in RE and trace it back to a Team Raiser transaction. The only major manual step in the process is that I must separate registration fees from additional gift amounts so I can apply each portion to the correct appeal, but compared to other systems I import gifts from this process is pretty simple. I've got the LO to RE import down to about 20 minutes from start to finish. No need for RELO, no duplicate records, no bi-directional communication issues between the databases, no need to fuss with organization gifts that RELO can't handle. I would encourage others to give it a try. It’s really not that difficult to build.0 -
Aaron Rothberg:
Hi Patti-
I use that LO report every week to import gifts and constituents into the Raiser's Edge instead of using RELO. Each week I get a deposit slip from our business office with a deposit amount. I log into BBMS and find the disbursement report matching that deposit amount and note the gifts that make up that deposit. I then log into LO, run my custom report, delete any of the payments I'm not interested in and that report is the basis for my Raiser’s Edge import file.
A couple of things I'm doing to help manage the process: I'm using the Team Raiser Id as both the Import Id for my constituents and I'm adding a constituent attribute called Team Raiser Id so that I can quickly see which constituents are already in RE and which constituents need to be imported. I'm also importing the Transaction Id as a Gift Attribute so if the business office has any questions about a gift I can find the gift in RE and trace it back to a Team Raiser transaction. The only major manual step in the process is that I must separate registration fees from additional gift amounts so I can apply each portion to the correct appeal, but compared to other systems I import gifts from this process is pretty simple. I've got the LO to RE import down to about 20 minutes from start to finish. No need for RELO, no duplicate records, no bi-directional communication issues between the databases, no need to fuss with organization gifts that RELO can't handle. I would encourage others to give it a try. It’s really not that difficult to build.
Sounds great and glad to hear it's working for you. I know processing these registrations and donations can be a pain. But I look at it as an opportunity to update my data and clean up my records. I just have a few concerns :
1. I find that people spell their name wrong, use their nickname, give a business address, etc. So what happens when they register or donate and create a new record and because they used Liz instead of Elizabeth or a different address or email, how are you searching for them in your database. This happens to us daily. I take my Unmatched records and search each one to make sure they don't have a record already. Most of the time they do so I can link them and not create a duplicate record. I then get to reject their crappy information and keep my date in RE clean.
2. What are you doing when they update their records with a new address, email, etc? Do you get to compare the LO record with the RE record for new information and get to accept or reject the information coming in to RE. I check every record in my connector to make sure I am not bringing in garbage. And what I mean by that is, people typing in all lower case or all caps, fake email adresses, etc. I get to control what goes in my database. It may take me longer to process records but I know everything that goes in to my database.
3. For your new records, how do you know if they don't already have a spouse in your database? Are you checking for relationships and linking your records? What do you do when First Name -Bob and Jane Last Name -Smith make a donation? Do you leave it like that or are you able to see that in your import and have the opportunity to add Bob as the primary and Jane as the spouse?
These are just some of the things I come up with daily which is why I can't just import this data in my database without checking each record linked, matched or unmatched in the RE/LO. It is time consuming, but it allows me to look and records, fix and spelling issues, validate addresses, add any special coding or eliminate dup.
I'd be interested to hear how you adress these issues.
Patti Posey
Stamford Hospital Foundation
0 -
Hi Patti-
|> I find that people spell their name wrong, use their nickname, give a business address, etc.
I clean this up in Excel before I import the data.
|> What are you doing when they update their records with a new address, email, etc?
I export from RE addresses of existing constituents, compare those addresses to my import file and import new addresses on a second pass.
|> For your new records, how do you know if they don't already have a spouse in your database?
I don't, but I use RE's de-dup tool to merge registrants into records with matching non-constituent spouses. I also run monthly integrity checks to find (and merge where appropriate) constituents with similar addresses, either street or email.0 -
Aaron,
Thanks for your honesty abou the tools, doesn't sound like luminate is an improvement over the Sphere connector as this is the type of stuff I have been delaing with for years. Good to know how it works so I am ready for the cleanup. I don't start working iwth our implementation for LO for another week or so. I like the way NetCommunity works as your bring data in clean it up and it stays only in RE no second database to maintain.
Linda0 -
Linda Allen:
Aaron,
Thanks for your honesty abou the tools, doesn't sound like luminate is an improvement over the Sphere connector as this is the type of stuff I have been delaing with for years. Good to know how it works so I am ready for the cleanup. I don't start working iwth our implementation for LO for another week or so. I like the way NetCommunity works as your bring data in clean it up and it stays only in RE no second database to maintain.
LindaHi nLinda:
As long as your RE records are synced to Luminate, you DO NOT have to maintain two databases. When you update your RE records, Luminate is updated in real-time. You only have to update your RE records with the data from Luminate. And if you do update any records in Luminate, the updates will come down in the connector for RE.
Patti Posey
Stamford Hospital Foundation
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®
- 2K 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™
- 1 YourCause® from Blackbaud®
- 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
- 124 Ninja Secret Society
- 32 Blackbaud Raiser's Edge NXT® Receipting EAP
- 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
- 1.1K ARCHIVED FORUMS | Inactive and/or Completed EAPs
- 3 Blackbaud Staff Discussions
- 7.7K ARCHIVED FORUM CATEGORY [ID 304]
- 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