If you’ve noticed I’ve been MIA the past 2 weeks…here’s the scoop.
I am neck-deep in a system migration right now, thanks to the shutdown of our online ticketing system. (If the phrase “Desk to Service Cloud” means anything to you, reach out. You’re likely a Salesforce admin doing the same thing, so we can commiserate together! 😅)
Any database manager will tell you that when it comes to implementing a new system, seamless-ness is next to godliness . If no one complains on launch day, then youknocked it out of the park. That’s my goal.
Okay, nonprofits. It’s time to move to Salesforce Lightning.
I know you love (or at least tolerate your disdain) for Salesforce Classic. I get that the idea of switching sounds like a nightmare! But we all knew this was coming.
In case you’re an admin who somehow hasn’t heard, Lightning is the latest Salesforce user interface. Without sounding like a gimmicky salesperson, Lightning is the way of the future for Salesforce customers.
Salesforce is a powerful tool. And if you’re tasked with implementing a new data system for your org, there are very good reasons why this might be the way to go.
But there are valid reasons to stay away, too.
My staff knows how much I love Salesforce. And as much as I wish every org could implement it without issue, that’s just not how it works! Your org needs to be in the right headspace to knock a Salesforce implementation out of the park. Take it from someone who’s experienced some of these issues firsthand: this isn’t the right tool for everyone. And that’s okay.
So, how can tell when Salesforce is just not the right fit? Check to see if any of these indicators are present before you commit your nonprofit to the Salesforce Ohana.