And, in my experience over the past 15 years, it’s where organizations are willing to spend the most money on technology – often more than on their website or other technology tools – for good reason. Because of this, the deck has always been stacked against open source tools in this arena. The sheer number of vendors providing this toolset for nonprofits is huge (although rapidly shrinking.) Two of them (Convio and Blackbaud) are even publicly traded companies, which says a lot about the profit potential of this vertical.

On the proprietary side, there is a wide range of available tools, from the relatively inexpensive, like Salesforce (web-based, including Convio Common Ground and the Nonprofit Starter Pack,) eTapestry (web-based, now owned by Blackbaud), Democracy in Action, and GiftWorks (desktop) to the egregiously expensive (you know which ones I mean.) Both NTEN and Idealware are the best sources for information about the range of options for this toolset – that’s out of scope for this post.

As you can tell, I’ve lumped SaaS tools like Salesforce, DIA and eTapestry in with proprietary in this post – that’s because that’s what they are – proprietary. However, Salesforce in particular has a leg up that most other proprietary tools don’t have, because of their open APIs and their incredibly robust development platform. That combination is impossible to beat if you need integration, ease of data movement, and a lot of customization. From my perspective, open data (via open APIs) can sometimes be more important to consider than whether or not a tool is open source – since integration with other tools, as well as using external tools of various sorts is critical. Closed data systems, difficult to integrate systems, or systems that require payment to get access to your data should be avoided at all cost.

On the open source side, there are a number options: you can choose an open source CRM package (designed for business), like SugarCRM, and use it or customize it for use in a nonprofit, use CiviCRM, or choose the desktop-based nonprofit CRM called MPX (built by a company called Orange Leap.) I’m excited about a new Drupal project called “Red Hen CRM” but it’s very fledgeling.

CiviCRM is a web-based open source nonprofit-focused CRM/Donation management tool. It’s been around for a while now, and is used by many organizations, some quite large (like the Wikimedia Foundation.) It is quite broad in its feature set – it has donation pages, event management, e-newsletter functionality, even a case-management system. I’ve installed, configured and administered CiviCRM many times, still work with it, and I have, like most developers, a love/hate relationship with it:

• I love that it’s open source/free software
• It’s got a great community of developers and users
• I love that it’s feature rich – you cannot find the whole set of things it does in any proprietary tool that I’ve seen.
• It is a tool that has unmatched cost-effectiveness for small organizations
• It’s great that it integrates with both Drupal and Joomla (although the Drupal integration is by far the most solid – and it is a very nice integration – hard to get with proprietary tools.)
• It is relatively easy to set up for most functionality

But …

• Data migration into CiviCRM is often nightmarish (this is really where the hate lies)
• Reporting tools are improving, but don’t match the proprietary versions
• It can sometimes be pretty tough to handle complex issues
• It can be tough to troubleshoot issues

MPX is a desktop tool, and although it is open source (GPLv3,) unlike CiviCRM, or SugarCRM, it is built on top of a proprietary stack (.Net/MS SQL Server.) It has primarily been used in faith-based organizations (that is Orange Leap’s primary client base.) But it’s a very full featured product, and quite mature.

So if you are a small organization that perhaps is still working with spreadsheets, CiviCRM is a great idea to check out. But in general, there are a lot choices and, sadly, few of them are open source.

In most CRM systems, especially older ones, and ones that are less flexible, some fields can be points of contention for some of us. Gender is one, marital status is another.

CiviCRM, to it’s credit, allows for an arbitrary number of genders – you can define them however you like. My bet (although I could be wrong) is that it’s one of the few out there that allow that. Gender is not a standard field in Salesforce.com contact records, so if you want to add your own, you can customize it however you’d like. There was a very interesting and lively discussion about the gender field in Drupal profiles. Of course, one can always customize these things in Drupal.

For a couple of projects we’ve been working on, we’ve been getting very interested in putting together a really expanded and fleshed out data model for gender, sexual orientation, and marital status. Here’s the first draft. We’d love feedback on this (besides “this is silly/too radical/dangerous/from the antichrist/etc.”). And we also know that even for those who agree that sex and gender are different things, people will differ on how to divide these categories and make sense of it.

• Sex: Male, Female, FTM, MTF, Intersex
• Gender: Male, Female, Genderqueer
• Sexuality: Gay, Lesbian, Bisexual, Queer, Questioning, Straight
• Marital Status: Straight Marriage, MA, DC, IA, VT Domestic, CA-SF 2004, CA 2008, Canada
• Relationship Status: Single, Partnered, Divorced, Dating, Poly  (There probably could be some field dependencies of Marital Status on Relationship Status)

And if you maybe thought that OpenIssue headquarters was in San Francisco, I’m sure this list made you sure. (Yes, we are.)

1. painstaking manual entry
2. painstaking export/import processes
3. tools written by the same vendor designed to talk to each other (which meant that they were generally exceedingly expensive)

Although many nonprofit organizations still find themselves in this situation, there are increasing numbers of tools available to help them out of it. And as more and more organizational processes become web-based (whether “in the cloud” or self-hosted), and as more and more nonprofit-focused software includes open APIs (with some unfortunate exceptions,) nonprofit data is looking less and less siloed, and more and more like an ecosystem – many different software parts talking to others.

NTEN is trying to get a bit of a handle on this with the Data Ecosystem Survey.

I’m very much looking forward to the result – looking to see where this new set of tools that can talk freely to each other is working … and where it isn’t – where there is still work to be done. Please take time to fill it out!

These are two fairly small, fairly low-profile services (although SoapBlox is considered an extremely important part of the progressive blogosphere.) They hosted a small percentage of the blogs out there (in comparison to, say, TypePad or Blogger.) However, this is, of course, devastating to those who had their blogs there.

Lessons to learn:

• Always have your own backup of your data/content
• Remember when setting up a website or blog that if you use a service, the data is not in your hands, but in someone elses
• Always have a disaster recovery plan