OpenText Documentum Content Management Reviews

We are using it to archive the information about our sales.

I am satisfied with OpenText Documentum so far; it has great integration capabilities. The connection with our API and SAP is useful, as you can use their SAP interface.

The key point that my company decided to go with OpenText Documentum is mostly because you can integrate it with many other tools such as Salesforce.

The interface of OpenText Documentum could be more intuitive; sometimes it is hard to find where the information is located.

It is a fresh experience as I just started to work with that.

We are planning to do an upgrade to Documentum X plan, the new version; I have been working with that for one month now.

We are doing fine; the initial setup and deployment process overall is going smoothly.

It will take another 3 to 4 months to fully upgrade to the next plan.

I have contacted the OpenText technical support team regarding Documentum with questions about how to define the number of licenses needed for the usage of the product because I did not really understand how it is defined.

My experience with the support overall is that they are really responsive and helpful.

This is my first time working with a platform such as OpenText Documentum, so I do not have a comparison.

The price that we are paying for OpenText Documentum is similar to our competitors, so I am aware that it is on the same price level.

One of my colleagues has found some automation features.

It is not my responsibility regarding security features; I am new to this job, so I do not have those responsibilities now.

I am not using any AI features with OpenText Documentum, but my company is evaluating some AI integrations.

I would rate OpenText Documentum seven to eight out of ten; it is good, but I always think that you cannot assign more than an eight.

We primarily use it for storing documents. We host a variety of documents in OpenText Documentum. This includes raw files, analyzed files, and documents in multiple formats. 

One major thing we've faced is that it doesn't support files directly coming from machines in their original format. We need to convert these files into PDF format, which is a manual process.

The primary challenge was migration. We have been using our own in-house product for the past 15 years, storing documents from that period, resulting in over 50 million+ documents in our system.

The migration process was particularly challenging. We needed to replicate a similar structure in OpenText Documentum, but our software didn't initially provide this capability. We had to request the implementation of some add-ons to facilitate the migration.

Another significant issue was the usability. The directory structures and overall system were not straightforward or easy to understand. These were the major challenges we faced and moved to Documentum.

We conducted a survey, and some employees initially struggled with the new UI, having been accustomed to the old one. But, after providing training, they became comfortable using it. It's a UI preference, and opinions vary from person to person.

The product increased the overall productivity by around 20% to 30%  because we divided the repository. We store over 50 million documents. So, we split those documents, some in Nuxeo, and some in Documentum. So, it definitely boosts our productivity because it's easier to load and manage. But it's not solely due to OpenText. 

We also divided those documents into other software solutions, multiple software solutions, to enhance productivity. So, it does boost our productivity. That's why we purchased it.

Moreover, OpenText Documentum actually helped simplify accelerate our modernization journey.

Documentum Security Protection is quite nice. Our main business involves hosting Syngenta data. We operate in the agricultural sector, and numerous scientists work across various continents conducting research. 

When they analyze something, we host the resulting raw files and other data. We store these files in a central location and provide access to them using this software. So, it's a crucial aspect of our operations.

The main issue is the software's performance when storing around 10 million or more documents. It becomes slow and needs improvement. Perhaps it's a cloud-related issue, but it needs to be addressed. It could be due to our S3 bucket or something else. Nevertheless, this is a significant challenge we're facing.

Additionally, OpenText doesn't support certain file formats, such as .rai. Some of our analyzed documents come directly from machinery. We utilize an IoT device, and some of the analyzed document files are directly generated by the machine. We then store them in the S3 bucket. 

However, when attempting to import these documents from the S3 bucket to OpenText, they fail to open. This is the primary issue. As a result, we have to convert these files to PDF before they can be opened. 

So, I hope for improved performance, particularly with a large number of documents, in future releases of the solution. Currently, our old software stores only eight million documents. However, we have over 15 million documents in our legacy software because we've been using it for the past 15  years across the globe. We have over 50 million documents in total, but only eight million are currently stored. As a result, the performance was slow, comparatively slow.

I have experience with OpenText Documentum, but we are in the process of migrating our repositories to our in-house product.

