Implementation services
OpenText Content Manager Upgrades
Avoid additional fees associated with older versions
Access the latest security updates and product fixes
Maintain vendor support and technology compatibility
Upgrade planning tailored to your environment
Testing and validation before deployment
Knowledge transfer and technical training
Support before, during and after go-live
Upgrade Content Manager with confidence
Assess your environment
We review your Content Manager version, infrastructure, integrations and customisations to identify dependencies and establish the right upgrade path.
Minimise disruption
A carefully planned and phased approach helps reduce downtime and allows upgrade activities to be coordinated around your operational needs.
Validate before go-live
Testing confirms that Content Manager, connected systems and critical business processes operate as expected before the upgraded environment moves into production.
Improve system performance
Gain access to current product enhancements and supported technologies that can improve system performance, stability and the user experience.
Prepare your team
Knowledge transfer and technical training help your administrators understand the upgraded environment and manage it confidently following handover.
Support a smooth transition
Post-upgrade support helps resolve issues quickly, minimise operational risk and ensure a smooth transition to your upgraded Content Manager environment.
Frequently Asked Questions
Why should we upgrade OpenText Content Manager?
Upgrading Content Manager gives your organisation access to current security updates, product fixes, enhancements and supported technologies. It can also help you avoid additional fees associated with remaining on an older version.
Does OpenText charge additional fees for older Content Manager versions?
Older versions of Content Manager may move into an extended support period that attracts additional OpenText fees. Upgrading to a current version can help your organisation avoid these additional costs while maintaining access to current product support and security updates.
How do we know when Content Manager needs to be upgraded?
An upgrade may be needed when your version is approaching the end of standard support, attracting additional support fees, presenting security concerns or becoming incompatible with connected technologies. FYB can assess your environment and recommend an appropriate upgrade path.
What is involved in a Content Manager upgrade?
A typical upgrade includes discovery, technical assessment, planning, environment preparation, installation, configuration, testing, production deployment and post-upgrade support. The exact process depends on your current version, infrastructure, integrations and business requirements.
How long does a Content Manager upgrade take?
The timeframe depends on the versions involved and the complexity of your infrastructure, integrations and customisations. Following an initial assessment, FYB can provide an upgrade plan and expected timeframe based on your environment.
Will Content Manager be unavailable during the upgrade?
Some downtime will be required when the upgraded environment moves into production. FYB uses a planned, phased approach and coordinates deployment around your operational requirements to minimise disruption wherever possible.
What happens to our existing records during an upgrade?
Existing records, metadata and configurations are protected through a controlled upgrade process. Testing is completed before production deployment to confirm that information remains accessible and critical processes continue to operate as expected.
Can FYB test integrations and add-ins during the upgrade?
Yes. FYB can assess and test integrations, add-ins and other Content Manager dependencies to identify compatibility issues before the upgraded environment goes live.
Does FYB provide support after the upgrade?
Yes. FYB can provide post-production support to resolve technical issues, minimise operational risk and support a smooth handover to your internal team.
