This site uses cookies to improve your experience. By viewing our content, you are accepting the use of cookies. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country we will assume you are from the United States. View our privacy policy and terms of use.

Remove 2009 Remove Doc Remove License Related Topics
Synchronous Copyright Calendar Files Mail Feeds Analytics Script Unconference Application More Related Topics >
article thumbnail

Integration of CRM and CMS

Zen and the Art of Nonprofit Technology

JANUARY 14, 2009

Depending on the CRM, some require additional license fees for forms or APIs. Some take internal staff resources (especially the Manual strategy.) Others take developer resources (especially the Integration strategy.) So what’s the right strategy? That totally depends on a few factors. First, are you happy with your current CRM and CMS?

Integration 100
Integration API Drupal Open Source 100
article thumbnail

Case Study: Moving to Google Apps

NTEN

FEBRUARY 7, 2011

In 2009, we finalized a technology plan. At this point, the servers were aging and needed to be replaced, and we needed new software and user licenses (MS Exchange Server), as well. When the analysis was done, I created a proposal with my recommendations, which was approved by October 2009.

Case Study 84
Case Study Google Studies Tutorial 84
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

 

Stay Connected

Join 17,000+ professionals by signing up for our newsletter

About
About
Editions
Editions
Topics
Powered by Aggregage | Terms and Conditions | Your California Rights and Privacy Policy
© Aggregage 2024