Home | Connectors | Bynder | Bynder - OpenText InfoArchive Integration and Automation

Bynder - OpenText InfoArchive Integration and Automation

Integrate Bynder Digital Asset Management (DAM) and OpenText InfoArchive Cloud Storage apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between Bynder and OpenText InfoArchive

1. Archive approved brand assets after campaign completion

Data flow: Bynder to OpenText InfoArchive

When a campaign ends, final approved creative files, brand guidelines, and supporting documents can be automatically transferred from Bynder into OpenText InfoArchive for long-term retention. This helps marketing teams keep Bynder focused on active content while ensuring completed campaign materials remain available for audit, legal review, and historical reference.

  • Reduces clutter in the active DAM environment
  • Supports retention policies for regulated industries
  • Preserves evidence of approved brand usage and campaign execution

2. Retain legally sensitive asset versions and rights documentation

Data flow: Bynder to OpenText InfoArchive

Bynder often stores licensed images, talent releases, usage rights, and approval records tied to creative assets. These records can be archived in OpenText InfoArchive to support compliance, contract management, and dispute resolution. This is especially valuable when rights expire or when organizations need to prove authorized use years after publication.

  • Maintains a compliant record of asset usage rights
  • Supports legal hold and audit requirements
  • Reduces risk of using expired or unauthorized content

3. Decommission legacy marketing repositories while preserving access to historical assets

Data flow: Legacy system to OpenText InfoArchive, then selective access back to Bynder

During a marketing technology modernization program, historical assets and metadata from legacy content repositories can be archived in OpenText InfoArchive before the old system is retired. Key approved assets or reference materials can then be surfaced in Bynder for ongoing use, while the full historical record remains preserved in the archive.

  • Enables legacy system retirement without data loss
  • Reduces infrastructure and support costs
  • Provides controlled access to historical content when needed

4. Archive completed creative workflow records and approvals

Data flow: Bynder to OpenText InfoArchive

Bynder workflow artifacts such as review comments, approval history, version notes, and final sign-off records can be archived in OpenText InfoArchive once a project is closed. This creates a defensible record of who approved what and when, which is useful for governance, brand compliance, and internal audit teams.

  • Improves traceability of creative decisions
  • Supports internal controls and audit readiness
  • Preserves workflow evidence without burdening active users

5. Preserve regional and franchise marketing materials for long-term governance

Data flow: Bynder to OpenText InfoArchive

Consumer brands and franchise organizations often manage large volumes of localized marketing content in Bynder. Once regional promotions or store-level campaigns are retired, final versions can be archived in OpenText InfoArchive to maintain a complete record of what was distributed in each market. This is useful for brand governance, franchise compliance, and post-campaign analysis.

  • Supports distributed marketing oversight
  • Creates a historical record of local market execution
  • Helps resolve disputes over approved regional content

6. Store expired digital assets and disposition records for regulatory retention

Data flow: Bynder to OpenText InfoArchive

Assets that are no longer active but must be retained for a defined period, such as product images, packaging artwork, or regulated disclosures, can be moved from Bynder into OpenText InfoArchive with associated retention and disposition rules. This ensures content is kept only as long as required and then disposed of according to policy.

  • Aligns content retention with corporate policy
  • Reduces legal and compliance exposure
  • Automates end-of-life handling for obsolete assets

7. Provide archived reference content back to marketing teams when needed

Data flow: OpenText InfoArchive to Bynder

When teams need to reuse historical brand materials, OpenText InfoArchive can supply archived assets or metadata back into Bynder for controlled reactivation. This is useful for rebranding, anniversary campaigns, product relaunches, or legal reviews where prior versions must be compared against current standards.

  • Speeds retrieval of historical content
  • Supports reuse of approved legacy materials
  • Improves collaboration between marketing, legal, and compliance teams

8. Centralize compliance reporting on asset lifecycle and retention status

Data flow: Bi-directional metadata exchange between Bynder and OpenText InfoArchive

By synchronizing key metadata such as asset owner, campaign name, expiration date, rights status, and retention class, organizations can create a unified view of content lifecycle across Bynder and OpenText InfoArchive. Marketing, legal, and records management teams can then monitor which assets are active, archived, pending disposition, or subject to legal hold.

  • Improves visibility across content and records systems
  • Supports governance and compliance reporting
  • Helps teams act on retention and disposition events faster

How to integrate and automate Bynder with OpenText InfoArchive using OneTeg?