Brandfolder - OpenText Core Digital Asset Management Integration and Automation

Common Integration Use Cases Between Brandfolder and OpenText Core Digital Asset Management

1. Centralized master asset sync for brand governance

Direction: OpenText Core Digital Asset Management to Brandfolder

Use OpenText Core Digital Asset Management as the enterprise master repository for approved brand assets, then automatically publish selected assets to Brandfolder for broader marketing and product team access. This ensures Brandfolder users always work from the latest approved logos, campaign images, and brand templates while preserving governance in the source system.

• Reduces duplicate asset storage across teams
• Improves brand consistency by limiting access to approved versions
• Speeds up asset availability for distributed teams

2. Campaign asset distribution from marketing to regional teams

Direction: OpenText Core Digital Asset Management to Brandfolder

When a campaign is finalized in OpenText Core Digital Asset Management, push the approved creative set into Brandfolder collections for regional marketing, sales, and channel partners. Metadata such as campaign name, market, language, usage rights, and expiration dates can be carried over to make assets easy to find and use correctly.

• Accelerates campaign rollout across regions
• Supports localized asset access with consistent governance
• Reduces manual packaging and email-based distribution

3. Brandfolder asset requests and approvals routed to enterprise DAM

Direction: Brandfolder to OpenText Core Digital Asset Management

When users in Brandfolder request new assets, variants, or updated files, route the request to OpenText Core Digital Asset Management for review, approval, and final storage. This is useful for organizations that want Brandfolder to serve as the front-end collaboration layer while OpenText Core Digital Asset Management remains the controlled production repository.

• Creates a structured intake and approval process
• Improves auditability for asset changes
• Prevents uncontrolled publishing of unapproved content

4. Metadata synchronization for improved search and reuse

Direction: Bi-directional

Synchronize key metadata fields between both platforms, such as product line, region, language, campaign, rights status, and expiration date. This allows teams in either system to search and filter assets using the same business terms, improving discoverability and reducing time spent locating the correct file.

• Creates a consistent metadata model across platforms
• Improves search accuracy and asset reuse
• Supports compliance by keeping rights and expiry data aligned

5. Product launch content distribution to sales and partner portals

Direction: OpenText Core Digital Asset Management to Brandfolder

For product launches, approved product photography, spec sheets, packaging visuals, and launch banners can be published from OpenText Core Digital Asset Management into Brandfolder collections dedicated to sales enablement or partner use. This gives commercial teams quick access to launch-ready content without exposing unfinished source files.

• Shortens time to market for launch materials
• Ensures sales teams use current product assets
• Supports controlled external sharing through curated collections

6. Rights management and expiration control across both systems

Direction: OpenText Core Digital Asset Management to Brandfolder

Synchronize usage rights, license terms, and expiration dates from OpenText Core Digital Asset Management into Brandfolder so users are warned before using assets that are nearing expiry or restricted by geography or channel. This is especially valuable for organizations managing third-party photography, talent releases, or licensed creative.

• Reduces legal and compliance risk
• Prevents accidental use of expired or restricted assets
• Improves governance for regulated industries and global brands

7. Workflow status updates for cross-team visibility

Direction: Bi-directional

Keep asset status synchronized between the two platforms, such as draft, in review, approved, archived, or replaced. Marketing teams working in Brandfolder can see whether an asset is ready for use, while content managers in OpenText Core Digital Asset Management can track downstream adoption and lifecycle status.

• Improves transparency across creative, marketing, and operations teams
• Reduces confusion about which version is approved
• Supports better asset lifecycle management

8. Migration or consolidation of legacy asset libraries

Direction: Brandfolder to OpenText Core Digital Asset Management or OpenText Core Digital Asset Management to Brandfolder

For organizations consolidating platforms, use integration to migrate selected asset libraries, metadata, and folder structures from one system to the other. This can support phased migration by moving high-value or business-critical collections first while maintaining access to legacy content during transition.

• Minimizes disruption during platform consolidation
• Preserves metadata and governance rules during migration
• Enables phased adoption by business unit or region