OpenText Content Management Reviews

We are partners of OpenText Content Management in the area of content management and in another area of SAP solutions, with OpenText Content Management solution related to SAP platforms.

OpenText Content Management has a feature that is unique in the market, which is the deep integration with leading applications, allowing reflection of the connections between different processes and objects in applications such as SAP, SuccessFactors, or Salesforce, visible inside the document management application. Without connecting to the leading application, for example SAP, you can navigate between all documentation, having a full 360-degree view of all information related to the process. This means that when you create some action regarding an object that has a connected document in the content management system, you can automatically see additional information connected, managed and controlled by the leading application, with automatic reflection in the document management system. This is a unique advantage that OpenText Content Management has, which is not found in the market.

Another unique feature is the integration with Office 365, where you can work with different folders or binders in the document management system and connect to Teams in a simple way, making all this information available in the Teams you are working with.

Digital Asset Management is a big part of the content management solution within OpenText Content Management, allowing full integration of all documentation, pictures, plans, and technical documentation if you have asset management inside SAP. It connects similarly to other modules of SAP but includes a special feature for asset management from a technical point of view and connects with the engineering department, providing the full life cycle from development through deployment to maintenance. This means you have the full life cycle from the beginning when you define the solution, construct it, and finally transfer it to maintenance to keep all information updated easily, avoiding risks and ensuring access to accurate information at the right moment.

There are some areas in OpenText Content Management that could be improved, particularly regarding the way you define and extend the solution with different metadata. Another important aspect is the improvement of the artificial intelligence already embedded in OpenText Content Management solution. While these improvements are part of a general trend affecting all software, the improvements of user interaction with the AI are on OpenText Content Management's roadmap, and they are making enhancements based on user feedback and experience, though initially this feature could be better.

I have experience of working with this solution for more than 20 years.

My experience with technical support from OpenText Content Management rates as a seven. A few years ago, it would have rated as a ten, but there was a shift to a new support platform that led to significant issues. Currently, they are improving support and transitioning to a new solution, which is better than what they implemented in the past three to four years. In prior years, support was really great; opening a ticket resulted in fast responses and proactive problem-solving. After the pandemic, the transition to ServiceNow made it challenging to find information on their support page, but they are currently working on improvements.

Positive

Regarding return on investment, the ROI may be very short if you use OpenText Content Management system effectively, as it provides many features that improve efficiency and reduce the workload of users handling documents.

OpenText Content Management has changed the licensing concept to one license that includes all features. Although this may make the final license price a little higher in the market, considering all the features offered with this license, it's not expensive. If you compare it to an archiving solution and you are using content management only for archiving, the cost of the license may seem too high, as you are paying for a license that not only includes archiving but also controls the full life cycle of information, connects with SAP and Salesforce, features a native connection with Office 365, and supports parallel editing.

This makes the solution unique in the market with full functionality and extensive certification to ensure correct operations. However, comparing the full solution with only one archiving function might lead you to find other solutions that only focus on archiving. The entire functionality of OpenText Content Management, relative to the price, may not be so expensive since there are many features to utilize and extend across many areas and users.

I have experience working with OpenText Content Management. This is part of the Content Management with Extended ECM, and the latest solution released by OpenText Content Management, Core Content, fulfills this feature too with Salesforce and SAP, fully connected with Office 365.

Currently, most of our solutions are typically deployed in an on-premise scenario. However, following market demands, many are moving to the cloud. The challenge with cloud deployment is the hidden costs, often referred to as iceberg costs that lie beneath the surface, such as traffic costs or volume costs, depending on the kind of solution you are using and its purpose. We actively promote the transition of solutions to the cloud for many customers.

I rate OpenText Content Management 9 out of 10.

I use extended ECM for procurement, sales, engineering documents, and sometimes invoices and accounts payable or receivable.

The version controls and the business workspace part integrate well with SAP and OpenText, providing granular level control over who accesses the workspace. The seamless integration between SAP and OpenText offers a 360-degree view of documents, facilitating a full-text search capability.

