Home | Connectors | SharePoint | SharePoint - OpenText Content Storage Service Integration and Automation

SharePoint - OpenText Content Storage Service Integration and Automation

Integrate SharePoint Cloud Storage and OpenText Content Storage Service Cloud Storage apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between SharePoint and OpenText Content Storage Service

SharePoint and OpenText Content Storage Service complement each other well in enterprise environments where collaboration, governance, and scalable cloud storage must work together. SharePoint serves as the user-facing collaboration and document management layer, while OpenText Content Storage Service provides durable, compliant object storage for large volumes of content and long-term retention.

1. Archive completed SharePoint project sites to scalable OpenText storage

When a project ends, documents, meeting records, and final deliverables can be moved from active SharePoint team sites into OpenText Content Storage Service for long-term retention. This reduces SharePoint storage growth, improves site performance, and supports records management policies.

  • Direction: SharePoint to OpenText Content Storage Service
  • Business value: Lowers storage costs and keeps active collaboration spaces clean
  • Typical users: PMO, legal, records management, IT

2. Store large binary files from SharePoint in OpenText while keeping metadata in SharePoint

Organizations can keep document metadata, approvals, and collaboration workflows in SharePoint while storing large files such as videos, engineering drawings, scans, or marketing assets in OpenText Content Storage Service. SharePoint remains the front-end for users, while OpenText handles the heavy storage workload.

  • Direction: SharePoint to OpenText Content Storage Service
  • Business value: Improves performance for large file libraries and reduces SharePoint storage pressure
  • Typical users: Engineering, marketing, operations, document control

3. Use OpenText as the retention repository for regulated SharePoint content

For content subject to compliance requirements, final versions of policies, contracts, audit evidence, and HR records can be stored in OpenText Content Storage Service as the system of record for retention. SharePoint can manage working drafts and approvals, then pass approved content to OpenText for immutable or policy-driven storage.

  • Direction: SharePoint to OpenText Content Storage Service
  • Business value: Strengthens compliance, retention, and audit readiness
  • Typical users: Compliance, HR, legal, internal audit

4. Enable SharePoint document workflows with OpenText-backed storage for final outputs

Business processes such as contract review, policy approval, or supplier onboarding can be managed in SharePoint using lists, forms, and Power Automate. Once a document is approved, the final version can be written to OpenText Content Storage Service for secure long-term storage, while SharePoint retains the workflow history and collaboration trail.

  • Direction: SharePoint to OpenText Content Storage Service
  • Business value: Separates active workflow content from finalized records
  • Typical users: Procurement, legal, finance, shared services

5. Centralize enterprise content access across SharePoint and OpenText repositories

Organizations with multiple departments using SharePoint can connect those sites to content stored in OpenText Content Storage Service so users can search, reference, and retrieve documents without needing to know where the content is physically stored. This creates a more unified content experience across business units.

  • Direction: Bi-directional access and retrieval
  • Business value: Reduces content silos and improves employee productivity
  • Typical users: Knowledge workers, service desks, operations teams

6. Support cloud migration from legacy file shares into SharePoint with OpenText as the back-end archive

During migration from file shares or older document repositories, active documents can be moved into SharePoint for collaboration, while inactive or historical content is migrated into OpenText Content Storage Service for cost-effective cloud retention. This allows organizations to modernize without forcing all content into the same operational layer.

  • Direction: Legacy sources to SharePoint and OpenText Content Storage Service
  • Business value: Enables phased migration and reduces risk during transformation programs
  • Typical users: IT, records management, business application owners

7. Preserve SharePoint-generated business records in OpenText for long-term governance

SharePoint workflows often generate records such as approvals, project sign-offs, policy acknowledgements, and committee decisions. These records can be automatically transferred to OpenText Content Storage Service to ensure durable storage, lifecycle management, and retention enforcement beyond the active life of the SharePoint site.

  • Direction: SharePoint to OpenText Content Storage Service
  • Business value: Improves records governance and reduces risk of accidental deletion
  • Typical users: Governance teams, compliance officers, business administrators

8. Retrieve archived content from OpenText into SharePoint for audits, reviews, or rework

When teams need to revisit archived contracts, project files, or policy documents, SharePoint can act as the access point to retrieve content from OpenText Content Storage Service back into an active workspace. This supports audit requests, legal review, and document reactivation without permanently restoring everything to SharePoint.

  • Direction: OpenText Content Storage Service to SharePoint
  • Business value: Speeds up audit response and controlled content reactivation
  • Typical users: Legal, audit, compliance, project teams

How to integrate and automate SharePoint with OpenText Content Storage Service using OneTeg?