Salesforce for Nonprofits, the Salesforce.org Nonprofit Cloud, is a nonprofit constituent relationship management platform from Salesforce, which supports constituent engagement, fundraising, and grants. Nonprofit editions contain Salesforce Lightning Edition along with the former Nonprofit Success Pack (NPSP) combined.
For smaller organizations who don't have extensive data needs (i.e. not many audiences to segment) and who don't need robust reporting, this works great.
I’d say it’s very well suited for organizations looking to move toward AI integrations and make more data-driven decisions. As I mentioned, I’ve also used the competing product from Blackbaud, which is a very closed system — you can’t really pull out the data. Salesforce, on the other hand, has a big advantage with its APIs, allowing you to extract data, store it in Data Cloud, and do much more with it. However, if your requirements aren’t clearly defined or if there’s heavy customization involved, the implementation can get messy. So I wouldn’t recommend using Salesforce Nonprofit Cloud in cases where the requirements and structure aren’t clearly laid out.
More restrictions regarding image upload. Currently, you can upload any size and insert it. The email will not send correctly but you do not receive an error message.
Organizations that are new to Salesforce need to be prepared for report building and other configurations. Customization is a great feature, but it can be overwhelming if not impossible for a brand new user.
Salesforce Trailhead is robust but can be confusing and overwhelming.
I'm currently comfortable with only using Salesforce CMS or any iteration on a desktop.
Salesforce CMS is very intuitive and easy to use. I have not found where it glitches or crashes out. You can tell where data is "supposed to live" and it you aren't sure, there is an easy search function. Support is made readily available.
Support response has been swift and knowledgable, though not always the answer I've wanted. One huge design flaw is if I add a new Salesforce field to sync, Salsa Engage will not sync it unless it has changed since the last sync, requiring me to fake an update for an entire database or re-sync the whole enchilada. Better to recognize it's a new Salesforce field and perform the sync en masse.
I have never had bad conversations with any support people with Salesforce but we also have not used them very much. I put it a little less because we are struggling to switch to lightning (some of our custom features do not migrate well) and it feels like the help and support for a little organization is not incredibly helpful unless we want to spend a lot of money.
As a cloud native organization with no previous Microsoft infrastructure, Salesforce was a more logical and effective option for us. The suite of products was also far more comprehensive and required less customization. We were able to adopt a "configure not code" approach to our development of systems to support our mission that lowered the cost of upgrades.