OpenText Extended ECM Reviews

My main use of this content server is to help end-users manage their documents without accessing SAP. 

We keep SAP data confidential, and whatever data is required for end-users, we make it available in a content server so end users can directly access the OpenText server to access their data and perform operations.

There are many features. One is the security, then the permissions management is really good, and the workspace, folder structure, and classification categories. The classification categories are mainly helpful for searching data, and the workspace is for managing projects. Permission management is really important for the end user.

The collaboration tool is another good feature. Many users on the team can work together on the same platform and the same document to collaborate.

It improved our team's productivity.

There are some workflows which need to be more user-friendly. We need to improve here on the specific map of the developers. Also, the support from OpenText is really difficult. Honestly, I had a very bad experience on this. It's really difficult to reach out to OpenText. Even for small things, OpenText is not transparent. As a professional, I don't think that's the right way. This is also one of the disadvantages; many customers are moving out of OpenText. 

I saw multiple instances when I was working with new RFPs or new opportunities. So many customers are raising the same concern, and they are looking for alternate products. That's been the case many times at the project level.

With OpenText, we ourselves often have to resolve the issue before OpenText people provide a solution.

It's been ten years.

There were a couple of issues that we resolved with the help of the support center.

But, it is really difficult to reach out to the support. it takes too long to get the solution.

Negative

I have very good experience with Microsoft SharePoint, which I was certified in. Very good experience on the SharePoint content management tool. 

 SharePoint and OpenText are both similar in terms of being tools to manage content. But OpenText has some advantages. We can integrate seamlessly with any third-party tool, and we can manage unlimited data and upload huge documents. 

In terms of features and functionality, as well as user-friendliness, OpenText is really good. Nowadays, however, SharePoint has come up with new features and improved functionality. Still, OpenText provides some complex features and functionality that are some of the best.

OpenText is always higher in the pricing. So, many customers look for alternate solutions. They are bringing their solutions to SharePoint as well. I saw a few customers who move to SharePoint because it's less expensive, has lower maintenance, and we get product support from Microsoft. SharePoint has some advantages.

The pricing is more than 30% to 40% higher for OpenText compared to SharePoint.

Microsoft SharePoint is a kind of package. If we start using Microsoft products, we'll obviously get some kind of discount. But OpenText is an individual product; until we specifically use that, there is no alternate price. 

Microsoft provides infrastructure, Office products, and other products, so we'll get some more discounts when we use SharePoint. But OpenText is not like that. OpenText is there. Specific to the business case, we need to go and get it. That's why the price is higher.

OpenText itself is a too expensive tool. But why the reason customers opt for is OpenText is one of the best and provides very good complex data with their managers.

Overall, I would rate it a nine out of ten. 

We use it for document storage. We also use it for reporting purposes, but mainly, it is for document storage.

The challenge that we were trying to address by implementing Extended ECM was the performance issue in terms of the time taken to pull up a document. We are still searching for a good tool to be able to do annotation. We currently use Brava, and our end users are not very happy with the experience with this tool. We would also like to learn more about the tool so that we do not have to do a lot of customization. Currently, some of the implementations that we work on require some customization, and they are hard to maintain as we do our upgrades.

We are jumping from an old tool to this new one, so we have not been able to optimize it yet because we are still not 100% familiar with it. We would like to improve the business processes for the users. I am looking into how to easily integrate this OpenText tool with any other existing application that we have, such as PeopleSoft or Oracle Cloud, to be able to easily look up a document within any existing application. The integration piece is what we need to improve. That probably is something that has been one of the selling points or one of the items that we were not able to do in our old tool. With OpenText, we are using integrations, and that is the main improvement that I see so far. It is just a matter of how to further improve them.

Extended ECM has helped to connect our content to our business processes. People rely on the tool a lot. They upload documents almost on a daily basis. It has had a good impact. We want people to be able to log in to the system and easily pull up a document and compare the data to another application. It has definitely impacted them on a daily basis.

Extended ECM has helped to maintain productivity in our organization.

Being able to search is valuable. Its search is pretty powerful. We are able to search for specific text, and it points us to the document that has that text. That is pretty powerful.

The annotation tool needs improvement. In other tools, such as Hyland OnBase, you can easily do annotation. You can easily merge documents. You can easily compare documents, whereas with OpenText, it seems to be a challenge. You need an additional tool to do that. I am not quite sure why that has to be an additional feature because, with the old tool that we use, OnBase is already delivered. That is a very old version of the tool. It seems like OpenText is still trying to explore.

We still do not know enough about this tool. We are still trying to learn or figure out where we can find the information. It would be great if there were easy-to-follow user guides or videos that tell us the top 10 or 20 features that we should know about OpenText. It would be helpful to know how to do something from a development perspective rather than from a user's perspective. It would be helpful to know how to easily develop a report or a workflow. It will help people to do all the configuration and use the tool.

I have been using Extended ECM for five years.

