We just raised a $30M Series A: Read our story

OpenText Documentum OverviewUNIXBusinessApplication

OpenText Documentum is the #6 ranked solution in our list of top Enterprise Content Management tools. It is most often compared to OpenText Content Suite Platform: OpenText Documentum vs OpenText Content Suite Platform

What is OpenText Documentum?

EMC Documentum is an enterprise content management platform that was purchased by EMC from the original developers in 2003.

EMC Documentum offers a range of products that are all highly integrated, secure, and cater for the full information lifecycle. The workplace has become increasingly dispersed, mobile and social, and EMC Documentum provides information solutions to align with these new business requirements.

OpenText Documentum is also known as Dell EMC Documentum, Documentum .

Buyer's Guide

Download the Enterprise Content Management Buyer's Guide including reviews and more. Updated: September 2021

OpenText Documentum Customers

Bank for International Settlements, Postel, GSD&M, Agility Logistics, and E.ON

OpenText Documentum Video

Archived OpenText Documentum Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Romas Bunevicius
Director of Business Development at proit
Reseller
Top 20
It helps us achieve enterprise content management. The biggest issue for us is the high price of the product.

What is our primary use case?

We use this for documentation management. It provides possibilities for us to save documents and supporting the business process while doing so. It helps us with some of the overflow of documents, and that is very important for our company.

How has it helped my organization?

It helps us achieve enterprise content management. It is quite good.

What is most valuable?

It helps us with some of the overflow of documents, and that is very important for our company.

What needs improvement?

The biggest issue for us is the price of the product.

For how long have I used the solution?

One to three years.

What's my experience with pricing, setup cost, and licensing?

It is quite an expensive product. The price is very high. 

Which other solutions

What is our primary use case?

We use this for documentation management. It provides possibilities for us to save documents and supporting the business process while doing so. It helps us with some of the overflow of documents, and that is very important for our company.

How has it helped my organization?

It helps us achieve enterprise content management. It is quite good.

What is most valuable?

It helps us with some of the overflow of documents, and that is very important for our company.

What needs improvement?

The biggest issue for us is the price of the product.

For how long have I used the solution?

One to three years.

What's my experience with pricing, setup cost, and licensing?

It is quite an expensive product. The price is very high. 

Which other solutions did I evaluate?

I would advise others that the best solution for enterprise content management is either Documentum or Microsoft SharePoint.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
VG
Solution Architect / Manager Software Engineer at a financial services firm with 10,001+ employees
Vendor
Lifecycle management enables different business rules for different "states" of content

