OpenText Information Archive - Adobe Experience Manager Sites Integration and Automation

Common Integration Use Cases Between OpenText Information Archive and Adobe Experience Manager Sites

1. Archive expired web content from Adobe Experience Manager Sites to OpenText Information Archive

Data flow: Adobe Experience Manager Sites ? OpenText Information Archive

When pages, landing pages, campaign microsites, or promotional content in Adobe Experience Manager Sites reach end of life, they can be automatically exported to OpenText Information Archive for compliant long-term retention. This preserves the content, metadata, and publication history while removing inactive assets from the live CMS.

• Reduces content clutter in AEM Sites
• Supports legal and regulatory retention requirements
• Lowers storage and maintenance costs for obsolete content
• Helps marketing teams manage content lifecycle more efficiently

2. Preserve website content for audit and legal discovery

Data flow: Adobe Experience Manager Sites ? OpenText Information Archive

Organizations can archive published website snapshots, page versions, and associated approvals from Adobe Experience Manager Sites into OpenText Information Archive to create an immutable record for audits, disputes, and legal requests. This is especially valuable for regulated industries that must prove what was published and when.

• Maintains evidence of published content and approvals
• Improves response time for audits and legal holds
• Reduces risk of content tampering or accidental deletion
• Supports governance across marketing and compliance teams

3. Retrieve archived content for reuse in new digital experiences

Data flow: OpenText Information Archive ? Adobe Experience Manager Sites

Archived articles, product descriptions, policy pages, and campaign assets stored in OpenText Information Archive can be searched and selectively restored into Adobe Experience Manager Sites when teams need to repurpose proven content for new campaigns or regional sites. This avoids recreating content from scratch and accelerates launch cycles.

• Speeds up content reuse across campaigns and markets
• Reduces duplicate authoring effort
• Improves consistency of approved messaging
• Supports controlled restoration of historical content

4. Decommission legacy web content repositories while keeping AEM Sites as the front end

Data flow: Legacy content systems ? OpenText Information Archive, with Adobe Experience Manager Sites as the active publishing layer

During modernization programs, legacy web content repositories can be retired by archiving historical pages, documents, and related records in OpenText Information Archive. Adobe Experience Manager Sites then becomes the primary system for active content management, while archived content remains accessible for reference and compliance.

• Enables legacy system retirement with minimal business disruption
• Preserves access to historical content without keeping old platforms online
• Reduces infrastructure and support costs
• Supports phased digital transformation initiatives

5. Manage content retention and disposition based on website lifecycle rules

Data flow: Adobe Experience Manager Sites ? OpenText Information Archive

Content governance teams can define retention rules for specific content types in Adobe Experience Manager Sites, such as campaign pages, event microsites, or regulated disclosures. Once the retention period ends, content is transferred to OpenText Information Archive for disposition management, ensuring the organization follows policy consistently.

• Automates content lifecycle governance
• Reduces manual review and deletion tasks
• Improves policy compliance across business units
• Creates a defensible disposition process

6. Provide customer service and compliance teams with access to archived web content

Data flow: OpenText Information Archive ? Adobe Experience Manager Sites, or OpenText Information Archive as the source of record

Customer service, compliance, or legal teams may need to verify what information was shown on a website at a specific point in time. Archived content in OpenText Information Archive can be linked from internal portals or surfaced through controlled access workflows tied to Adobe Experience Manager Sites, allowing teams to retrieve historical content without exposing it publicly.

• Improves internal access to historical website records
• Supports customer complaints and regulatory inquiries
• Limits access to authorized users only
• Reduces dependency on IT for content retrieval

7. Retain approved content variants and localization history for governance

Data flow: Adobe Experience Manager Sites ? OpenText Information Archive

For organizations managing multilingual or region-specific websites, approved page variants and localization versions can be archived in OpenText Information Archive after publication. This creates a complete history of content changes across markets and helps teams demonstrate governance over translated or localized messaging.

• Tracks content changes across regions and languages
• Supports brand and regulatory consistency
• Provides a historical record of approved variants
• Helps global marketing teams manage content at scale