
# OpenText Information Archive

Archive legacy application data and content while retaining searchable access and lifecycle controls.

Canonical page: https://launchinyourcloud.com/directory/infoarchive/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## OpenText Information Archive

Archive legacy application data and content while retaining searchable access and lifecycle controls.

- Listing: https://launchinyourcloud.com/directory/infoarchive/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: unspecified
- License: Commercial software licensing; confirm the current archive edition, metrics and deployment contract.
- Licensing model: commercial-only
- Installation: Arrange the documented on-premises deployment and implementation with OpenText.
- Architecture: Enterprise archival platform; exact current on-premises topology requires vendor sizing and design.
- Operations: Plan extraction, information packages, validation, storage, retention, access, backups and upgrades.
- Product website: https://www.opentext.com/products/information-archive
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Formerly InfoArchive. The current product explicitly supports on-premises deployment. Named cloud availability alone does not establish deployment in your account.

The listed OpenText archive is licensed commercial software. The vendor license-model schedule explicitly includes OT InfoArchive; current metrics, bundles and terms must be confirmed for the renamed product.

The current product page establishes on-premises deployment but does not specify a complete current runtime topology; infrastructure is left unspecified.


### Category fit

- legacy-system-archive-access: Dedicated structured/unstructured data archiving and legacy application decommissioning while preserving governed historical access.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/blogs/apn/manage-your-business-complete-data-with-opentext-infoarchive-and-aws/ (checked 2026-11-12). 


### Cloud deployment evidence

- Customer-deployed OpenText InfoArchive architecture on AWS (aws): https://aws.amazon.com/blogs/apn/manage-your-business-complete-data-with-opentext-infoarchive-and-aws/
  AWS and OpenText explicitly distinguish customer-deployed InfoArchive from the managed offering. Their reference architecture places the web application, directory service and InfoArchive server on EKS in private subnets, with S3, EFS and RDS. Confirm the current product release, licensing, sizing and operating agreement before implementation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Current product, legacy retirement and on-premises deployment: https://www.opentext.com/products/information-archive

- InfoArchive license model schedule: https://www.opentext.com/assets/documents/en-US/pdf/opentext-license-model-schedule-for-ecd-software-en.pdf

- Vendor implementation and on-premises upgrade responsibilities: https://careers.opentext.com/us/en/job/53767/Principal-Consultant

### Licensing sources

- https://www.opentext.com/assets/documents/en-US/pdf/opentext-license-model-schedule-for-ecd-software-en.pdf

### Infrastructure sources

- https://www.opentext.com/products/information-archive


### Buyer diligence


Research coverage: 4/12 fields (33%); 1 documented, 3 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The accessible developer overview and REST material do not establish a version-matched user-facing SAML/OIDC integration for customer-managed Information Archive. API bearer/JWT access and a generic OpenText identity service do not by themselves prove the archive UI login path and entitlement. Scope: Customer-managed Information Archive user federation remains unconfirmed. Source: https://developer.opentext.com/ce/products/infoarchive (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The product page confirms on-premises and hybrid deployment options but does not identify an installable package or current IaC artifact. A deployment model is not enough to establish the installer, version compatibility or entitlement; obtain the licensed installation documentation. Scope: Current customer-operated product; installer/artifact remains unconfirmed. Source: https://www.opentext.com/products/information-archive (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The accessible product/developer overview does not supply quantitative current production CPU/RAM/storage or HA sizing. A lightweight test-installation statement cannot size archive ingestion, indexes, retention, retrieval or database/storage replicas. Scope: Customer-managed Information Archive production sizing remains unconfirmed. Source: https://developer.opentext.com/ce/products/infoarchive (reviewed 2026-11-21).

- License pricing: Documented. The published ECD software schedule (effective 2021) identifies InfoArchive as application-specific licensed software and defines order-selected usage metrics and restrictions. This documents a commercial licensing framework, not the metric or price of a current customer order; confirm current product/DR/non-production entitlements. Scope: Historical public ECD licence framework naming InfoArchive; current transaction documents control. Source: https://www.opentext.com/assets/documents/en-US/pdf/opentext-license-model-schedule-for-ecd-software-en.pdf (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






