OpenText Digital Asset Management

Name: OpenText Digital Asset Management
Brand: OpenText
Rating: 2.9 (66 reviews)

Leader

Information Reimagined

Est 1991|Valuation $6.1B|Raised $14.3B

LinkedIn 550K|Website|Web traffic 1.1M|FTEs 19,900|HQ Waterloo, Ontario, CA

MarketsCompliance & HR Document Management Digital Asset Management (DAM)

OpenText Digital Asset Management screenshot

Published Oct 15, 2026

01Common complaints

- Fast, low-effort rollout is a primary requirement and there is no capacity or budget for implementation services and administration. - Modern, consumer-like UX for casual users is the highest priority and governance depth is less important. - The procurement process requires many third-party peer reviews for stakeholder validation and public review volume is inadequate for that purpose. - Requirement for simple SaaS packaging and transparent costs without negotiation. - Concerns about vendor-level organizational stability: recent restructuring and leadership changes at the company level may be considered as a factor; product investment commitments should be confirmed during diligence.

Deal disqualifiers (poor fit)

Small teams seeking self-serve onboarding, transparent pricing, and minimal administrative overhead
Organizations primarily needing a simple brand portal and fast adoption by casual users
Teams without budget for professional services or system integrators

Known limitations (from available public evidence)

Usability concerns: some reviewer excerpts indicate the UI could be more user-friendly.
Review visibility limitation: limited review counts on some major platforms reduce the ability to benchmark sentiment.
Ambiguity in naming/packaging: variation in product naming (Digital Asset Management vs Media Management CE) can complicate feature mapping and RFP language.

Roadmap / “what’s new” signals

OpenText publishes release notes and product updates for Digital Asset Management / Media Management (for example: May 2025: release notes), indicating ongoing product releases. Specific roadmap details and prioritization should be confirmed with the vendor during procurement.

Why customers might leave or not purchase (inferred)

Usability or user experience concerns
Implementation complexity and reliance on professional services
Preference for DAMs with more modern UX or different product focus
Vendor-level organizational changes affecting perceived continuity or roadmap

02Why they buy

Unique selling points supported by evidence (not just marketing)

- Deployment flexibility: analyst materials reference support for on-prem, managed hosted, and dedicated SaaS deployments. - Fit for complex/regulatory environments: analyst commentary notes capabilities for regulated environments, legacy integrations, and complex use cases. - Integration ecosystem: documentation and product descriptions reference connectors for Adobe Creative Cloud, Adobe Experience Manager, Salesforce, SAP integrations, and other enterprise systems.

Claims that require validation

Vendor claim of “1B+ assets managed” lacks a public methodology or definition; the claim should be treated as a high-level scale indicator and validated during procurement.

03Field reports

Review-platform availability and volume (practical reality)

G2: OpenText DAM’s G2 page indicates insufficient reviews to provide robust buying insight.
Capterra: Capterra shows a high rating with a very small sample size, which limits statistical confidence.
SoftwareReviews (Info-Tech): lists a modest composite score with a modest review sample for an enterprise platform.
Gartner Peer Insights: OpenText has a vendor presence in the DAM market category; access to detailed quotes may be gated.

Examples of vendor-provided testimonial (case example)

“The OpenText DAM integration into Adobe® Premiere® was a game changer. The platform’s search capabilities and seamless tools made it a no-brainer for our team.” — Dustin Lamendola, Director, Creative and Entertainment, San Jose Sharks (appears on OpenText product page).

Note: this is a vendor-published excerpt and should be treated as a customer testimonial rather than independently verified ROI.

Peer-sourced commentary (limited excerpts)

PeerSpot (excerpt): “This is an all-in-one media solution in terms of media management.”
Community forum excerpt (Reddit): “I’m going bonkers trying to implement opentext without pro services and it’s a friggin nightmare.” (Not DAM-specific, but signals potential implementation or services reliance across OpenText tooling.)

Why customers choose OpenText DAM (inferred)

Requirement for enterprise scale and governance capabilities
Support for complex workflows, records orientation, and regulated environments
Integration requirements with Adobe Creative Cloud, SAP ecosystem, Salesforce, and the broader OpenText stack

Vendor-published case signal

OpenText publishes customer excerpts highlighting Adobe Premiere integration and search capabilities (example: San Jose Sharks quote).

Critical evaluation: These are testimonial excerpts rather than independent case studies with baseline metrics (time saved, reuse rate, cycle time reduction, or cost impact). They are useful as anecdotal evidence but not independent ROI verification.

Analyst excerpts as supporting signals

Analyst materials (e.g., IDC MarketScape excerpts) identify strengths such as handling large asset and user volumes, processing loads, and regulated-environment use cases. Analyst reports often include vendor-provided guidance for some metrics; organizations should treat such figures as one input among others during diligence.

04Best fit

Company sizes

Best fit appears to be upper midmarket and enterprise organizations (typically large, multi-region operations with high asset and user volumes).

Industries / verticals

Analyst materials suggest relevance for industries with regulated processes and complex content lifecycles, including financial services, healthcare, utilities, manufacturing, and the public sector.

Roles and personas

Marketing operations / brand management leaders
Creative services / studio teams (Adobe CC users)
Digital experience / web teams integrating with CMS/e-commerce
IT / enterprise architecture teams
Compliance / records management / legal teams

Qualification criteria (good fit)

Requirement for on-prem/managed hosted/dedicated SaaS deployment options for data residency or regulatory reasons
Need to manage large libraries and complex metadata/taxonomy
Need for integrations with Adobe Creative Cloud, SAP, Salesforce, or the broader OpenText ecosystem
Need for governance features such as audit trails and rights/clearance workflows

05The pitch

What the product does (core value proposition)

OpenText Digital Asset Management (DAM) is a digital asset management platform designed for enterprise use that centralizes, governs, and distributes rich media (images, video, audio, documents) across teams, systems, and channels. OpenText describes the offering with the phrase “from creation to delivery.” The product documentation emphasizes support for workflows, collaboration, and maintaining brand consistency. OpenText’s product naming is variable: public-facing product messaging often uses “OpenText Digital Asset Management,” while some analyst materials and vendor collateral refer to **OpenText Media Management / Media Management CE** (Cloud Editions). This nomenclature variation can introduce ambiguity during evaluations and procurement.

Target market and market positioning

Target market (per analyst excerpt): upper midmarket and enterprise, including regulated and complex environments.
Positioning: marketed for larger organizations requiring governance, integration capabilities, and flexible hosting options. The product is commonly considered for deployments where integration with existing enterprise content and information management stacks is required.

Get a comprehensive analysis of OpenText Digital Asset Management including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →