SFTP - OpenText Information Archive Integration and Automation

Common Integration Use Cases Between SFTP and OpenText InfoArchive

Below are practical integration scenarios where SFTP and OpenText InfoArchive work together to improve secure file handling, compliance, retention, and operational efficiency.

1. Secure Ingestion of Regulatory Files into Long-Term Archive

Data flow: SFTP to OpenText InfoArchive

Business units, external partners, or service providers can deliver regulated files such as invoices, claims records, audit evidence, or customer statements through SFTP. OpenText InfoArchive then ingests these files for compliant long-term retention with searchable access and retention policies.

• Reduces manual handling of sensitive documents
• Supports audit readiness and regulatory retention requirements
• Creates a controlled archive repository for structured and unstructured content

2. Archiving Legacy System Extracts Before Decommissioning

Data flow: Legacy application exports to SFTP to OpenText InfoArchive

When retiring a legacy ERP, billing, or document management system, teams can export historical records to SFTP in scheduled batches. OpenText InfoArchive receives the extracts and preserves them for legal, operational, and compliance access after the source system is shut down.

• Enables system decommissioning without losing historical data access
• Reduces infrastructure and licensing costs
• Minimizes risk associated with keeping obsolete systems online

3. Secure Transfer of Customer and Transaction Records for Compliance Archiving

Data flow: SFTP to OpenText InfoArchive

Finance, insurance, healthcare, and public sector organizations often receive customer records, transaction logs, or case files from internal systems or external processors via SFTP. These files can be automatically archived in OpenText InfoArchive to meet retention, privacy, and audit obligations.

• Improves governance over sensitive records
• Supports retention schedules and disposition controls
• Provides traceability for compliance audits and legal reviews

4. Archiving Distributed Partner Deliverables and Proof of Delivery

Data flow: SFTP to OpenText InfoArchive

Organizations that exchange production files, shipping confirmations, signed forms, or vendor deliverables through SFTP can store the final copies in OpenText InfoArchive as the system of record. This is useful when multiple teams need a retained copy of what was sent or received.

• Creates a defensible record of external file exchanges
• Supports dispute resolution and contract compliance
• Centralizes evidence across procurement, operations, and legal teams

5. Archiving High-Volume Output Files from Core Business Systems

Data flow: Core systems to SFTP to OpenText InfoArchive

Applications such as billing platforms, HR systems, or customer communication engines can generate large output files that are staged on SFTP and then archived in OpenText InfoArchive. This pattern is common for statements, notices, reports, and batch-generated documents that must be retained but not actively managed in the source system.

• Offloads storage from production systems
• Improves application performance by reducing retained file volume
• Ensures consistent retention across business-critical outputs

6. Controlled Access to Archived Files for Audit and Legal Teams

Data flow: OpenText InfoArchive to SFTP

When auditors, regulators, or legal teams need a specific set of archived files, OpenText InfoArchive can be used to retrieve approved content and export it securely through SFTP. This provides a controlled method for sharing archived evidence without exposing the archive directly.

• Limits access to only approved file sets
• Maintains secure transfer and auditability
• Supports eDiscovery, audits, and regulatory requests

7. Disaster Recovery Copy of Archived Business Records

Data flow: OpenText InfoArchive to SFTP

Organizations can periodically export archived records from OpenText InfoArchive to an SFTP location at a secondary site or managed backup repository. This creates an additional protected copy of long-term records for disaster recovery and business continuity planning.

• Improves resilience for critical retained records
• Supports continuity requirements for regulated data
• Provides an encrypted transfer path for backup operations

8. Automated Retention and Disposition Workflow for Incoming Files

Data flow: SFTP to OpenText InfoArchive

Files received through SFTP can be automatically classified in OpenText InfoArchive with retention rules based on file type, source, business unit, or metadata. At the end of the retention period, disposition can be executed according to policy, reducing manual review and storage overhead.

• Standardizes retention enforcement across departments
• Reduces compliance risk from over-retention
• Improves operational efficiency through automation