Common problems with Software as a Service (SaaS) implementations

Common problems with Software as a Service (SaaS) implementations

What are common problems with Software as a Service (SaaS) ERP implementations with CRM integrations, especially on the host side, and how should we plan for them?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning editorial writers on the latest customer relationship management (CRM)and call center technology issues today. Our goal is to keep you informed on the hottest issues facing this fast-changing industry.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchCRM.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchCRM.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

A SaaS implementation for ERP and CRM is a big deal and you do need a plan, but even before that you should be looking at your business processes and asking yourselves what kind of support those processes need. What applications are involved? Where is the data stored? What kind of response times are needed? Can you work with a batch update to the data once a day or do you need near real time access to new data regardless of which system owns it?

Batch data updates tend to be relatively easy and there are extract, transform, load (ETL) tools to help with the process. For more real-time data sharing, you need integration technology or middleware and you need to evaluate the options out there. I can't tell by the question if both your ERP and your CRM systems are SaaS or just one, but any time you deal with SaaS you need a service level agreement (SLA) and if the two systems are from different vendors you need to consider what happens if one system is down — how is transaction data stored etc.

This was first published in November 2007