The OpenText InfoArchive Connector
Take control of archived content stored in OpenText InfoArchive. Migrate records, metadata, and retention history to open Lakehouse formats.
🌟 Featured in Gartner® Hype Cycle™ for Data Management
Connectors
Data Governance
Enterprise Clients
Talk to a Connector Expert
OpenText InfoArchive Migration and Content Extraction
Archon’s OpenText InfoArchive Connector extracts archived records, document content, metadata schemas, retention holds, and lifecycle policy records from InfoArchive environments and migrates them into open Parquet and Delta Lake formats on modern Lakehouse platforms. Designed for organizations retiring InfoArchive, consolidating archive platforms, or standardizing archived data within a broader governance and compliance ecosystem.
OpenText InfoArchive locks archived content into a proprietary repository. When organizations decide to move on, whether driven by cost, vendor consolidation, or a strategic shift to Lakehouse architecture, the content extraction challenge can be significant. Archon eliminates that challenge: full extraction of InfoArchive content with metadata integrity, retention hold preservation, and chain-of-custody continuity across the migration.
- InfoArchive REST API and xDB extraction for archived records and document content
- Archived records, metadata schemas, retention holds, and lifecycle events captured
- Active legal holds and retention controls preserved during migration
- Full-text and metadata search through Archon Analyzer after migration
- SEC 17a-4, FINRA, HIPAA, DoD 5015.02, and GDPR retention support maintained across migration
Capabilities
Everything You Need for OpenText InfoArchive Data Operations
Complete InfoArchive Content Extraction
Archon extracts all InfoArchive archived records, document content, metadata schemas, xDB collection structures, and application configurations while preserving the full metadata context of every archived record.
Retention Hold Migration
Active legal and compliance holds in InfoArchive are migrated to Archon with chain-of-custody continuity, ensuring no gap in hold enforcement across the migration timeline.
Vendor Lock-In Elimination
InfoArchive's proprietary xDB repository locks archived content in a format that cannot be accessed without InfoArchive infrastructure. Archon converts that content to open Parquet and Delta Lake formats, making it accessible without InfoArchive.
License Cost Elimination
OpenText InfoArchive licensing, annual maintenance, and infrastructure costs are among the highest in enterprise archiving. Archon migration eliminates those costs while preserving the complete compliance posture of every archived record.
Use Cases
How Enterprises Use the OpenText InfoArchive Connector
01 InfoArchive Platform Migration
Organizations replacing OpenText InfoArchive extract records, documents, metadata, and hold information through Archon and retire legacy archive infrastructure while maintaining access to historical content.
02 OpenText License Cost Reduction
InfoArchive licensing and OEM support represent significant annual costs. Archon migration enables complete license elimination while maintaining key compliance controls such as WORM storage, record integrity verification, and hold enforcement.
03 ECM and Archive Consolidation
Organizations consolidating content repositories from InfoArchive, SharePoint, and FileNet into a unified Lakehouse compliance platform use Archon's InfoArchive connector as part of the enterprise-wide archiving consolidation program.
04 eDiscovery Without InfoArchive
Legal proceedings requiring InfoArchive-held records are fulfilled through Archon Analyzer after migration, providing full-text and metadata search across migrated records from a centralized archive environment.
Technical Specifications
| Specification | Details |
|---|---|
| Connection Method | InfoArchive REST API / xDB direct database connection |
| Supported Versions | OpenText InfoArchive 4.x, 16.x, 20.x, 22.x, 23.x |
| Data Scope | Archived records, document content, metadata schemas, retention holds, audit logs, lifecycle events |
| Output Format | Parquet, Delta Lake, Avro, XML, CSV, Excel |
| Metadata Handling | xDB schema definitions, InfoArchive application configurations, hold state records |
| Transformation Rules | InfoArchive schema normalization supported |
| Retention Management | SEC 17a-4, FINRA, HIPAA, DoD 5015.02, GDPR retention schedules — compliance posture maintained across migration |
| Legal Hold | Hold migration with chain-of-custody continuity; new holds managed natively in Archon |
| Deployment | On-premises · Cloud (AWS) · Hybrid |
| Security & Compliance | TLS 1.3 in transit · AES-256 encryption at rest · WORM storage support · audit logging |
How It Works
Up and Running in 4 Steps
01
Connect to InfoArchive
Authenticate via InfoArchive REST API or direct xDB database connection. Archon auto-discovers all applications, collections, schemas, and active legal holds. 02
Map & Configure
Define application and collection scope, hold migration strategy, metadata schema mapping, and target Lakehouse configuration. Map InfoArchive retention schedules to Archon policy framework. 03
Validate & Preview
Run a dry-run against sample InfoArchive applications. Quality report flags schema mapping gaps, hold state anomalies, and content extraction issues before full migration. 04
Migrate & Monitor
Execute full extraction and migration. Active holds transferred with chain-of-custody continuity. All records searchable via Archon Analyzer immediately on ingestion.FAQ
Common Questions About the OpenText InfoArchive Connector
- 1. Does Archon preserve active InfoArchive legal holds across the migration?
Yes. Archon migrates active legal and compliance holds with chain-of-custody continuity — ensuring no gap in hold enforcement between InfoArchive decommission and Archon activation.
- 2. Can Archon extract InfoArchive xDB content without OpenText support?
Yes. Archon's InfoArchive connector can extract xDB content directly, reducing dependency on external migration services during archive modernization projects.
- 3. Does the Archon migration maintain SEC Rule 17a-4 compliance posture?
Yes. Archon's migration preserves record retention controls and non-rewriteable storage requirements, maintaining SEC Rule 17a-4 and FINRA Rule 4511 compliance requirements throughout the migration.
- 4. Can Archon migrate InfoArchive content across all application types — documents, structured data, and email?
Yes. Archon handles InfoArchive applications containing document content, structured data records, and email archives, extracting all content types with their associated metadata schemas.
- 5. What happens to InfoArchive retention schedules during migration?
Archon maps InfoArchive retention schedule configurations to Archon's policy framework, ensuring all retention rules, disposition schedules, and hold conditions are enforced in the Archon archive.
Looking to move archived content out of InfoArchive?
Speak with an Archon expert about your migration goals and explore ways to preserve archived records in open, future-ready formats.