It depends on the users and their vision and how much they want to invest in a product. They can then go from there. The product itself is good. They have good direction, but it is just a matter of whether the customers or end users can follow that direction. Each office or institution has its own challenges.

My colleagues can answer this better, but it depends on how you ask the question and whether you get the right person to assist you who knows that area. The first couple of times, the experience was different because they did not quite understand the question or that area, but over the years, we understand the structure a little bit better. It is a matter of asking the right question and then finding the right person who can help us. There are some challenges here and there, and overall, I would rate their support a seven out of ten.

Neutral

We were using another tool, but there were not many options to integrate. There was no out-of-the-box solution. We had to do customization to do the integrations. It was a fairly old tool, whereas OpenText is more modern.

Its initial setup was complex. Each implementation is different, but the most important thing is to gather the right stakeholders from the beginning of the project. Make sure that you are asking the right questions to collect business requirements correctly, and then you have to control the scope. To be able to complete the project, you have to control the scope of the project.

It is good. In general, people are heavily using it. They rely heavily on integrations. It is not just pulling up a document and looking at it. They are looking at the data within another system and then comparing it. They no longer use the tool just for storage. They kind of multitask in two different systems at the same time. They are looking at the document, and they are also looking at the data within another application.

Overall, I would rate Extended ECM a seven out of ten.

We use the archive as our official repository for all of our finalized documents.

By implementing Extended ECM, we wanted to have a central location for all finalized documents so that everyone knows where to go and look for them. We also wanted to have retention around documents.

It is keeping us organized. It is putting retention around documents. It provides a centralized location for our documents.

Extended ECM has absolutely helped connect our content to our business processes. It has been very beneficial for employees' experience. Everyone knows where to find the information that they are looking for. They are not searching through different S drives, network locations, or random numbers.

Extended ECM has absolutely helped to increase productivity in our organization. There is about 50% improvement.

The integration of Extended ECM with applications has not yet helped eliminate content silos in our organization. If we did make those bridges, I could see how that would help. I am hopeful we can bring that recommendation to the company.

Being able to tag metadata on documents and being able to have different workspaces in there for our documents is valuable. We do loan documents, and different types of documents have different types of retentions. We are able to categorize based on that, and we are able to do tag searching to find what we are looking for. There are a lot of good features.

It is easy. The usability is there. It is easy to navigate through.

A dashboard with information would be nice to see.

I have been using OpenText Extended ECM for three years. It probably was not called Extended ECM then.

It is stable.

It is scalable.

I have not contacted their technical support. We use managed services. It is not on-prem for us. It is managed. I contact our support, and they contact OpenText's support.

We were using FileNet, but I was not personally there at the time. I came to the company later. I do not know all the details about it, but they switched because FileNet just was not meeting business needs. 

I am not involved in the setup piece. I am the bridge between IT and business users.

To a colleague at another company who says they do not need Extended ECM because they are invested in Microsoft solutions, I would just encourage them to look at different retention pieces and have the ability to have protection on the documents. I do not know what goes into that on different platforms, but that is a key piece for us at least, so taking a look at it would be good.

Overall, I would rate Extended ECM an eight out of ten. It has a lot of great features for our business needs.

We use OpenText Extended ECM for our document management purposes. 

We help clients to upgrade and migrate. Without the product, we wouldn't be in business. 

OpenText Extended ECM's most valuable features include permissions and security models. I also like the tool's ability to add metadata and use it to categorize information. 

The solution needs to improve the user interface. 

I have been using the solution for 23 years. 

OpenText Extended ECM is stable. 

The solution's support is good most of the time. The hardest part is finding the right resource to answer the question. 

Positive

The product's deployment is complex because of the integration and the time to complete an upgrade. Our implementation strategy focused on minimizing the impact on the end customer. 

We have seen ROI with the tool's use. 

The tool's pricing is confusing to the end customer. 

I have evaluated Microsoft SharePoint before choosing OpenText Extended ECM. 

Over the years, we have been trying to manage massive data amounts and ensure that employees get what they seek. 

The tool's integration capabilities with Microsoft and Salesforce help eliminate content silos if done correctly. It has made our operations smoother and more efficient. 

The solution has helped us connect the content to our business processes. It helps to take away barriers. 

The product increased productivity in our organization by 25 percent. 

Any company refusing to integrate OpenText Extended ECM for Microsoft products will change its mind in two years. 

I rate the product a seven out of ten. 

We build products that add value on the OpenText Extended ECM.

Our products run on OpenText software.

OpenText Extended ECM's most valuable features are document storage, security, and compliance.

The solution should work better with partners and be more developer-friendly.

I have been using the solution for 20 years.

OpenText Extended ECM is pretty stable. I rate it an eight out of ten.

I rate the tool's on-premise scalability a six and cloud scalability a nine.

For support, when we open a ticket, we get assigned logs. We need to wait a week or two for a response.