I have been working with OpenText Documentum for three years. We use the latest version. 

It's absolutely stable. But it's important to note that all 6,000 users are not logging in at the same time. Only a small fraction of users, for example, 500 to 600 log in simultaneously. So, while the scalability is good, it's not meant to handle all 6,000 users logging in at once.

It is quite scalable because currently, around 6000 users are using it.

The customer service and support are responsive. However, Nexus's support is better.  

Neutral

We had our own software, but it was slow, prone to hanging, and had security issues. Our document repository is similar to OpenText in terms of its features and functionality.

During the COVID pandemic, there was a virus attack, and we lost some crucial documents and data. That incident prompted us to consider alternative software solutions. 

We wanted to consolidate our document storage and avoid the risk of data loss due to scattered storage across multiple software platforms. Currently, we're managing the backup of all the documents.

I work as an assistant product manager, so I was involved in the installation and deployment process.

We evaluated Nuxeo. We worked with both Nuxeo and OpenText simultaneously

Overall, I would rate this solution a seven out of ten. 

Our old software was a bit better. Our old software was designed specifically for our requirements. It incorporated all our needs and attributes perfectly. OpenText, on the other hand, is a more generic solution, and it doesn't cater to our specific needs as well.

We use OpenText Documentum for managing the command life cycle and for content management.

Documentum helps by saving time during daily operations.

The product is user-friendly.

The BPM side should be improved. It would be beneficial to have more ability to customize features for specific use cases.

I have been working with OpenText Documentum for ten years.

In terms of stability, I would rate it as seven out of ten. For example, database connections could be improved.

When talking about scalability, I would rate the ability to scale and expand as eight out of ten.

The setup process can be complex.

Our team comprised of four people handled the setup.

With regard to pricing, I would rate it as four out of ten. It is quite expensive.

I do not have real experience with other solutions to compare with.

I recommend Documentum for large enterprises. Additionally, it would be great if the solution could include certain functions in-house rather than requiring third-party tools.

I'd rate the solution seven out of ten.

We are doing a big project with court systems, developing solutions about use cases, core use cases, and on a national level. We work with seven in courts, which pertains to the court system. It is a big government institution, specifically the department of Lithuania, involving about 50,000 officials and 30,000 users.

It is a very good solution for text analysis and supports some significant automations, creating considerable value for our customer.

The most valuable feature is the good automation engine, which helps in reducing the development cost and allows easy development of applications. Another important aspect is its ability to support big systems, which is crucial for developing content management for large-scale systems.

The price is quite high as the licensing prices are significant.

We have been doing some projects for about eight years.

They are supporting some AI solutions, and the platform is quite good regarding automation, which is important for handling large systems.

Their customer service is good, with a rating of about seven or eight out of ten.

Neutral

We discussed the possibility of using other solutions but have experience with OpenText.

It was quite an easy deployment, though it took more than a year for the last project. It is necessary to understand the logic and programming required for development.

Our implementation team consisted of about ten to 12 people, including project management, architecture, developers, and Scrum Master.

I don't remember exactly the figures for return on investment, however, there was a significant return.

The licensing price is quite high, rated around seven or eight out of ten for pricing.

We are working with OpenText and have considered other options but currently have experience with this solution.

I recommend Documentum as it supports big systems and offers good integration. It is one of the best solutions for big systems.

I'd rate the solution ten out of ten.

I started my journey with Documentum as a software developer. I then worked as a consultant to help customers use the solution. I have worked across various industries like media and publishing with customers like McGraw Hill, banking, insurance, and aviation. There are any use cases. The product gives us the flexibility to configure it the way we want for our business domain.

Customers who don't use Documentum use emails and documents placed in file stores. Documentum enables users to organize the documents. As a whole, there is a single source of truth for the entire organization to work with. It really saves time spent looking for documents and brings in more productivity.

It's a great enterprise content management product. Our customers love the product for its stability and scalability. Search is the most useful feature of the solution. The way we retrieve documents is more important than how we store them. There's no use if we can't find a document. It's the most critical feature.

