content services

Enterprise Content Management: Transitioning to Content Services

For organizations who have been using FileNet, OpenText and Documentum, the need to plan a transition to alternative solutions is looming large. That is why many 2018 IT budgets include line items for projects to migrate enterprise content management (ECM) applications and replace ECM technologies.

Note: This is part three of our three part series on technology that is taking a leading role in IT budget this year. You can catch the first one, File Analytics: Shining Light in the Darkest Corners of Your Stored Content and the second one, Application Decommissioning: Stop Paying for What You Do Not Use.

The big change in this space is the shift from the unwieldy ECM platforms built by vendors through acquisition to more flexible ECM services frameworks. While almost everyone shares the understanding that this is a good evolution, navigating the transition remains a major challenge.

Your ECM Transition Plan

The key is to assess your current use of ECM technologies, break it down into its component parts, and commit to a project to transition at least one ECM application into a new, less expensive and more flexible environment.

The project should focus on an ECM application that does more than act as just a repository; it should also include workflow and integrations with other applications. Migrating that solution to a new environment will go a long way toward helping you understand the capabilities of the new services-based ECM frameworks, and provide a template for additional application migrations.

Your 2018 budget summary for ECM Transition

What? Select an ECM application for the transition off of Documentum, FileNet or OpenText.

Why? The major ECM platforms are more than twenty years old, and the vendors are taking actions that suggest the end-of-life is near. It is critical to understand how to rebuild our ECM applications in new, more flexible ECM technologies that provide the functionality required but in a lower-cost and more flexible architecture. By migrating one application, we will know a lot more about our options when we have to migrate all of them.

How Much? Migrating an ECM application to a new environment is a major undertaking and the cost pivots on the question of “which application?”. Any enterprise ECM application deployment is going to cost upwards of $150,000, with key parameters being the amount of integration with other systems, the content migration requirements, and the complexity of the business process (workflow) steps. The payback, however, can be very high if the project illuminates the path to moving off of a legacy ECM environment with its accompanying high costs.

For more ideas on your ECM transition plans read, Six Questions to Ask Before Your Next Content Management Project .

Sign up for our newsletter to get regular updates on our blog, podcast and webinars related to content management and information governance.