The cost of the product could be improved. Currently, there are certain snags in document viewing, and communication from the pre-sales team is not clear. The expectation from the customer versus the product explanation needs alignment. OpenText's knowledge website needs better organization.

I have been working with OpenText-based solutions for about 17 years.

I rate stability between eight out of ten. The product is quite stable if it is well-managed.

I rate scalability around six to seven. There is not enough documentation about scaling, which makes it difficult to enhance or modify environments without significant effort.

I rate technical support between three and four. The response time is not effective, and the staff lacks adequate knowledge.

Neutral

The initial setup is quite complex and requires an expert. However, the process is well-documented.

The setup and installation require expertise, indicating the use of professional services.

The cost is a significant factor that may deter medium-sized businesses from using OpenText extended ECM.

Some competitors include Cofax, now called Tungsten, and Microsoft, which is doing a great job with document ingestion, detailing, indexing, and recognition.

I rate OpenText extended ECM between six and seven overall. 

The solution is good yet needs to evolve to keep up with market trends. It is particularly suitable for large enterprises due to its cost and complexity.

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. 

The solution is used for drawing management, EPC transactions, and comprehensive document management.  

The engineering document management system is one of the most valuable features of OpenText Extended ECM. Our company has been using the solution for document management for ten years, and it still functions satisfactorily. Our company also utilizes workflow capabilities along with OpenText Extended ECM for some use cases. 

More out-of-the-box automation features should be added to OpenText Extended ECM. The workflow engine's integration capabilities can be enhanced in the solution. Limited automation capabilities are already present in the tool, and custom development efforts are required before full utilization. 

I have been using OpenText Extended ECM for ten years. 

The solution has been used in our organization for over a decade, and we have never witnessed OpenText Extended ECM go down in functionality. 

The solution provides impressive scalability. There are two kinds of architecture supported by OpenText Extended ECM: horizontal and vertical scaling. OpenText Extended ECM can support applications even with a 20,000-user base. In our organization, we have scaled the solution to more than a couple of servers as per the performance and compliance requirements. There are about 1,000 solution users in our organization, and almost every employee uses it. 

The maintenance support offered for the solution should be improved. I would rate the tech support a seven out of ten. There was a platform change in OpenText Extended ECM, but the vendor hasn't done a great job of migrating the content, so technical professionals cannot solve certain issues by themselves by browsing the vendor's website or data. 

Neutral

Before adopting OpenText Extended ECM, we used SharePoint to some extent in our organization. I have also used Microsoft 365 personally, but not in my company. If you need to manage a large volume of data, then OpenText Extended ECM can be the ideal solution, while Microsoft products can serve small departmental use cases in your company.  

Our company has implemented a few customized application integrations in-house with OpenText Extended ECM, but we haven't tried any large integrations with high-end vendors. The product's maintenance depends on the number of user capacity licenses. Due to its complexities, Deploying OpenText Extended ECM for engineering use cases can be highly time-consuming.

For engineering use cases, sketches of each file of GB size can be stored and managed by OpenText Extended ECM. The solution is being used mainly in our organization for applications built in Texas, but I have personally carried out OpenText Extended ECM deployments in the US for one of the customers. The applications' network and WAN are hosted internally in our organization. 

The solution was implemented in-house. 

OpenText Extended ECM is worth the cost and is able to provide a satisfying ROI because of the consistent support it provides to enterprise applications and infrastructure. At our company, we always exceed our SLAs and don't have any performance issues in OpenText Extended ECM. 

The total cost of the product will vary on the capabilities required, including recording and reporting capabilities. 

Our organization has the flexibility to use any kind of database as OpenText Extended ECM supports multiple database partners. At our company, we utilize Microsoft SQL along with OpenText Extended ECM. The solution offers immense flexibility and integration possibilities, at our company we previously integrated SharePoint with OpenText Extended ECM. 

The record management feature of the solution has helped my organization enhance the compliance or regulatory processes. This full-blown feature integrates easily with OpenText Document Management System, and this combination can be used to manage the lifecycle of the records or documents. 