My organization works with other customers. We are consultants for OpenText. Our customers have seen a lot of benefits in terms of regulatory compliance. Industries like banking are highly regulated. The product captures the information centrally so everybody in the bank can see the right information at the right time. It is tamper-proof and enables us to return to the document source, which is helpful with legal issues.

The user interface can be a bit more intuitive. OpenText has made an effort to improve the UI from where it was to where it is today. However, I think it can be improved a lot more.

I have been using the solution for the last 20 years.

It's the most stable product I've seen in the ECM space.

Documentum is the most scalable product I have seen so far.

Off late, the support team has been responsive. Before, we had to escalate things to get them done.

Neutral

Some of our customers were using IBM FileNet. It was not very intuitive. Documentum is much more easy to manage and configure.

Each installation is very different because each customer has different solutions in their ecosystem. The product does give us connectors to work with various industry-leading solutions. Often, we have to be innovative to develop our own integration points.

We encourage the customers to share their roadmap. It's not just about installing Documentum and catering to their current needs. We also look at how it works with the customer's existing ecosystem and encourage them to establish a roadmap. Then, we have a better approach to how a customer can benefit from it than just using Documentum as a silo application. We are integrators.

The ROI is not measurable.

There are a lot of cheaper options in the market, such as Dropbox. It camouflages itself as an enterprise management solution, but it is not. Enterprise content management is not about storing files. It's more about collaboration, workflows, version management, and security. It is where solutions like Dropbox fail.

At times, customers have a perception that they can do the same thing with Dropbox and wonder why they must invest so much in Documentum. Here, the value gap or communication is lost. We communicate the value of the solution to the customer. There is scope for reducing the cost to some extent. We cannot always expect organizations to have a minimum of 250 users.

For licensing, we can also look at organizations with 50 members. It's an entry point for us if they see value in it. We can always leverage other OpenText products.

We look for second-tier options if the customer is really stretched for budget. It is a suboptimal arrangement. We often encourage customers to stretch their budgets and choose Documentum as a long-term investment. The tool provides value for money.

The product's security is top-class. It is very secure in terms of the level of access we can work with. The underlying encryption is pretty strong. It's very difficult to break in. We use Capital Projects for asset management. The industry-specific flavors of the solution reduce the time to deploy because most of the use cases are already thought through. Otherwise, we would have had to develop or customize the product to meet our requirements. The product gives an extra edge for a faster time to market.

We use Documentum's integration points with leading business applications for our customers. We have integrated the tool with Microsoft 365, SAP, and Salesforce. The integration of Documentum with leading business applications is quite critical for us. Users have various avenues to work with documents and collaborate. If we don't have integration, the users will have to work with silos, and there will be a lot of content duplication. The productivity will go for a toss, and we'll have multiple versions of the truth, which will be very inconvenient.

The configurability of Documentum is pretty good, especially with D2. It's very configurable. It leads to less customization. Documentum has helped boost productivity within our organization. How we implement the solution is also important. The product brings in at least a 30% improvement in productivity.

Documentum has certainly helped simplify and accelerate our modernization journey. There was a case in a bank where all the documents were stored in a network drive, and everyone needed to know where the document was. With Documentum, the same document was made available to everyone with a click of a button. Finding documents with metadata and version management is very easy. Teams are able to integrate and collaborate better with Microsoft 365 and Salesforce easily.

Overall, I rate the solution a nine out of ten.

It serves as a content management solution at our company, Chevron, where it plays a crucial role in managing the extensive documentation associated with various aspects, such as sales and field operations.

When a field mechanic needs to inspect a pipeline to identify issues, they follow a specific procedure marked by a PSA code. In such cases, they need to access relevant documents stored within the Documentum system, which isn't stored on their personal devices like laptops or iPads. To access these documents, they simply open the Documentum app, enter the assigned PSA code, and, voilà, the system retrieves the associated documentation, including the structural details of the pipeline. 

This quick access enables the mechanic to efficiently pinpoint and address the issue right on the spot, not only facilitating field operations but also ensuring the security of sensitive data through robust implementation.

