When working with enterprise content management systems, the decision to upgrade is not to be taken lightly. How will bug fixes and feature changes impact things like prior customizations and extensions (ex. API integrations and third-party tools)? Will performance be impacted (for better or worse)? Will an upgrade make your system more or less vulnerable to security risks? And then there’s the most important question of all: is an upgrade worth the time and cost it will take to get it done?
Earlier this month, HP announced the end-of-life for TeamSite Version 7.2. This announcement marks an April 2016 end-date for support services. For many existing clients, the decision to upgrade will be discussed in conference rooms across the world, and perhaps without resolution until almost too late. With stakeholders weighing the pros and cons of upgrading to TeamSite 7.3, 7.4, 7.5 or even 8.0, there are several areas for consideration.
TeamSite Whisperers are long-time proponents of working with the most up-to-date systems. If you are struggling to make the case for an upgrade, you are likely appealing to two separate, yet equally important groups; the marketing / business team and the IT team. Some may not need convincing at all. But for those who do, we have come up with a simple guide to help you sound the alarm for an upgrade in the most successful way possible.