We recommend and use CiviCRM with most of our clients, and have since 2005. It's got a fantastic collection of functionality that fits the needs of non-profit organization communications, and the CiviCRM community of developers and users is growing, broad, vibrant and responsive.
The best part? When I describe to potential new converts how all of their constituent relations (donations, membership, mass emails, etc.) can be managed with a single integrated, configurable tool, I can hear an incredible yearning at the other end of the phone.
CiviCRM makes it possible for non-profit organizations, even those with a limited budget, to forge strong relationships with their constituents, thus bringing them closer to fulfilling their mission. Over the years, we have seen CiviCRM develop and evolve in a very responsive way to the needs of the marketplace.
AustLII is the leader in the free access to law movement and has a philospophical bias towards open source systems. After investigating all the other possible major alternatives it seemed logical to turn to CiviCRM. We have software developer resources, and though it is not core business, we may be able to direct some of these resources towards improving CiviCRM for the community.
CiviCRM is helping us serve member-based community organizing groups across the
U.S. to keep better track of their events, fundraising, and membership data. It's helping our community to aim higher in terms of what kind of questions they should be asking and what kind of data they should be collecting. We chose CiviCRM because it's the best all-around tool to do what our groups need, AND because it's open source.
From fundraising websites which really connect you with your donors to essential tools for care organisations to manage their data, Civi has allowed us to do some amazing things for our clients. It's such a flexible platform and has such a great community which we're proud to be a part of.
Freeform Solutions uses CiviCRM to help the non-profit organizations we develop sites for to manage information about their members, volunteers, activists, donors, employees and other contacts, and to handle donations, correspondence, mailings and more. We support the CiviCRM community by contributing documentation, patches, modules and code, and are a silver sponsor of CiviCon 2013.
Implemented CiviCRM in 2011 now use it as a complete CRM solution for the organisation. Looking to extend its use in the next 12 months though the use of Civi PCP;s and Civi HR and deeper web integration.
We recently had one of our groups report that merging data was resulting in data loss. Specifically, when they merged two records, they noticed that the contribution records on the record that was deleted were not carried over to the record that remained.
I investigated and found the culprit: we were missing a foreign key constraint between the contribution table and the contact table. In fact, we were missing a lot of foreign key constraints in this database.
The ability to create petitions in CiviCRM was a tremendous move forward for people using CiviCRM for political organizing. The petitions feature took another step forward with the Petition Email extension, that allows copies of your petition to be automatically sent by email to a given target. However, the holy grail of e-advocacy was still just out of reach: automatically sending your petition to the petition signer's elected official.
When generating mailing labels, CiviCRM users have the option of choosing the address to be used (e.g. you can select "Primary," "Home" or "Work") depending on where you want to reach your contacts.
CiviMail, however, does not provide this option. Instead, CiviMail automatically chooses the address for each contact - a process we can only control on a contact-by-contact basis by setting the "Bulk Mail" or "Primary" flags for each individual contact.
Have you ever completed a training a wondered whether usage of your CiviCRM database changed as a result? Have you ever wondered who were the major database users in your organization and who might need more prodding?
With the 4.3 upgrade, the Progressive Technology Project has made a number of important steps toward breaking out our work into pieces that others can use on their sites. This blog will begin a series of (hopefully) weekly blogs outlining new functionality that others can use.
Our first blog features the civicrm_petition_email Drupal module. Thanks to the hard work of agh1, a Drupal 6 version of the module is available (https://github.com/agh1/civicrm_petition_email). We just finished porting it to Drupal 7.
Progressive Technology Project has released a new Drupal module called CiviCRM Cicero that integrates with the Cicero service from Azavea. If you are using CiviCRM with Drupal, you can now add legislative district and more information to your database.
Last spring I started working on a Drupal module that would keep CiviCRM contacts in sync with Salsa contacts. I did a lot of the work on it and then, upon joining PTP's staff, the project unfortunately fell to the bottom of my stack.