In late 2009, we were looking for a better solution for one of our larger faith-based clients. The AMS and CRMs we investigated were either too expensive or too simplistic. We had taken a hard look at CiviCRM about a year earlier, but we didn’t think it was ready. However, with the release of CiviCRM 3.1, CiviCRM was more mature and gave us the flexibility and Drupal integration we needed. CiviCRM was ready and so were we.
I am often asked by our clients to help with hire a CiviCRM administrator. This can be a new hire or a promotion of someone within the organization. Although every organization has specific needs, I've found the below job description to be helpful as a starting point. Hopefully you can find it helpful as well.
Starting with version 4.2 and 4.3, CiviCRM has incorporated sophisticated financial batch capabilities. However, for organizations switching from another CRM or financial system with batches, there is currently no capability to import batches or associate contributions with batches through the standard CiviCRM import process. (Hopefully this capability will be added.) This means that one must either manually create batches and manually associate contributions to batches or load the batches and then create the association through database inserts.
Vanco Payment processor
BackOffice Thinking is pleased to release the Vanco payment processor to the CiviCRM community. Today we are releasing versions for 3.4x and 4.1x and hope to have a 4.2x version shortly.
This processor allows single payment and recurring for credit cards and ACH (electronic check)
The Vanco payment processor is quite popular among religious organizations and we have been utilizing this processor for past 2 years with many of our clients. Thanks for all the support from the Vanco team along way.
We are looking forward to a great turnout o Tuesday. If anyone has any questions that they'd like addressed please send them to me by Monday.
We had another excellent meet up on Tuesday (June 12). Our attendance was lower due to the terrential rain. I was impressed that Dan actually was going to bike home 20 minutes during the downpour.
Just a quick shout out to all those who attended the Philly CiviCRM meet up earlier this month.
I thought the session was excellent. 2 hours straight of Q&A with a host questions and a lot of excellent experience shared. I think we all learned a lot and are looking forward to our next meetup.
If you're in the Philly area on June 12, we'd love to see you. Hopefully Byron won't eat all of the Oreo's next time!
How much server (disk space and memory) do I need to run my CiviCRM implementation....
The answer is, of course, it depends. But what are the critical factors?
-- Data base size (Number of contacts and number of custom data fields, relationships, groups, etc.)
-- Number of users (light usage vs. heavy usage)
-- What other applications will be running? (A CMS with a small data base or Jasper Reports with a lot of simultaneous users.)
I think it would be good to put forth some guidelines or rules of thumb.