The major use of the solution has been to organize documents, previously scattered everywhere, some employees saved them on the desktop, some on local drives and IT solutions, which often led to discrepancies in our organization. Our company was looking for a single application to manage all documents and then we adopted OpenText Extended ECM. Our company is working on a plant and thus also needs to organize all engineering sketches at a single source. 

I would recommend OpenText Extended ECM to other users, depending on their budget. I would rate the solution a nine out of ten overall. 

The biggest use case in our company, which I help support, is that our accounting department uses it to help compile and do all the tax returns that we use. We are a private company. We work for a wealthy Chicago family, and the accounting department handles thousands of tax returns that they do every year. We use the OpenText Capture product to bring in all the forms and documents and get them into the Content Server. We have built a workflow and reports around that process, which includes getting the documents, compiling the tax returns, having them go through multiple reviews, and then eventually filing them with the IRS.

By implementing this solution, the biggest challenge that we were trying to overcome was to give our accounting department a little bit more visibility into that workflow. Prior to this, they were literally doing everything on paper by hand. We wanted to automate the workflow and have a way to store those documents on a long term. We wanted them to be able to work from home without taking a stack of papers home with them. All these things were the big gains from moving over to it.

They handle thousands of tax returns a year. They are usually in the range of 3,000 to 5,000 every year. It was always a slog and a lot of work to get all that done on time and racing against the October 15th deadline. By giving them visibility in that process, they are now able to run some analytics and organize things better year to year. They can figure out when to do certain things in terms of timing, how things go in a sequential order, and what needs to be done before what. They have been able to do that a lot more easily. There is a lot less tracking of everything on a spreadsheet. They are able to see the data. That has been extremely helpful for them.

I have some personal success stories of some older people who have now retired. Seven or eight years ago when we first did this, they would say, "Why are we doing this? Our way works just fine. It is no big deal." We implemented it, and a year later, we went back and talked to them, and they said, "We actually know what everything is. It is amazing." That was nice. We want people over.

It allows them to collaborate more easily. The content silo here was that an accountant had the papers on their desk, so only they could work on them and look at them, whereas now, anybody can. Anybody who is in the approval process does not need to pick up papers and put them on somebody else's desk. There is a notification that says that somebody needs to go check this out. 

Extended ECM has helped connect our content to our business processes. There is more flexibility. People only have to take their laptops home to do work now. This is something that we have been talking about for a decade but it was something that we were behind on. I am so glad that we already had this in place when COVID hit because otherwise, it would have been a disaster. Because it was in place, it was a pretty seamless transition. 

Extended ECM has helped to increase productivity in our organization, but being on the IT side of things, I do not have the statistics that the account team might have. They are the ones who know how quickly things got done beforehand versus now. I only have a once-a-year meeting with them to discuss what we are improving on for the next year. 

We also have a module on top of the Content Server called WebReports that has been one of the things that helped us facilitate the workflow and give managers good reporting and visibility into where everything is. Being able to use that on top of the Content Server was a big help.

We make iterations on it. Every year, they usually ask for some small things. Overall, they are pretty happy with it. Being the IT person here, I do think there are areas for improvement, but both for us and them, it is 80% to 90% good enough. It might take a big overhaul to get to that next step of being able to do even more. They are fairly happy with it right now, so I do not see that coming immediately down the pipeline. It is like the juice or the squeeze on some of those things, but there is definitely some room for improvement. We have learned more since we implemented this, so there are things we could do for sure. Overall, they seem to be pretty happy with the process.

When it comes to addressing complex use cases, three or four years ago, we ended up purchasing an additional OpenText product called AppWorks because we started to run into some limitations with the workflow that can be done in Extended ECM. It was a little limiting, so we ended up getting another product. They integrate together, but in some of the more complex scenarios, we have started to shift and start building things in AppWorks. Documents are still stored in the Content Server. It is almost like an additional layer that helps us do a little bit more. So, Extended ECM Content Server does a very good job for a lot of use cases, but if you do need to do something that is a little bit more complex, you might need other tools.

I have been using their Content Server in our business for about a decade.

