OpenText Content Storage Service - LionBridge Integration and Automation

Common Integration Use Cases Between OpenText Content Storage Service and Lionbridge

1. Automated Translation of Archived Enterprise Content

Data flow: OpenText Content Storage Service ? Lionbridge

When organizations need to localize stored documents, product manuals, policies, or marketing assets, OpenText Content Storage Service can act as the secure source repository while Lionbridge handles translation and localization workflows. Content is selected from storage, sent to Lionbridge for translation, and returned to the repository with language-specific versions and metadata.

• Reduces manual file handling and version confusion
• Speeds up multilingual content delivery
• Supports controlled access to source and translated files

2. Centralized Storage for Multilingual Content Packages

Data flow: Lionbridge ? OpenText Content Storage Service

After translation is completed in Lionbridge, final localized files can be automatically stored in OpenText Content Storage Service as the enterprise system of record. This creates a single, durable archive for all language variants, supporting compliance, auditability, and long-term retention.

• Creates a governed archive for translated assets
• Improves traceability across language versions
• Supports retention and lifecycle policies for global content

3. Translation Workflow for Large-Scale Content Migration Projects

Data flow: OpenText Content Storage Service ? Lionbridge ? OpenText Content Storage Service

During cloud migration or content modernization initiatives, organizations often need to move legacy content into a new repository while also localizing high-value assets. OpenText Content Storage Service can store the migrated source content, send selected items to Lionbridge for translation, and then receive the localized outputs back into structured storage.

• Combines migration and localization in one controlled process
• Helps global teams launch migrated content faster
• Reduces duplicate storage and unmanaged file copies

4. Multilingual Compliance and Policy Distribution

Data flow: OpenText Content Storage Service ? Lionbridge ? OpenText Content Storage Service

Enterprises often need to distribute policies, legal notices, HR documents, and regulatory materials in multiple languages. Source documents stored in OpenText Content Storage Service can be routed to Lionbridge for translation, then stored back with language tags, approval status, and retention rules applied.

• Supports regulated content distribution across regions
• Improves consistency of policy communication
• Enables audit-ready storage of approved translations

5. Localization of Product Documentation and Technical Assets

Data flow: OpenText Content Storage Service ? Lionbridge ? OpenText Content Storage Service

Manufacturers and software companies can use OpenText Content Storage Service to store source documentation, release notes, and technical diagrams, then send selected assets to Lionbridge for localization. Completed translations are returned and stored alongside the original content for easy retrieval by regional teams.

• Accelerates release readiness for global markets
• Ensures localized documentation stays aligned with source versions
• Improves access for support, sales, and field teams

6. Secure Storage of Translation Source Files and Deliverables

Data flow: Bi-directional

OpenText Content Storage Service can serve as the secure content vault for source files sent to Lionbridge and for the translated deliverables returned from Lionbridge. This bi-directional integration supports controlled handoff, version tracking, and centralized governance across the translation lifecycle.

• Minimizes risk of lost or outdated files
• Supports enterprise security and access control requirements
• Provides a complete content history for each project

7. Global Content Lifecycle Management

Data flow: Bi-directional

Organizations managing large volumes of multilingual content can use OpenText Content Storage Service for long-term storage and lifecycle management, while Lionbridge handles translation updates when source content changes. This is especially useful for recurring content such as training materials, product catalogs, and customer communications.

• Keeps translated content synchronized with source updates
• Reduces rework on repeated translation cycles
• Supports scalable governance for global content operations