What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.