Neutral

The solution's deployment is straightforward. Our implementation strategy involved the deployment of SAP systems with the product.

The tool offers value for money.

The solution is expensive.

The tool's integration with Microsoft and Salesforce has eliminated content silos in our organization.

OpenText Extended ECM makes things simple for business users.

The tool has helped our customers connect business processes.

OpenText Extended ECM has boosted productivity by 75 percent.

Anyone who says they don't need the product should give it a try and understand its value-adding capabilities.

I rate the product an eight out of ten.

We use OpenText Extended ECM to build a connector to view documents on ServiceNow. It also helps to create a custom search for archived documents. 

OpenText Extended ECM has improved our exposure since our product is available in the market. It helps us get more business. 

We can configure the solution with any industry's products per customer requirements. 

The tool's documentation is not proper and has missing information like steps. 

I have been using OpenText Extended ECM for three years. 

OpenText Extended ECM's stability is good. It keeps improving with newer versions. 

The solution is scalable. 

We contact the support to resolve documentation challenges. The tool's support is good. 

Positive

A few things are complex in the tool's deployment due to the missing information in the documentation. We first build a development environment on our on-premise server for our implementation strategy. We test it out and report to the support if we find any bugs. 

We can address a lot of problems using OpenText Extended ECM. You can build different connectors to the configuration. 

The product has helped us boost productivity by 30-40 percent. 

Microsoft doesn't have as many features as OpenText Extended ECM. You get more features in the solution compared to any other product. 

I rate it an eight out of ten. 

We use it to manage our engineering documents. We use it for the drawings and our asset documents.

The challenge that we have is that some users are reluctant to use the system, so we still need to come up with a way to motivate company-wide acceptance.

The search capability is great, and it is far better than File Explorer, which is what we had before. That was a network drive. When it is indexed and it is OCR, it is easy to find things.

We are working to integrate with SAP completely, and we are hoping that would help to eliminate content silos in our organization.

The range of Extended ECM's integrated capabilities for addressing complex use cases is pretty good.

Extended ECM has helped connect our content to our business processes. People are able to find what they are looking for quickly.

Extended ECM has helped to increase productivity in our organization.

We use Core Share to share documents with external auditors or with vendors, and that prevents them from being able to get into the whole system. It is useful.

In terms of features, problems are mostly internal. We are still struggling with fixing our taxonomy and how we want our browsing to work. That is what we struggle with the most. There are no additional features that I would like to see. I am pretty happy with it, but their support could be a bit better.

We have been using OpenText Extended ECM for about six years.

We do go down sometimes. I would rate it an eight out of ten in terms of stability.

Its scalability is good.

Sometimes it takes a while, but things do get resolved. I would rate them a seven out of ten.

Neutral

We were not using any other solution previously. We were using network shares.

It was complex in terms of understanding the users and their processes at that moment. We are doing interviews and trying to understand why that even was the way it was. That part is always complex. We are now going to translate them.

In terms of implementation strategy, we have multiple sites in our organization, and one site at a time was rolled out.

We have seen an ROI.

I was not involved in the decision-making process, but other solutions were evaluated.

To a colleague at another company who says they do not need Extended ECM because they are invested in Microsoft solutions, I would say that they just have to look at each product and see what would help them the most.

Overall, I would rate Extended ECM an eight out of ten.

We verify complex solutions and we implement it on the business process management system. 

ECM has extra value for us. We focus on both solutions and they are a little different. 

One is only ECM and the second is as a VPN, with ECM as well.

It's a very good solution.

Pricing could be improved and the stability or the performance needs improvement, which is very important.

I was using this solution for a year as a developer and for more than three years as a user.

It's stable, although it could be better.

Open Text ECM is scalable. We have over 200 users, but the organization is now bigger.

We use a component to connect ECM to IBM file share by other systems. I am not sure how many users we have who are using it but it may be over 1,000.

The technical support was okay. 

We haven't had many issues and everything was resolved through our service agreement.

When I was an architect, on one of our organizations we used IBM Finance in one part of our business. We decided that it was a good solution.

For OpenText, it was a decision which related to using a business process managed system as well.

I was not a part of the initial setup. We have a team in place that handles the setup and deployment.

Both OpenText ECM and IBM FileNet share are expensive.

From my perspective, we are working with two solutions. For both IBM FileNet and OpenText ECM, I was the accountant manager and a place where you can store electronic documentation. 

The extra value for both solutions is adding workflow managers, similar to business process management systems. You can verify flows and sign off documents.

I am not sure if I will continue to use this solution in the future. It depends on the business requirements.

If somebody were to ask me which product is better, I think that both are okay and they should verify the business needs then decide which model of pricing or which performance is better for the company.

I would recommend this solution, and if I am considering an enterprise solution, both Open Text ECM and IBM are the same, it depends on what the customer's needs are.

I would rate Open Text ECM a nine out of ten.