CRM application upgrade decision checklist based on business needs

CRM application upgrade decision checklist based on business needs

How do you recommend preparing for a Siebel upgrade? How far in advance should we start, and what are some common pitfalls to watch out for?

    Requires Free Membership to View

    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.

The decision to embark on an upgrade for Siebel or any CRM application should primarily be based on your business needs, not a vendor-driven upgrade schedule. Start a dialog with your business users to consider the pros and cons of pursuing an upgrade. Use these discussions to prepare business users for the possibility that an upgrade may be necessary at some time in the future. Make sure IT pursues the upgrade for the right reasons.

Here is an application upgrade decision checklist for "why or why not" to do a CRM applications upgrade.

Why upgrade?

• Gain the benefit of new functional enhancements
• Compliance changes
• Reduce customizations
• Consolidate instances
• Keep options open for service-oriented architecture (SOA) releases
• Synchronize tools and infrastructure releases
• Get relief from vendor-imposed support deadlines

Why not upgrade?

• Applications are mature, enhancements not compelling
• Risk of disruption to the business
• Cost and resource requirements
• Too many customizations
• Plan to switch to another vendor
• Complex integration with other applications
• Vendor-imposed platform requirements
• Questionable future of the product or vendor

This was first published in July 2007