Tips and best practices for implementing open source CRM
By Richard Boardman, Founder, Mareeba
SearchCRM.com
However, there are a few areas where I think you may need to pay more attention when implementing open source CRM technology. While you can get a lot of functionality for little or no money with open source CRM, I've generally found that you don't get the breadth and depth of functionality available through commercial packages, and some of the features you might take as a given in mainstream applications aren't necessarily included. This makes it even more important than usual to identify your needs, match them against the available functionality and have a good plan for filling the gaps.
Another challenge w
Requires Membership to View
To gain access to this and all member only content, please provide the following information:
By joining SearchCRM.com you agree to receive email updates from the TechTarget network of sites, including updates on new content, magazine or event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile or unsubscribing via email.
TechTarget cares about your privacy. Read our Privacy Policy
ith open source CRM software is that it is often more difficult to find capable implementation partners than it is with other applications. I'd imagine this reflects the fact that open source tends to be adopted by smaller, lower-spending organizations, and that the absence of margins to be earned on the software means there aren't the commercial foundations for an extensive network of suppliers offering the full range of support services. This means that you may need to be more creative in accessing resources, perhaps working with a number of suppliers and freelancers, and you would need to be even more careful than normal in terms of due diligence, especially in terms of ongoing financial viability.
Lastly, I think that the fact that open source software is free causes many organizations to set unrealistic expectations for the overall project budget. You're going to need to do things such as gather requirements, customize software, migrate data, integrate with other systems, project manage, train staff, etc., regardless of whether the software is open source or commercial. You're likely to need outside assistance to do this, and it will cost you. I think a lot of organizations head down the open source route unaware that there may be a significant service cost element if they are to be successful.