Pros and Cons

    • "It needs a better UI and it should also be cloud-ready. The UI has not changed in years."

    What is our primary use case?

    We use it for enterprise content management and we have many businesses which use it for business process content management. So we have two categories of users. The primary use case is lifecycle management or flow management and that includes the enterprise content management service.

    How has it helped my organization?

    We have several customers and each one has a different "flavor." So the benefits vary with each case.

    What is most valuable?

    The lifecycle management is valuable because many of our businesses create content and it passes through a lifecycle. Each state of the lifecycle means that your business has certain business rules, which are set.

    What needs improvement?

    It needs a better UI and it should also be cloud-ready. The UI has not changed in years. These are the two major improvements I would be expecting.

    For how long have I used the solution?

    More than five years.

    What do I think about the stability of the solution?

    The stability is good.

    What do I think about the scalability of the solution?

    The scalability is good.

    How is customer service and technical support?

    Technical support is average.

    How was the initial setup?

    I wouldn' say the setup was straightforward but it was also not complex. It's somewhere in between.

    What other advice do I have?

    When selecting a vendor, the primary considerations are the cloud and that we need simplified solutions for all of our customers.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Find out what your peers are saying about OpenText, Microsoft, IBM and others in Enterprise Content Management. Updated: September 2021.
    542,267 professionals have used our research since 2012.
    LI
    Manager - Projects at Cognizant
    Consultant
    Reduced the amount of paper documents; reducing time and errors in the process

    What is our primary use case?

    We use it for content management solutions and processes, such as credit, document lifecycle, etc., in the following verticals: banks, insurances, and so on.

    How has it helped my organization?

    It has reduced the amount of paper documents; reducing time and errors in the process. This has improved people effectiveness and avoided missing documents.

    What is most valuable?

    Ability to build a solution without code. Build solutions based on process and content management.

    What needs improvement?

    It should provide: More Docker based solutions. More support to the cloud (AWS, Azure, etc.). More tools to help clients upgrade solutions based on Webtop.

    For how long have I used the solution?

    More than five years.

    What is our primary use case?

    We use it for content management solutions and processes, such as credit, document lifecycle, etc., in the following verticals: banks, insurances, and so on.

    How has it helped my organization?

    It has reduced the amount of paper documents; reducing time and errors in the process. This has improved people effectiveness and avoided missing documents.

    What is most valuable?

    • Ability to build a solution without code.
    • Build solutions based on process and content management.

    What needs improvement?

    It should provide:

    • More Docker based solutions.
    • More support to the cloud (AWS, Azure, etc.).
    • More tools to help clients upgrade solutions based on Webtop.

    For how long have I used the solution?

    More than five years.
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    it_user5988
    Anonymous User at a tech vendor with 10,001+ employees
    MSP
    Core components provide features such as permissions, auditing, transactions and debugging. The permissions model could be better.

    What is most valuable?

    In terms of sub-products/components, the most valuable features are definitely Content Server and DFC. The core components are the most valuable and trusted ones. These components help us make a solution that can manage documents and their metadata providing features such as permissions, auditing, transactions and debugging for when things get strange. Doing this from scratch may be a good option, but using Documentum we may be able to save some time.

    WDK is also very useful. It's not the best web framework, but it is an acceptable one for most cases and it's directed for a Documentum solution.

    For some users, Webtop can be a good solution. From my experience, a customized version, usually very customized, of Webtop is an optimal solution.

    How has it helped my organization?

    The organization needs to manage a large number of documents. Depending on the context or application, it produces from 50k documents a year to 200k documents a day.

    We designed several solutions for several business contexts. The core of the solution design was the custom-made design specific for the organization, and not the fact that it depended on Documentum. Using Documentum helped in the development process. Application development would be more costly if it was from scratch, rather than using some basic Documentum features.

    What needs improvement?

    Performance could be better. But this is a generalization. We can achieve good performance with Documentum, but we need experience to understand several details about how Documentum works to avoid performance problems. Documentum, out of the box, could be better designed so that we wouldn't fall into these problems so easily.

    Also, the permissions model could be better. For example, I don't understand why we don't have the concept of a read-only user enforced by content server. But I can understand it can be difficult to make a permissions model that can be simultaneously generic and functional.

    Sub-products like RPS and Records Manager are really bad. But I wouldn't hope for improvement here. The mission here is difficult. Trying to make a product that can handle lots of records, millions usually, is a tough mission. We have to be able to apply customer rules you don't know yet, because they're the customer's rules (and exceptions).

    For how long have I used the solution?

    I’ve been using Documentum for 11 years.

    What do I think about the stability of the solution?

    The core (content server and DFC) is very stable. Several sub-products, like RMA and RPS are really bad stability-wise and many other aspects.

    What do I think about the scalability of the solution?

    The core (content server and DFC) are reasonably well scalable. Several sub-products, like RMA and RPS, are really bad scalability-wise and many other aspects.

    The content server could be more scalable if it didn't depend so much on dm_sysobject. The design overuses dm_sysobject without much need. Lightweight objects can be a way of solving this issue. Table partitioning can be useful also, but table partitioning can be a lot of work for solving a design problem.

    How is customer service and technical support?

    I rate technical support 1/5. Whenever I wanted help from Dell EMC, it wasn't for trivial issues. I wanted help from people that have a high degree of knowledge in Documentum and, in some cases, have access to information that I don't (like something I could only know by reverse engineering).

    For sure, some people in Dell EMC have knowledge and can be really helpful, but usually when we submit a case or question, we have to pass through some people that know less than what we know. This makes us lose lots of time asking irrelevant questions for information we already gave. Sometimes we give up before getting to someone with knowledge.

    Other times, our issue really gets to someone with knowledge (after quite some time), and only a percentage of those times the support is helpful. Also, Dell EMC doesn't support Documentum's versions for a long time. You quite often see Dell EMC personnel saying Dell EMC does not support old versions when, for most situations, we can see the issue would not be any different in the most recent version.

    How was the initial setup?

    Initial setup was complex. Several times we started with a solution. Then, in production, we started to get problems concerning performance or complexity, because we tried to use a product that needs to be generic to our customer specific solution. Then usually, when we address the problems, we figure out that replacing some Documentum-specific features with a customized feature (usually a simple one) can be a huge improvement.

    What's my experience with pricing, setup cost, and licensing?

    I'm not an expert on this but from what I know, the pricing and licensing model is strange and I'm not sure how well it is controlled. For example, paying by user capability (consumer, contributor, coordinator) makes sense when the user application is Webtop. But we can have a WDK solution or any other web-based solution where the user capability is completely irrelevant.

    Which other solutions did I evaluate?

    I was not involved in product evaluation. The organization evaluated FileNet as one option, but I can't say much about it.

    What other advice do I have?

    Stick to the core (Content Server, DFC)! I don't want to say WDK because Dell EMC is/was always saying it was going to end it. Otherwise, it was something to consider.
    Dell EMC made DFS, which was a logical approach. But for several users (like myself), if you design web services by yourself using plain DFC, you’ll get better web services and it's not that complicated. Of course, you're not going to provide all the functionality DFS provides, but you won't need it.

    Make it simple when possible! When you need something more complex regarding specific functionality or great performance, consider custom development. Don't assume that because Documentum has a feature addressing what you want to do, you should use it. Do the pros and cons first.

    You would want to block the generic interfaces and customize your solution, unless:

    • Your solution needs to manage only a few documents.
    • Your users are IT people that understand what they should or should not do with an interface as generic as Webtop or CenterStage.
    • You use DFS services without being very careful (performance-wise, for example).
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    ITCS user
    Change Manager at a tech services company with 51-200 employees
    Consultant
    Nice for document management but it's not too flexible

    Valuable Features

    Lifecycle management

    Improvements to My Organization

    We use it as a repository of our records.

    Room for Improvement

    The interface is not user-friendly, new meta data classes are not easy to create.

    Use of Solution

    6 months

    Stability Issues

    Not too stable.

    Customer Service and Technical Support

    Customer Service: AverageTechnical Support: Average

    Initial Setup

    Complex. We needed external help to set it up.

    Implementation Team

    Through a vendor team.

    Valuable Features

    Lifecycle management

    Improvements to My Organization

    We use it as a repository of our records.

    Room for Improvement

    The interface is not user-friendly, new meta data classes are not easy to create.

    Use of Solution

    6 months

    Stability Issues

    Not too stable.

    Customer Service and Technical Support

    Customer Service: AverageTechnical Support: Average

    Initial Setup

    Complex. We needed external help to set it up.

    Implementation Team

    Through a vendor team.
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    ITCS user
    Sales Engineer at a tech consulting company with 11-50 employees
    Real User
    Documentum was stable, but it did not serve our business well

    What is most valuable?

    Version Tree Branching. Bulk document edit. Hierarchal navigation. Document annotation. At the time webtop was an integration point we wanted into our products CM.

    How has it helped my organization?

    We were able to meet ISO 9001 QMS Standards and add a more robust CM integration to our product base.

    What needs improvement?

    After implementation, I was pleased with the functions of the application. Design and newer functionality should always be evolved.

    For how long have I used the solution?

    I used this solution for approximately 5 years.

    What was my experience with deployment of the solution?

    Yes, system deployment was complex and very tedious.

    What do I think about the stability of the solution?

    No, after the deployment, we found the system to be reliable. Not the fastest system, but stable.

    What do I think about the scalability of the solution?

    Never had to scale to meet demand.

    How are customer service and technical support?

    Customer Service: I would rate the service below average. This was three years ago, so maybe it has improved since.Technical Support: Support was average. My involvement was not only user level, but development integration level also. I had more difficult questions I am sure than the average user.

    Which solution did I use previously and why did I switch?

    We had integrations to several content management applications. We ended up not choosing this option in-house as we felt it was too much. Just not a good fit for us.

    How was the initial setup?

    The initial setup as per their install guide was pretty spot on. As we customized, it became more complex. This could be due to our unique business rules or because we were building an integration to the software.

    What about the implementation team?

    Ours was an in-house implementation. We did lean on support a few times and it was average support if we were not dependent on a time line.

    What other advice do I have?

    Be sure that you can invest the time for implementation on this also, use their technical services team. The software does what it says it does, but make sure you have considered cheaper options.
    Disclosure: I am a real user, and this review is based on my own experience and opinions.