I have had both very good and very bad experiences with it. It sometimes depends on the product. I have sometimes struggled with support and getting answers in a timely fashion. I am also not a huge fan of the change in platforms. I am getting used to it a little bit, but it still leaves something to be desired from the old support platform. 

Overall, I would rate their support a five out of ten. Specifically for AppWorks, I would rate them one or two. I have had a tough time with support with that one. The support for the Content Server and other things around that has generally been much better, and I would rate them a seven out of ten. 

Neutral

Our only document management solution has been the Content Server.

It was fairly complex because we ended up using a couple of different modules to help us out. We built the workflow and a lot of custom reports. It was definitely some work to get them up and running and to get there, but I would not necessarily call it a con because it would be naive to ever think that you can just flap something down and have it work great for anybody. There is going to be some configuration, and there is going to be some tailoring to make it work for not just your organization but also the individual department. There was a decent amount of work to get it there and to get it to work well for them.

We even did a couple of different stages. We started off using something a little bit more basic to help them manage their process, which we eventually upgraded to a full-fledged workflow. We did it in stages because it was just too much to undertake all at once. They are busy from February until April, so we have this small window to roll things out and implement new changes. We stepped up over two or three years. In year one, we just cared about getting their documents digital in there and giving them some minimal tools to track the process. We refined that. In year two or three, we made that an actual workflow, so it did take a couple of years to get there. It was not simple, but we did it. You need to build that roadmap or that plan and keep iterating it.

We try, but we do not do a super great job of measuring the ROI in IT at this point. The accounting team would have a better understanding of the ROI.

I was not involved in that specifically, but there were a number of other options we looked at. Laserfiche was one of them. There were one or two bigger names in the field. Documentum might have been one of them. It was a separate company at that time.

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 we too are a Microsoft shop, but there are a lot of things that are limited. Years ago, we tried to do some of the things years with SharePoint and fell flat. It just did not have enough features. It could not do all the things. Now with Teams as the front end, it is a little bit better in terms of usability, but you do not get the same capabilities, options, and extensibility that you get with OpenText products. In general, you will have to work a lot harder to do the same things, and then you are going to have gaps in terms of certain things that you cannot do.

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

We use it as a single source of support for the company. We store all official confidential documents in OpenText as the final record, keeping with records retention policies.

The challenge that the company was looking to address by implementing OpenText was governance. 

In any organization, if you implement governance, some people follow, and some people are not aware of it. We have to educate and enforce compliance purposes. 

When I started, very few people were using it. Now, I'm doing demos and marketing within the team to encourage everyone to use it for compliance. We have around five million documents and things stored in ECM now.

When it comes to integrations, we are discussing external DCM with Office 365. We are still in the discussion stage, but some Salesforce teams are using OpenText API for Connections.

Since rest API is available for integration capabilities, it's easy for their applications to build their own and integrate. OpenText also gives connectors. It's a little pricey, but it's good that the users have options available. They don't have to build anything.

Moreover, OpenText has helped increase productivity in our organization. It helps full-text indexing search, so when employees upload a document, they can easily find it again later, even if they don't know the metadata. 

Smart Viewing videos are most valuable for the end users. The end users like the look and feel of Smart View. It's similar to SharePoint, with the latest HTML5 features, filters, and everything. It's like online shopping.

OpenText Extended ECM helped connect our content to our business. Employees don't have to switch between applications to find the content they need. 

For example, if they have adapted to their front-end applications, and they don't want to change it, they can still store the content in OpenText. They can access it all from within the application they're already using, such as SAP or Microsoft Office.

We can store everything in OpenText Content Server, and we can access it from the other app again.

There is room for improvement in records management. ECM should be a single place to keep all the documents so people can easily search and access them.

We have been using OpenText Extended ECM for four years.

Stability is good but I would like OpenText to improve the alerting system. 

We had some issues with scalability in the production. I would rate it a five out of ten. 

The customer service and support seem to be good. 

There are some delays with response and escalation.

Neutral

People in my company used different solutions to cover different divisions. For example, some people used NetworkDrive, and others used SharePoint. After I joined, I decided to consolidate enterprise-wide applications and I also educated people about the product.

