Need: Experienced Database Developer. Develop Drupal CiviCRM, migrate to WP

[ChrisKeefe]

CiviCRM Development Request for Bids: Project Deadline 6/1
The Non-GMO Project maintains relationships with over 3,000 grocery retailers and their employees, using CiviCRM 4.2.19 running on Drupal 7.34. The initial build (03/2013) no longer meets our reporting needs. As our scale and sophistication have increased, some questions about the way the data is structured have come up, and many reporting and training needs have been identified. Further, with our websites (http://www.nongmoproject.org,http://www.nongmomonth.org,http://www.livingnongmo.org) running WordPress, we are exploring the cost/benefit of migration.

We are seeking an experienced database developer(s) to support us with the following:
1.   Update, debug, and develop a CiviCRM instance.
2.   Review database and data structure and improve according to our organizational needs.
3.   Advise on and/or perform Drupal>WordPress Migration
4.   Advise on and advance webforms, adding payment processing and tracking.
5.   Develop full reporting solutions.

Requirements:
•   All items must be completed by June 1, 2015. Completion by May 1 preferred.
•   Proven expertise developing and administering CiviCRM on Drupal / WordPress for diverse clients.
•   Quality results & communication:
   o   Measurable improvement in our systems
   o   A proactive approach to understanding client business and IT needs
   o   Willingness and ability to work efficiently with non-technical contacts
   o   Upfront communication style

Below, you’ll find a rough outline of the needs we are looking to address. If you are interested, and meet the above criteria, please email a summary of your qualifications, and a 2-4 page proposal to:
Chris Keefe
Retailer Programs Associate, Non-GMO Project
chris@nongmoproject.org

Immediate Needs
•   Migrate, update, debug, and develop our CiviCRM instance.
•   Confirm whether our database and data structure are meeting our needs optimally, and will continue doing so.
•   Advise on and/or perform Drupal>Wordpress Migration
•   “One-touch” reports:
•   Update Retailer Programs Registration Form with Payment Processing
•   Make Activity history legible at a glance
•   E-Newsletter contact list integration


Optional/Non-Immediate Needs and Questions
•   *What Core Civi functions should we be taking fuller advantage of?
•   Automation of mailings
•   Make Contact UI more legible and less error-prone
•   Configure Dashboard displays to make day-to-day numbers more visible
•   Implement USPS Address Standardization
•   Can we use Civimail to our advantage?
•   How should we be taking advantage of Drupal Users functionality?


About Us: The Non-GMO Project is a rapidly growing international nonprofit, headquartered in Bellingham, WA. It is our mission to protect and build sources of food and products that have not been genetically engineered, and to provide shoppers across North America with reliable non-GMO choices. 

1155 N State Street, Suite 502
Bellingham, WA 98225   
Phone: 877.358.9240 x106
www.nongmoproject.org

[rgridley]

Did you find the resources you needed and did you complete your project on time?  Did you use a firm or independent contractor?  I have been piloting CiviCRM on WordPress for a few months (because I am familiar with WP) and have been wondering if I should consider Drupal.  My organization is considering converting completely over to CiviCRM.  Any details on your experience and who assisted you would be appreciated.

Regards,
Ron Gridley

[petednz]

Hi Ron - I can't answer for Chris on how he got on with their project, though when I last had discussions with them he had left for another project but I can pass on your question to John T.

But your other question about what Drupal adds to the mix can be summed up as follows
- greater integration with users such as
-- civi groups to drupal roles synch
-- civi membership to drupal roles synch
- webform with amazing abilities to handles many civi tasks, contacts, memberships, events, relationships, activities all via one interface
- Views query builder for creating displays of data
- node reference field to civi contacts (useful for linking content with contacts)
- civi entities meaning drupal 'sees' civi entities as drupal entities which gives access to other Drupal goodies like Rules

None of the above is to say you can't do what you need in WP but currently the Drupal toolbox is much fuller.