Agility - OpenText InfoArchive Integration and Automation

Common Integration Use Cases Between Agility and OpenText InfoArchive

Agility CMS and OpenText InfoArchive complement each other well in organizations that need to balance modern digital content delivery with long-term information retention and compliance. Agility supports fast, marketer-friendly content creation and omnichannel publishing, while InfoArchive provides secure archiving, retention, and disposition for records and legacy data. Together, they can support content lifecycle management, regulatory governance, and cost reduction across digital operations.

1. Archive retired web content and landing pages for compliance and auditability

Data flow: Agility to OpenText InfoArchive

When marketing campaigns, product microsites, or event landing pages are retired in Agility, the final published content, metadata, and supporting assets can be archived in InfoArchive for long-term retention. This gives legal, compliance, and audit teams a preserved record of what was published, when it was published, and who approved it.

• Preserves historical web content for regulatory review
• Reduces risk of losing evidence of published claims or disclosures
• Supports retention policies for campaign and brand records

2. Retain approved content versions and editorial history for governance

Data flow: Agility to OpenText InfoArchive

Agility content items, page versions, and approval records can be periodically archived to InfoArchive once content is published or superseded. This creates a governed record of editorial changes, which is useful for regulated industries such as financial services, healthcare, and public sector organizations.

• Captures version history and approval evidence
• Supports internal governance and content audit trails
• Helps teams prove which content was active at a specific point in time

3. Decommission legacy content repositories while keeping content accessible

Data flow: Legacy content sources into OpenText InfoArchive, then selected content references exposed to Agility if needed

Organizations migrating from older web CMS platforms can archive legacy content in InfoArchive before or during the move to Agility. Agility can then host only active, customer-facing content, while InfoArchive retains historical content for legal, operational, or reference purposes. If needed, Agility pages can link to archived records for internal users.

• Reduces the cost of maintaining obsolete systems
• Preserves access to historical content without keeping the old CMS online
• Supports phased migration and controlled system retirement

4. Archive regulated digital assets and supporting documentation

Data flow: Agility to OpenText InfoArchive

Agility often manages content that includes brochures, product sheets, disclosures, and campaign assets. Final approved versions of these documents, along with related metadata such as publication date, owner, and approval status, can be archived in InfoArchive to meet retention requirements and simplify records management.

• Centralizes retention of published documents and supporting files
• Improves control over regulated marketing materials
• Helps ensure expired materials are retained or disposed of according to policy

5. Support legal hold and eDiscovery for published digital content

Data flow: Agility to OpenText InfoArchive

When litigation, investigations, or regulatory inquiries arise, content published through Agility can be exported to InfoArchive and placed under legal hold. This ensures the organization can preserve specific pages, assets, and related metadata without altering the live website or marketing workflow.

• Enables rapid preservation of relevant digital content
• Reduces disruption to marketing and web operations
• Improves responsiveness to legal and compliance requests

6. Maintain a long-term record of customer-facing disclosures and policy pages

Data flow: Agility to OpenText InfoArchive

Organizations can archive privacy notices, terms and conditions, accessibility statements, pricing disclosures, and other customer-facing policy pages from Agility into InfoArchive on a scheduled basis. This creates a defensible record of what customers saw at a given time, which is especially valuable for regulated or high-risk business environments.

• Provides evidence of published policy content over time
• Supports compliance with consumer protection and privacy obligations
• Reduces manual effort in tracking historical page changes

7. Feed archived content metadata into content lifecycle reporting

Data flow: OpenText InfoArchive to Agility or shared reporting layer

Archived content metadata from InfoArchive can be used to inform content lifecycle dashboards, helping marketing and compliance teams identify which pages, assets, or campaigns are due for review, renewal, or disposal. This can improve governance over content sprawl and reduce the risk of outdated information remaining accessible.

• Improves visibility into content retention status
• Supports scheduled review and disposition workflows
• Helps teams manage stale or obsolete content more effectively

Together, Agility and OpenText InfoArchive enable a clean separation between active digital experience management and long-term compliant retention. Agility remains focused on publishing and content operations, while InfoArchive provides the controlled archive needed for governance, risk reduction, and legacy system retirement.