It provides extensive accessibility to our content, and it's a vital component in our work processes. We've gained access to a plethora of applications through OpenText, which enables us to enhance our services for customers. 

One notable example is the integration with Xfinity ECM, a solution that seamlessly integrates with SAP. For instance, when someone working with SAP needs to access a specific invoice document, SAP itself doesn't store these documents, instead, the content related to the invoice number seamlessly flows through Documentum. 

It offers robust security features and it allows to leverage a variety of plugins from OpenText to enhance security. For example, there are plugins like Trusted Content Services that allow you to encrypt entire documents for added security, though it's essential to be aware that this might impact performance. 

It is a highly potent content management tool. It stands out for its impressive records management capabilities and the ability to handle an extensive volume of documents, even reaching into the billions.

The documentation often leaves customers feeling somewhat frustrated, as OpenText seems to expect customers to remind them constantly about the need for better documentation, as they don't provide clear guidance on their documentation practices.

I have been using it for eighteen years.

Its quarterly release schedule for new versions is appreciated, but it often introduces bugs that inconvenience customers. This puts customers in a dilemma between not upgrading and falling behind or upgrading and dealing with issues. Mobile apps provide seamless and automatic updates with minimal user hassle. I would rate it eight out of ten.

OpenText offers a wealth of service engines and components that can be seamlessly integrated with Documentum, enhancing its capabilities significantly. It has shown excellent versatility in supporting various databases, with Oracle being notably powerful in this regard. I would rate it eight out of ten.

The application has been upgraded, and the majority of relevant articles have been updated within the last two years. This means that when I used to search for solutions in the past, I often had to connect with support and wait for assistance.  The shift towards a more self-service approach, where knowledge is readily available, has significantly improved the support experience. It provides direct support with a dedicated support engineer, which further enhances the overall support quality and about forty to fifty percent of our smaller issues can be resolved by referring to articles available, without having to open a ticket.

In the past, Documentum and SharePoint were often seen as competitors, running side by side in many organizations. However, this came at a significant cost, especially when Documentum was owned by BMC, which had a different licensing strategy. Nowadays, Documentum has emerged as a robust competitor against SharePoint. 

SharePoint has limitations when it comes to handling large volumes of data and lacks comprehensive records management features. When it comes to document retention, Documentum is a strong choice, emphasizing the importance of maintaining a clear document retention lifecycle. Previously we used content management systems like FileNet and eRoom at Chevron. However, neither of them is in use anymore. 

The reason is that Documentum is a robust, heavy-duty vehicle capable of handling a substantial load and it excels at managing and handling heavy workloads, which signifies the vast amount of content and documents efficiently.

The initial setup was relatively easy for me as I had prior experience. However, for newcomers, there might be a bit of a learning curve, especially when it comes to navigating the documentation.

Regarding pricing, although I'm not directly involved, I've heard from my manager that the pricing has improved significantly. The price is considered affordable now.

It is important to note that it follows a strategic approach of releasing updates incrementally every quarter, rather than providing a complete package all at once. It offers support for hostless SQL using an OpenText open-source database, which is known for its lightweight and efficient nature. Overall, I would rate it eight out of ten.

We use Captiva and Webtop. Webtop is a regular Webtop. CenterStage is also there. So these three products are mainly integrated with OpenText. And for third-party, we have SAP. We have PTW, that is Permit to Work, which is an in-house product and integrated with Documentum because all the data (files and metadata) will come into Documentum.

The version control capabilities are the basics of Documentum. Everyone uses that one.

The organization still uses Documentum because it's tightly integrated with two applications, which they cannot move on from. There is SharePoint, which our organization uses, and about 30% of the data has moved from Documentum to SharePoint. But there is no roadmap for Documentum yet.

We did for xECM in, I guess, 2019. We gave the proposal to move to xECM, which is OpenText Cloud. But due to the cost issue, the organization did not agree to move to it.

The most impactful thing is the size, which is almost 25 TB. 

