Over the last few years my organization has migrated close to 500 nonprofits to the cloud — from very small nonprofit organizations (sometimes all-volunteer-based) to large national institutions. It does not matter if you are small or big or if you are moving to the cloud to manage your donors, volunteers, dogs, cats, or trees: there are some things that you should keep in mind. Here are my top ten (and a bonus one at the end).
1. Do your homework
You might never be able to debate the merits of Apex code (the programming language that executes on the Salesforce platform), for example, and that’s okay. However, before you start your migration to the cloud, figure out what you want and what is possible; reach out to other nonprofits in your sector, consult with volunteers and board members, and read related publications.
Implementing a constituent relationship management (CRM) application can be a difficult project for organizations with multiple large complex departments. Rolling out a solution that caters to your development, marketing, program, and HR departments could be challenging due to the different strategies, processes, and products.
Salesforce CRM encompasses the people, processes, and applications that enable organizations to organize and manage their constituent relationship. A successful implementation needs a holistic approach that aligns staff training and changes in business processes with constituent needs through thoughtful planning. It also entitles implementing applications that will automate and consolidate constituent information. If CRM isn’t helping you to become more effective, increasing your constituent retention or improving staff satisfaction – don’t do it.