I would recommend OpenText because it has more features than Microsoft's native content management solution.

We used to grab on-prem, but we migrated to OpenText managed services, so they do all the installation and patching.

Whenever the new release comes, I'll create a ticket and ask to upgrade and test the new features. I'm not directly involved in the upgrade.

We saw a return on investment. 

It is costly. It's costly to integrate with Office 365 and to go back and forth with the sales team. 

When I presented the numbers to my leadership, they were shocked by the price. It's very expensive to implement until we have a strong governance, and then the price point implementation; there is no point in spending that much money for.

We evaluated SharePoint and OpenText.

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

I've worked at three or four different companies that have all used some version of OpenText Extended ECM for document management purposes.

Through the years, we've used the solution to manage massive amounts of data and ensure that the employees get what they need in a timely manner.

We help other clients to upgrade or migrate, and we wouldn't be in business without OpenText Extended ECM.

The permissions and security model of OpenText Extended ECM have been really good features. The ability to add metadata and use that to categorize information is a valuable feature of OpenText Extended ECM.

OpenText Extended ECM's user interface could be improved.

I have been using OpenText Extended ECM for 23 years.

OpenText Extended ECM has been in the marketplace for a long time and is pretty stable.

OpenText Extended ECM's scalability is quite good.

OpenText Extended ECM's technical support is pretty good most of the time. The hardest part with the support is finding the right resource to answer a specific question.

Positive

OpenText Extended ECM's setup is complex in terms of the integration side and how long it takes to perform an upgrade.

We have seen a return on investment with OpenText Extended ECM.

OpenText Extended ECM's pricing and licensing are aggressive and confusing for the end customer.

Before choosing OpenText Extended ECM, we evaluated SharePoint and Documentum.

If done right, the integration of OpenText Extended ECM with applications like Microsoft 365 or Salesforce helps eliminate content silos in our organization. The elimination of content silos has made our operations smoother and more efficient.

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

OpenText Extended ECM has helped connect our content to our business processes. This connection between our content and business processes makes things more efficient and removes barriers.

OpenText Extended ECM has helped increase our organization's productivity by about 25%.

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

Our company is an engineering company that creates documents for engineering projects. We use OpenText Extended ECM for the engineering model on top of the content server. We use OpenText Extended ECM to define the entire lifecycle of the document from creation to sending to the vendor and receiving the updated version from the vendor.

We have users all over the world. If someone wants to see the status of a document, they can run the report and get the latest information. They don't need to wait for anything since it is easily searchable from the system.

The automatic document numbering, state management, and process flow are very useful features to go through the full cycle of the document.

The performance, stability, and consistency could be improved. The solution works well when the load is low. We have around 6,000 to 7,000 users using the system, and we see some performance issues during peak times.

I have been using OpenText Extended ECM for four to five years.

I rate OpenText Extended ECM a six to seven out of ten for stability.

OpenText Extended ECM is a scalable solution.

The solution's technical support team lacks the expertise to resolve the issues, and their response time is not fast enough.

Neutral

We previously used a tool from Siemens.

The solution’s initial setup is a little complex.

OpenText Extended ECM is an expensive solution.

We have integrated the solution with SAP, and users can access the document from SAP and OpenText Extended ECM. It simplifies our business because users can get into the document from multiple channels, making life easy. They don't have to search from the different systems because it unifies the integrated system.

Right now, OpenText Extended ECM provides integration with multiple systems, like Salesforce, Microsoft, and SAP. Earlier, users had to log on to multiple systems and look for something, but now they can access everything from one place.

OpenText Extended ECM has helped connect our content to our business processes. That is the advantage of using OpenText Extended ECM for SAP. They can see the business process metadata as attributes at the document level. An OpenText user can see the same information on OpenText, and an SAP user can see the document on the SAP side. They can access the document from multiple channels. This simplifies the process and makes everybody's life easier.

OpenText Extended ECM has definitely helped to increase productivity in our organization.

The integration capability with OpenText Extended ECM has a big range. You can integrate the solution with different products, which makes it robust.

Overall, I rate OpenText Extended ECM a seven 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.