OpenText Content Server upgrade and migration

Upgrade to a current, supported Content Server release, or migrate in from file shares and other repositories, with version history, metadata, permissions and Business Workspaces intact.

Plan your upgrade Start with a Health Check

Evidence: document counts, metadata, versions and permissions checked before and after.

Our method

How we move content safely

Inventory

Versions, modules, customisations, integrations, Archive Center and data volumes, checked against current support status.

Plan the path

Direct upgrade or staged route, with the test environment, timings and rollback agreed up front.

Rehearse

A full trial run on a copy of production, with counts and spot checks of documents, metadata and permissions.

Go live

A planned cut-over window, verification against the rehearsal, then support while users settle.

What we protect

The things that usually go wrong

Content

Version history and audit trails
Categories, attributes and classifications
Business Workspaces and their relationships

Access & rules

Permissions and group structures
Records holds and retention schedules
Links from SAP, Microsoft 365 and other systems

Checklist

Content Server upgrade checklist

The questions we answer before any Content Server upgrade or migration.

Which version and modules are you on, and what is their support status today?
Which customisations, workflows and WebReports must survive?
How many Business Workspaces, and which integrations create them?
Is Archive Center in scope, and where is storage held?

How are OTDS, Active Directory and permissions structured?
Which systems link in: SAP, Microsoft 365, Salesforce, Exstream?
What is the rollback plan, and how long is the cut-over window?
Who signs off, and against which counts and spot checks?

Support dates for Content Server releases change. We check your exact versions against OpenText's published support status during the inventory, rather than quoting dates here.

Next step