Frequently Asked Questions

Q. What is the DropCRM Project?
A. The DropCRM project has formed to encourage collaboration a on a number of different software components that we feel can form a solid foundation for building CRM Features for Drupal 7. DropCRM is not a specific piece of software, although the closest thing might be the upcoming Drupal 7 release of CRM module. There are also plans to eventually release a DropCRM distribution and/or Install Profile.
Q. When will CRM module or the DropCRM distribution be released?
No one knows. It's done when it's done, although we expect the "release early, release often" philosophy to prevail. If you want to speed things along, check out how you can help.
Q. Is DropCRM designed primary for commercial organizations / online businesses?
A. Not in particular, although such use is fully expected. The DropCRM team wants to help build generic components that can be used for creating CRM functionality of many kinds, and for packaging those components together in pre-configured forms for many use cases, including both commerical and non-profit.
Q. Will there be a migration path from CiviCRM to DropCRM?

A. This is obviously desirable, and is one of many goals being discussed among developers who have committed to the DropCRM project. However, it's a complicated undertaking, and is unlikely to be an immediate top priority unless one or more organizations planning to migrate provide financial sponsorship.

The primary objective is to allow developers to build CiviCRM-like functionalities using Drupal's APIs, tools, and conventions. Elsewhere this concept has been referred to in relation to "verticalization technology."

Q. How will DropCRM support Joomla users? DropCRM will never replace CiviCRM because it won't support Joomla users.
A. Joomla users already download an install a huge collection of third-party libraries when they install CiviCRM, whether they realize it or not. The Drupal layer under DropCRM could be provided just as transparently. If the CiviCRM project were to leverage DropCRM tools, it need not inhibit the ability support other CMSes in any way.
Q. Is DropCRM an API / UI / integration layer that interacts with the CiviCRM data model?
A. No. DropCRM envisions defining a new data model that is not compatible with the current CiviCRM data model, although a migration path is conceivable. Regardless, CRM module is expected to provide integration with all kinds of entities that are analogous to CiviCRM entities, including Contacts, Relationships, Groups, Events, Payment/Donations, Postal Addresses, and Mailing lists.