SharePoint sprawl is not solved by adopting more SharePoint. Most enterprises that have lived through a Microsoft 365 Copilot rollout already know this: the permissions model surfaces content the records team never intended to expose, the system of record is impossible to identify, and the audit trail does not survive a regulator's sample. BCS implements OpenText Content Hub (Core Content Management) as the cloud-native system of record while keeping Microsoft Teams and SharePoint as the active collaboration surface. The migration is selective, not big-bang.
Contracts, signed records, regulated documents migrate. Active team sites and project collaboration stay on SharePoint with Teams co-authoring writing back to the governed estate.
Microsoft 365 Copilot surfaces content the user is permitted to see, including content the records team did not intend to expose. The permissions audit catches the gap before users see it.
The regulator's question — "where is the latest signed version" — has one answer. Retention, audit trail, and disposition policy run on the governed estate, not on the collaboration surface.
Content Hub is OpenText's cloud-native answer to the SharePoint-as-system-of-record problem. The product layers are straightforward; the implementation decisions are not. BCS designs around the four decisions that decide whether the platform earns its place in production.
Content Hub is positioned not as a SharePoint replacement but as a system-of-record companion. The collaboration surface stays where the business already lives — Teams chat, Outlook attachments, OneDrive sync — and the governed record consolidates on the Content Cloud.
The implementation question is not "will it integrate with Microsoft 365" — it ships Teams and Copilot bridges out of the box. The implementation question is which content categories qualify as records, what permission model survives Copilot exposure, and how Aviator AI activates without surfacing the gaps that Copilot already revealed.
The repository is multi-tenant SaaS. No infrastructure to size, no upgrade weekends. Storage and compute scale with the workspace volume. Integration to Microsoft 365 and the SAP estate ships with the subscription.
Aviator ships embedded in the Content Hub subscription. Conversational summarisation, semantic search, chart generation against the governed content. Permission-aware retrieval: users only see content they are authorised to access.
Teams reads Content Hub documents in chat and channel context. M365 Copilot can ground responses on Content Hub content alongside Microsoft 365 data. Co-authoring writes back to the governed record where the content qualifies for retention.
Lightweight records management embedded in the workspace. Retention policy per document class, disposition workflows, legal hold mechanics. Sufficient for most non-regulated and mid-regulated industries (Documentum remains the path for FDA 21 CFR Part 11 scope).
CIOs do not buy Content Hub to "consolidate ECM." Programmes get budget when one of four operational realities forces the decision.
An IT review or compliance review of the Copilot pilot revealed permissions gaps. Users searching legitimate questions returned content from finance, HR, or M&A spaces that should not have been accessible. The CIO needs a system of record with auditable permissions before Copilot expands.
The auditor flagged that SharePoint cannot serve as the system of record for regulated documents — the version history can be edited, the audit trail can be bypassed, and the retention policy is inconsistent across sites. The CIO has 6-9 months to put a defensible system in place.
The organisation has accumulated hundreds of SharePoint sites with no consistent taxonomy. Business users invent their own folder structures. Migrations from acquired entities pile up on top. The CIO needs a single system of record that surfaces "the latest signed version" reliably.
Post-merger integration has surfaced the content estate as a workstream. The acquired entity has its own SharePoint tenancy, its own retention practice, and its own user permissions. The CIO needs a destination estate that absorbs the acquired content without losing the audit trail.
Content Hub lands across every C-suite differently. Each accordion below names the specific lever the role inherits and the implementation decision that makes it land.
For the CIO, Content Hub answers the system-of-record question that SharePoint cannot. The Copilot rollout that exposed permissions gaps now has a governed destination, and the audit trail finally survives a regulator's sample.
For the CFO, audit findings on missing supporting documentation are recurring. Content Hub answers the audit question structurally: every signed record lands in the governed estate with retention policy applied at the workspace.
For the COO, the cost of fragmented content is operational friction. Teams search across SharePoint, network drives, and email for documents that should be one click away. Content Hub consolidates the system of record so operations runs against one source.
For the CTO, Content Hub removes the legacy on-premise ECM from the IT estate. Multi-tenant SaaS handles infrastructure, upgrades, and AI capability delivery. Integration to Microsoft 365, SAP, Salesforce, and ServiceNow ships supported.
For the CHRO, employee records are spread across HR systems, SharePoint, email archives, and personal drives. GDPR right-to-be-forgotten and statutory retention land as multi-system manual operations. Content Hub consolidates the employee record into one workspace per employee.
For Compliance, the records programme becomes operational rather than a permanent backlog. The Content Hub policy is one rule. Legal hold lands as a workspace flag. Disposition runs against policy with full audit trail.
For the CDO, Aviator and Copilot ground on Content Hub content semantically. The governed estate becomes the AI training ground for internal queries; hallucination risk drops because the AI reads governed records.
For Strategy, M&A integration carries an under-discussed content workstream. Acquired entities arrive with their own SharePoint estates. Content Hub absorbs the records-qualifying content; Information Archive retires the deprecated platforms.
Seven product components spanning the SaaS repository, conversational AI, Microsoft 365 integration, workspace patterns, records governance, and ERP/CRM connectors.
Multi-tenant SaaS content repository with workspace-based content organisation, document version history, and metadata-driven classification. Replaces the legacy on-premise Content Server and the SharePoint-as-record pattern.
Conversational AI grounded on the governed content store. Summarise documents, locate records by attribute, generate charts from content metadata, draft responses. Permission-aware retrieval ensures users only see content they are authorised to access.
Documents from a Content Hub workspace open in Microsoft Teams for collaboration. Teams chat references Content Hub content with permission inheritance. Co-authoring writes back to the governed record where the content qualifies for retention.
Microsoft 365 Copilot can ground responses on Content Hub content alongside Microsoft 365 data. The user gets one Copilot surface with answers from both the collaboration estate and the governed estate.
Auto-generated workspaces for projects, customers, contracts, vendors. Workspace templates carry metadata schema, document type catalogue, and access policies. Users do not configure workspaces; they are created and governed centrally.
Embedded records management with retention rules per document class, legal hold mechanics, disposition workflows, and audit trail. Sufficient for most non-regulated and mid-regulated industries; Documentum handles 21 CFR Part 11 scope.
Pre-built connectors for Salesforce customer records, SAP business objects, and ServiceNow case management. Content from Content Hub renders inside each system's native UI when configured.
A Content Hub programme typically runs 12 to 20 weeks depending on the scope of the SharePoint migration. BCS sequences six workstreams against the SaaS activation, the permissions audit, and the selective content migration.
SharePoint estate inventory: sites, document libraries, retention practice per business unit, permission inheritance map. Microsoft 365 Copilot exposure analysis surfaces which permissions need remediation before AI activation.
BCS owns: discovery tooling, permission map, Copilot exposure report. Client owns: records-team policy data, business-unit content owners, access to SharePoint admin.
SaaS tenant model decision (single vs multiple tenants based on data residency, M&A roadmap). Workspace templates designed against business object dimensions — project, customer, contract, vendor. Records policy harmonised across business units.
BCS owns: tenant architecture, workspace template catalogue, records policy harmonisation. Client owns: records committee sign-off, business owners validating templates.
Which SharePoint content qualifies as records (contracts, signed records, audit evidence) and migrates to Content Hub. Which content stays on SharePoint as active collaboration. The migration is selective; only records-qualifying content moves.
BCS owns: migration scope, qualification criteria, source-to-destination map. Client owns: records-qualifying content category sign-off.
Microsoft Teams integration configured with permission inheritance honouring Content Hub workspace permissions. Microsoft 365 Copilot bridge configured so Copilot grounds on the governed estate with correct permission honouring.
BCS owns: Teams integration, Copilot bridge configuration, permission propagation validation. Client owns: Microsoft 365 admin access, Copilot licensing.
Selective migration executes in waves. Anugal IGA extends identity governance over Content Hub workspace permissions, closing the access certification gap that core IGA tools do not reach. Symphony orchestrates the cutover with validation gates and rollback path.
BCS owns: migration execution, Anugal access policies, cutover orchestration. Client owns: sign-off on cutover validation criteria.
Aviator activated against the migrated Content Hub estate. Permissions audit runs to validate Aviator only surfaces content users are authorised to access. Hallucination test harness validates Aviator response quality. Adoption metrics track actual usage.
BCS owns: Aviator configuration, permissions audit, test harness. Client owns: business-user enablement, sign-off on audit findings.
BCS implements OpenText as part of the broader cloud and SAP programme practice. Content Hub programmes typically run alongside a Microsoft 365 governance review, a Copilot expansion, or an SAP migration — not as a stand-alone content modernisation.
The agentic system integrator model means three operating platforms travel with every Content Hub programme. Each one plays a specific role named below.
Identity governance over Content Hub workspace permissions and document-type access. Closes the certification gap SailPoint and SAP GRC leave between core identity directory and content surface — the gap that surfaced when Copilot exposed content.
Metadata validation that runs before migration. Inconsistent SharePoint metadata is normalised against the Content Hub schema so workspace classification and Aviator retrieval start accurate rather than requiring remediation in month four.
Migration orchestration for the selective SharePoint-to-Content-Hub waves. The cutover sequence, the validation gates per wave, and the rollback path execute as one workflow with sign-off checkpoints.
Three updates that shape the Content Hub implementation conversation in 2026.
Content Aviator 26.1 extends from conversational summarisation and semantic search into chart generation. Users ask Aviator to chart contract values by region, document volume by class, or compliance status trends; Aviator returns the chart inside the conversation surface.
Source: OpenText Content Aviator updatesOpenText positioned as a Leader in The Forrester Wave: AI-Powered Content Management Platforms. The recognition spans the broader Content Cloud including Content Hub, anchored on AI-grounded retrieval and SaaS-native governance.
Source: OpenText Forrester recognitionEnterprise Copilot pilots through 2025 surfaced permission exposure incidents that drove governance reviews. Content Hub procurement increasingly anchors on "we need a system of record that Copilot can ground on without the SharePoint exposure pattern."
Source: OpenText Core Content Management updatesEach surfaces in the first or second scoping session. The honest answer matters more than the marketing answer.
BCS runs a 30-minute readiness session covering the SharePoint estate state, the Microsoft 365 Copilot exposure surface, the records policy harmonisation gap, the selective migration scope, and the Aviator activation sequence.
30-minute discovery session*