OpenText Documentum vs. Salesforce Experience Cloud

What are the document volume, the throughput - currently and expected in year, 3 years etc.? Is the company doing content management on international level, where access from multiple locations is needed - then Documentum can be good investment. What ECM system will be used for - document storage, document lifecycle or retention? Or all of the above? - Documentum works very well if all 3 items are combined, yet for storage there must be cheaper and more easily adaptable solutions available.

HR and Employee Self-Service Portals: Organizations using Salesforce Experience Cloud can leverage Salesforce CMS to create centralized knowledge hubs for HR policies, onboarding resources, and internal communications. Employees can access up-to-date content without IT involvement, improving efficiency and reducing HR’s administrative burden. Multi-Channel Content Distribution: Businesses needing to push content across different touchpoints (web, mobile, email, and customer portals) benefit from Salesforce CMS’s ability to deliver consistent messaging seamlessly. A sales enablement team can publish case studies and product updates on a customer portal while simultaneously integrating content into marketing emails. Personalized & Dynamic Content: Companies using Salesforce CRM can leverage Salesforce CMS to deliver AI-driven, tailored content based on user behavior, preferences, or past interactions. For example, a recruiting team can show custom job recommendations based on a candidate’s past applications.

Incentivized

• It's good at integration with external systems through standard industry supported APIs, including but not limited to web services integration and file system integration.
• Good support from major up and downstream technologies such as image capturing and back end ERP, Database, and HR.
• Highly configurable.
• Very fast searching capabilities.
• Highly scalable.

Incentivized

• Easy to use, just like Salesforce's other products. Many users can sit down and figure it out in no time, and with a little training become power users.
• Fast and secure - Salesforce is a leader in the cloud world so you get consistently fast results and security that is top notch in the industry.
• Accessible from anywhere - if you use cloud CMS already this is a no-brainer, but for those that do in-house CMS still, this is a major difference. Mobile access from anywhere on the planet without a VPN is something you just can't do without the cloud.

Incentivized

• Expense. If Documentum costs less it would penetrate more markets. This is often the reason a lighter weight solution is chosen.
• Web Publishing. Documentum is not a great solution for replacing CMSs like SiteCore or Drupal. Probably better as an archiving target for parallel publishing to both web and Documentum. Documentum is also not a web hosting solution like some other systems, it is possible to try and consume directly from the repository in real time but it is better to push web content out and consume from another platform.
• Development. The price of broad functionality is complexity. Arguably, Documentum drank the kool-aid and tried to become like other enterprise solutions by adapting Java, Windows, etc. in the late '90s and it made them slower, more complex in design, and less stable. They recovered from that but it still requires developers with a few years of experience in Documentum to safely develop in Documentum. The issue is not knowing Java but knowing what to do or not do in an ECM system. This is even more important in regulated ECM/RM systems.

Incentivized

• The documentation for implementing Experience Cloud can be a bit confusing as their rebranding hasn't made it's way into all articles, resulting in different terminology being used to refer to the same thing
• Some things are not as intuitive regarding their customizability, so there's a bit of a learning curve (i.e. Lightning apps can't be used to customize layouts in Experience Cloud)

Incentivized

Stability is a key factor as well as its flexibility. Also, any organization that deploys Documentum will have made a significant investment in terms of time and money, so not renewing its commitment can come with a significant cost. That said, the decision to deploy Documentum initially should come only after extensive evaluation, knowing that once deployed it will likely remain the platform of choice.

Incentivized

Renewal exercise is already underway. Platform is to ubiquitous to not leverage, especially at a Fortune 50 firm

Incentivized

It's very easy to train users on this, even external facing customers. Our users were already familiar with Salesforce user interface since we use the platform for other reasons. We built custom Visualforce pages with a simple, clean layout so we didn't need to train customers. That's ultimately the goal for external facing stuff, that we don't need to train them; they just "get it."

Incentivized

Again, since we provide and recommend solutions, I can't speak to every client's individual experience, but can offer general reflections as to keep their collaborations private, that they are satisfied with the experience. We hear a lot about how this system helps to encourage collaborations between their own business partners, customers, and internal members, and enables quality integrations with other products that help drive revenue.

Incentivized

Support is better than with ECM, but could use some improvement.

Incentivized

Although support from Salesforce itself can be quite unresponsive sometimes, the community hub is incredibly helpful. The large user base of Salesforce products contribute to troubleshooting and the forums are a powerful tool for finding solutions and possible bugs and response times can be quite fast compared to your regular support channels.

Incentivized

Subjective but here's how I see it: Heavy duty (in order of how much they can do and how much they can handle): 1)Documentum, 2)FileNet 3)OpenText Middle duty: 1)WCC-WebCenter Content, 2)Alfresco, 3)M-Files (3rd b/c it is Windows only), 4)Nuxeo (only b/c of its newish approach that may lead somewhere) Light duty: 1) BOX (not an ECM but it says it is), 2) EFSS (pick your poison, BOX is an enhanced EFSS), 3) CMSs (some have some ECM capability, none have much)

Incentivized

Yeah, so we've utilized a few different evaluations of products. Most of them are website or WordPress base, intranet, hidden backend applications. It's just because all the data we have already and we have multiple experience clouds, it allows us to leverage SSO or single sign-on approach across of our experience cloud. So it's less because all one platform, it's less complex for the end user and less confusing.

Incentivized

• After this product, the client is able to manage content security and due to it, the client is able to use the business process, and this really reduces effort and increases the profit in business.
• It provides integration with SAP easily which really helps the client to manage this effectively and with minimum effort system is ready to use.
• Also searching, automated flows also create a bigger impact and reduce a lot manual effort.

Incentivized

• Before using Salesforce, different teams managed content separately, leading to duplication and inconsistencies.
• Using Salesforce within Experience Cloud, we have improved our customer service portal, reducing ticket volume.
• Our sales team can access and share content directly from Salesforce without searching external folders.

Incentivized