OpenText Information Archive - Sanity Integration and Automation

Common Integration Use Cases Between OpenText Information Archive and Sanity

1. Archive published content versions for compliance and auditability

Data flow: Sanity ? OpenText Information Archive

When marketing, legal, or regulated business content is published from Sanity, the final approved version can be automatically archived in OpenText Information Archive with metadata such as author, approval date, campaign, region, and retention class. This creates a defensible record of what was published at a specific point in time.

• Supports audit requests and regulatory reviews
• Preserves historical content even after edits or deletion in Sanity
• Reduces manual export and filing effort for content operations teams

2. Retain regulated content after decommissioning legacy publishing systems

Data flow: Legacy system ? OpenText Information Archive ? Sanity

During modernization programs, legacy web or content repositories can be retired while their historical content is preserved in OpenText Information Archive. Selected content, such as approved policy pages, product disclosures, or archived campaign assets, can then be surfaced in Sanity for controlled reuse or reference in new digital experiences.

• Enables system retirement without losing access to historical content
• Reduces infrastructure and support costs for obsolete platforms
• Allows content teams to reuse approved legacy material in new channels

3. Store final approved content packages for long-term retention

Data flow: Sanity ? OpenText Information Archive

For high-value content packages such as annual reports, investor communications, product documentation, or regulated customer notices, Sanity can trigger archival of the final approved content bundle into OpenText Information Archive. The archive can retain the content body, associated assets, and approval metadata for the required retention period.

• Ensures retention policies are applied consistently
• Provides a single source of truth for final approved records
• Improves legal hold readiness and disposition control

4. Retrieve archived content for controlled reuse in new digital experiences

Data flow: OpenText Information Archive ? Sanity

Content teams can search OpenText Information Archive for previously approved materials and import selected records into Sanity as reusable content entries. This is useful when launching a new site, regional microsite, or campaign that needs validated historical content, such as product descriptions, compliance statements, or policy language.

• Speeds up content creation by reusing approved material
• Reduces risk of rewriting regulated text incorrectly
• Supports consistent messaging across channels and regions

5. Preserve content governance evidence for approvals and change history

Data flow: Sanity ? OpenText Information Archive

Sanity collaboration data such as approval snapshots, editorial notes, and publish history can be archived alongside the content record in OpenText Information Archive. This gives compliance, legal, and internal audit teams a complete evidence trail showing who approved content, when it changed, and what was published.

• Strengthens governance for regulated industries
• Reduces time spent gathering evidence during audits
• Improves accountability across editorial and compliance teams

6. Archive expired campaign content and assets after campaign close

Data flow: Sanity ? OpenText Information Archive

At the end of a campaign, Sanity can automatically send the final campaign page content, copy variants, and related metadata to OpenText Information Archive before removing the content from active use. This keeps the production environment clean while preserving a complete record for future reference, legal review, or performance analysis.

• Reduces clutter in active content repositories
• Supports post-campaign review and brand governance
• Maintains a searchable record of past campaigns for reuse or compliance

7. Support retention and disposition workflows for content lifecycle management

Data flow: Bi-directional

Sanity can manage the active lifecycle of content, while OpenText Information Archive enforces long-term retention and disposition rules once content is no longer actively edited. When a retention period expires, disposition actions can be triggered in the archive and status updates can be reflected back to Sanity for visibility to content owners.

• Aligns editorial workflows with records management policies
• Automates retention, legal hold, and disposal processes
• Gives business teams visibility into content lifecycle status

8. Provide a governed content source for regulated omnichannel publishing

Data flow: OpenText Information Archive ? Sanity

For industries such as financial services, healthcare, and public sector, archived authoritative content can be exposed to Sanity for use in websites, portals, and digital experiences. Sanity then acts as the presentation and reuse layer, while OpenText Information Archive remains the governed record system for approved source content.

• Separates active content delivery from records retention
• Improves consistency for regulated statements across channels
• Enables faster digital publishing without compromising compliance