Documentum's integration capabilities with other systems has largely impacted the workflow. That is the main reason they have not decommissioned it.

The main thing is the cost. Most of the time, organizations move away from Documentum due to cost. It's highly-priced, and the support costs are high. Now, SharePoint and other options. Microsoft gives free licenses, so organizations mainly look for cost-effective products.

The second thing is updates and patching. We patch very often, every six months or a year. We have SP1, SP2, and SP3, and then suddenly, it's moved out of support. That's the organization's main pain area. They don't want to keep investing from a storage perspective. The licensing model should be changed.

The product itself is out of support. They have not considered it for AI initiatives.

The new version should be on the cloud. I'm not sure if the new version of Documentum, xECM, is cloud compatible or on which cloud it is compatible, but the OpenText server itself is on a cloud, which would be beneficial to the business. And it would also be easier for migration.

It's been, like, seven to eight years. I use the old version, v7.5.

I have been working in Documentum since version 5.3.

With standard technical support, we don't need any dedicated engineer for our organization. Whenever it's required, the Priority One and Priority Two issues should be addressed within one day. But for Priority Three and Priority Four, we can do it in another five days. 

But for Priority One and Priority Two, where there is a complete loss of service, that needs to be taken care of as a priority.

I would like to move to xECM, which is OpenText Cloud. It's the same Documentum, but this Documentum is quite costly, and lots of organizations are moving away from it. Alfresco as well. A few organizations have adopted Alfresco.

It's an on-premises solution. For me, it's straightforward because I have worked with it for a long time. So I don't have any issue installing it on Windows or iOS. I did a lot of migration from 5.3 to 6, so I have installed more than a hundred databases. For me, it's straightforward, no issue at all.

The integration with other products is easy, that's also not an issue. I integrated it with SAP, Captiva, PTW (an in-house product). The company uses DFC to connect to Documentum.

The licensing model should be changed. It varies from organization to organization, depending on how it is integrated with the business.

Technical support should be included in the standard licensing fees when we purchase the product. Standard support will be included, not premium support.

My recommendation is fifty-fifty. I would suggest OpenText since lots of organizations are moving away from Documentum.

Overall, I would rate it a seven out of ten, for the current version I use.

We have an accounts payable use case, and we also have an HR use case. We store all of our documents for HR and accounts payable. OpenText Documentum helps us organize and keep everything in one place we can trust. With the new versions, people can't share or download them whenever they want to.

OpenText Documentum has tremendously improved our organization by organizing it and keeping people accountable.

The most valuable feature of OpenText Documentum is the versioning.

OpenText Documentum's user interface could be improved a little bit.

I would love to see OpenText Documentum having an out-of-the-box integration with DocuSign.

I have been using OpenText Documentum for 23 years.

OpenText Documentum's stability is awesome.

OpenText Documentum has amazing scalability. It's very flexible, and we can add more licenses whenever we need.

OpenText Documentum's technical support needs to be improved.

Negative

We have seen a return on investment with OpenText Documentum.

OpenText Documentum's pricing is good.

Before choosing OpenText Documentum, we evaluated SharePoint and Box. We chose OpenText Documentum because it had the most features and was the most user-friendly for the security we needed.

OpenText Documentum's security protection is awesome.

We use OpenText Documentum's integration points with the leading business application, Salesforce.

The integration of OpenText Documentum with Salesforce is very important to make sure we have it all in one place, and it's all synced.

It would be nice if the configurability of OpenText Documentum were faster, but it is good overall.

OpenText Documentum has helped boost productivity within our organization. Earlier, we had to track each person down to ensure they had the most recent document, which was time-consuming for HR. The solution has ensured that whatever we have is the most recent version, and that's what we have to worry about.

It has helped boost our productivity by 70%.

OpenText Documentum has helped simplify or accelerate our modernization journey by simplifying everything so that we have one place for everyone to work.

Overall, I rate OpenText Documentum a nine out of ten.

We are a pharmaceutical company. We use it for quality documentation, validation, clinical, regulatory, and lots of different things.

