OpenText Information Archive - LionBridge Integration and Automation

Common Integration Use Cases Between OpenText Information Archive and Lionbridge

1. Archiving translated content packages after localization approval

Data flow: Lionbridge ? OpenText Information Archive

When multilingual content is completed and approved in Lionbridge, the final translated source files, translation memory references, glossaries, and approval records can be archived in OpenText Information Archive. This creates a compliant record of what was published in each language, when it was approved, and by whom.

• Supports auditability for regulated industries and global brands
• Preserves final localized assets for future reuse or dispute resolution
• Reduces storage and version sprawl in translation workspaces

2. Retaining legacy multilingual content during system decommissioning

Data flow: Legacy content repositories and CMS platforms ? OpenText Information Archive, with translation references from Lionbridge

When retiring a legacy CMS or digital asset repository that contains multilingual content, OpenText Information Archive can store the original content and associated translated versions. Lionbridge can provide translation metadata, language variants, and localization history to ensure archived content remains understandable and traceable after the source system is shut down.

• Enables legacy system retirement without losing multilingual business records
• Preserves access to translated customer-facing content and legal notices
• Reduces maintenance costs for obsolete platforms

3. Archiving translation project artifacts for compliance and governance

Data flow: Lionbridge ? OpenText Information Archive

Translation projects often generate source files, translated deliverables, reviewer comments, terminology decisions, and approval logs. Integrating Lionbridge with OpenText Information Archive allows these project artifacts to be automatically retained according to corporate retention policies, supporting governance and quality control.

• Creates a defensible record of translation decisions and approvals
• Helps meet industry and regional compliance requirements
• Improves traceability across localization, legal, and content teams

4. Preserving multilingual regulated content for long-term retention

Data flow: Lionbridge ? OpenText Information Archive

For regulated content such as product labels, safety instructions, financial disclosures, or policy documents, translated versions must often be retained for many years. Lionbridge can deliver the finalized localized content to OpenText Information Archive, where it is stored with retention rules aligned to regulatory obligations.

• Supports long-term retention of language-specific compliance content
• Reduces risk of losing approved translations after publication cycles
• Provides a centralized archive for audit and legal review

5. Reusing archived translations to reduce localization costs

Data flow: OpenText Information Archive ? Lionbridge

Archived translated documents and approved language variants in OpenText Information Archive can be retrieved and sent to Lionbridge as reference material for new translation projects. This helps linguists reuse prior approved wording, terminology, and style patterns, improving consistency and reducing retranslation effort.

• Lowers translation costs through reuse of approved content
• Improves consistency across product lines and regions
• Speeds up turnaround for repeat or derivative content

6. Archiving multilingual customer communications for legal hold and eDiscovery

Data flow: Lionbridge ? OpenText Information Archive

Customer communications, notices, and service messages translated through Lionbridge can be archived in OpenText Information Archive to support legal hold, eDiscovery, and regulatory investigations. This is especially valuable when organizations must prove what was communicated in each language and when it was distributed.

• Maintains a complete record of multilingual external communications
• Supports legal and compliance teams during investigations
• Reduces risk from inconsistent or missing translated records

7. Centralizing multilingual content history for content operations and audit teams

Data flow: Bi-directional between Lionbridge and OpenText Information Archive

Content operations teams can use Lionbridge for active translation workflows while OpenText Information Archive serves as the system of record for completed content. Metadata such as language, version, approval status, retention class, and publication date can be synchronized so teams can quickly identify the authoritative version of any localized asset.

• Improves visibility across localization, compliance, and records management teams
• Reduces duplicate storage and manual tracking of versions
• Ensures archived content remains linked to its translation history