Content migration to OpenText InfoArchive

Heroshot | Target Platform | OpenText InfoArchive

OpenText InfoArchive is an archive system based on xDB and implemented based on the OAIS standard. The InfoArchive connector creates up-front validated SIP packages while it complies with the before-mentioned standard. It is fully flexible and creates all necessary information and XML files that are needed for the ingestion. The XML structure of the eas_sip.xml and eas_pdi.xml can be fully customized according to the requirements or holding configuration.

  • Fully implemented OAIS standard support

  • Ruleset to create configured pre-validated SIP packages

  • Metadata within XML files fully customizable in values and structure

  • High performance through multi-threading

  • Suited for highly regulated environments

  • Schedule ingest jobs for automated active archiving

  • Free configurable packet sizes (SIP data size & number of AIUs per SIP)

migration-center is an official OpenText Services and Technology Partner:

Logo | Partner | OpenText | Services
Logo | Partner | OpenText | Technology

Platform-specific use cases

OAIS-conform long term data preservation

OpenText InfoArchive in combination with migration-center is the perfect solution for long-term data preservation, which comes into play whenever information needs to be retained for very long periods of time and therefore demands for platform-independent retention. InfoArchive uses extensible mark-up language (XML) as the format for preserving data and metadata and it implements the Open Archival Information System (OAIS). migration-center can transform data into a platform-independent interpretable format and enrich it with metadata to fulfill long term preservation standards such as METS and PREMIS. For unstructured content migration-center can be used to add long term interpretable format renditions such as PDF-A or TIFF. The migration-center InfoArchive importer then out-of-the-box creates OAIS-conform submission packages and ingests them to OpenText InfoArchive.

Active archiving - optimization of active business applications

migration-center supports the periodical migration of  business complete data and content from active applications to OpenText InfoArchive. By storing business complete data in InfoArchive costs for backups, system administration, servers, and database licensing can be reduced while at the same time significantly improving performance of the production environment used in daily business. With the help of widgets or integration via the REST API, secured read-only access to the data in the archive can be provided directly from the original application. migration-center’s scheduler can be programmed to check frequently for new business complete data and transfer it automatically to InfoArchive.

Application decommissioning

Moving forward and leveraging new technologies is essential to stay on top of digital transformation. But for all innovation, the proper retirement of old applications must not be neglected. OpenText InfoArchive as an archiving solution enables you to keep what you need, control disposition, and fulfill legal requirements towards retention and compliance.
Our certified solution migration-center assists you in classifying, transforming, and transferring your data and documents to InfoArchive all while preserving a complex multi-system chain of custody.
Data from applications that a company migrates to OpenText InfoArchive will remain accessible for business reporting, audits, or compliance with data retention regulations, enabling the organization to shut down the old applications and save all the costs associated with supporting and maintaining them as well as eliminating the security risk of outdated technology.

Application Decommissioning & Archiving

Logo | Medtronic | Gray
Logo | Alexion Pharmaceuticals | Gray
Logo | Swedish Armed Forces | Gray
Logo | OMV Petrom | Gray
Logo | Prince William County | Gray
Logo | ASTAD | Gray

All migration path capabilities in one list

The Connector Matrix allows you to create all currently available migration paths (source system in connection with target system) and to list the supported capabilities and versions.

Source System

Supported versions:

Target System

Supported versions: 4.0, 4.1, 4.2, 16.3, 16.4, 16.5, 16.7, 20.4

Feature Category Support