Home / Why Are Companies Still Using Legacy CMS Products like TeamSite & Vignette?

Why Are Companies Still Using Legacy CMS Products like TeamSite & Vignette?

One of the favorite parts of my job is helping Acquia's sales team in competitive web content management replacement opportunities.

I believe the traditional enterprise software model is broken. The antiquated idea of buying an expensive software license is being destroyed by open source and SaaS business models, which align the needs of the buyer and vendor. But I remain astounded by the number of companies who are still using legacy web content management products, in particular, HP/Autonomy/Interwoven TeamSite and OpenText Vignette.

TeamSite

I spent nearly 10 years working at Interwoven, so I'm very familiar with TeamSite. Much of the core of TeamSite hasn't been updated since the early 2000's, and while the interface has been prettied up a bit, it remains an archaic platform that is too complex and expensive to maintain. Instead of focusing on addressing TeamSite's core product issues to make it competitive in the web content management market, HP/Autonomy has focused on trying to up-sell other products like its search engine IDOL to existing customers. HP/Autonomy simply has no roadmap for TeamSite.

If you are still using TeamSite, I suggest to take a close look at the annual maintenance bill you receive from HP, and see if you can justify spending tens (or hundreds) of thousands of dollars on a product that hasn't changed in many years, and isn't going to take your company into the future. Acquia is frequently replacing TeamSite, including at one of the largest entertainment franchises in the world, who grew tired of its poor authoring experience and limited mobile support.

OpenText Vignette

OpenText is where legacy web content management products go to die. Over the years, OpenText has acquired two web content management companies, RedDot and Vignette. RedDot (now called Web Site Management) is a dead product with no roadmap, and Vignette remains on life support, as OpenText holds onto its few remaining customers. Every few years, OpenText will feign interest in web content management, but their interest is always fleeting, and they quickly revert to their old ways of enterprise information management.

If your company is still using Vignette, it's just a matter of time before you will need to switch. The State of Georgia switched from Vignette to Drupal, at a projected cost savings of nearly $5,000,000 over 5 years.

If you are still using a legacy web content management platform like TeamSite or Vignette (or for that matter, SDL, Ektron, Percussion, etc), I feel your pain. I've put together a Web CMS Selection Toolkit to help guide you through the process of moving off your legacy web content management system.

The Complete Guide to Selecting Your Next Content Management System.
Find out why Acquia's been named a leader in this year's report.
Get Forrester’s insight on the leading solutions to help transform your digital experience strategy.

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.