We use the Life Sciences package. We are in 120 different countries with lots of products, and this is what we run our documentation on.

By implementing Documentum, we moved off paper 25 years ago.

We have various APIs connected to our documented environment. It is connected to many other things. I only have a portion of that. This integration is extremely important for us.

We find Documentum adequate in terms of configurability to make the solution available to our users.

Documentum has helped boost our productivity to some extent. We have an international distribution of content and accessibility around the globe. There is 24/7 access.

Documentum has helped simplify and accelerate our modernization journey. We implemented it as a part of Y2K. That is how long we have been running it.

We like Documentum for its capacity and reliability. Documentum is pretty solid in terms of security protection.

We mostly use the Life Sciences package. That package is somewhat dated. There should be enhancements to the Life Science package and additional offerings to support pharma in particular.

I have been using OpenText Documentum since it was acquired. The buyout was in 2018 or something like that, but we have been running Documentum before EMC owned Documentum. It has been 25 years.

We have been using it for generations, and it is fabulous.

For the volume and distribution model, it is quite scalable. Integration with other applications is less than IDR.

OpenText's support has been pretty solid. I cannot always say that about the history of Documentum, but since it moved to OpenText, we have got pretty solid, reliable, and timely upgrades and support. I would rate their support a good solid eight out of ten. There is room for improvement, but they are quite reliable.

Positive

We had a myriad of different things. Most of them have not been on the market for generations. The reason for switching to Documentum was modernization.

By implementing Documentum, we wanted to address the challenges of integration and API connectivity with other applications, optimizations and enhancements for the additional platform, and future plans for the platform. Is it going to be fully incorporated into Extended ECM, or is it going to become something else? We wanted to ensure ongoing long-term support for the product and AI compatibility.

We have done so many upgrades and updates. We have run the full gambit of extremely easy and extremely difficult. We also grow through acquisitions and mergers. When you have to roll over systems and migrate data from other systems, and you have a catalog with 20,000 things or applications, millions of documents, and terabytes of data, you can have everything that you can imagine, from easy to the most complicated.

Our implementation strategy is by project. There is no one broad stroke you can paint it with. Whether it is a clinical, quality, or regulatory migration or an integration or connectivity to another system, it is a unique task.

We have used product services related to Documentum. We use third parties and homegrown internal resources depending on the project.

We have to have something. There is really no choice in our industry. It is highly regulated around the globe, and there are many different regulations to comply with, so we have to have something. Documentum has been our choice for many years.

It falls in line with a lot of things that are out there on the market. There is nothing extraordinary in terms of great or bad.

We evaluate other options as our regular business plan. We do not always assume we are upgrading what we have. As a business process, we always look at what we have versus what is available in the market. The main differences between Documentum and others are the compatibility with other systems and tailored solutions for our industry. Sometimes, it is language compatibility and things of that nature for actual human language, not computer language.

Overall, I would rate Documentum a solid eight out of ten.

We use the solution for storing structured, like XML or JSON.

The search feature has improved our workflow. It was mostly used in data centers and within the data center. It's just user-based role management.

It has the ability to categorize and search.

I have been using OpenText Documentum for 15 years.

It's pretty stable.

It is very scalable. 5000 users are using this solution.

I rate the solution’s scalability a nine out of ten.

I rate the initial setup an eight out of ten, where one is difficult and ten is easy.

It was done through independent consent.

It has a yearly license. 
I rate the product’s pricing an eight out of ten, where one is cheap, and ten is expensive.

I recommended OpenText Documentum to a client I worked with because it's excellent for handling transactional document management. The client had a terabyte of structured or transactional data, and Documentum was well-suited for managing it.

If you're using another product for transactional document management, such as a mortgage application system, and you have a high volume of documents (e.g., a million mortgage applications resulting in ten million documents), you should consider switching to OpenText Documentum instead of relying on systems like SharePoint or other office management tools. Documentum is designed to handle large-scale document management needs more efficiently

It can be somewhat cumbersome for the operations team since it’s not a cloud instance but hosted in a data center. However, when compared to other data center products, the overhead would likely be similar.