Content Manager renewal management
Review your licensing requirements, check that the model fits and explore what your Content Manager investment could do next.
A conversation worth having
More attention to what your organisation needs.
Your people, systems and priorities change. The renewal is a chance to check whether your Content Manager licensing still fits the work it supports.
Review the requirement
Understand who needs CM, how they use it and what is changing. Check the existing licence schedule before assuming you need more.
Check the model
Look at commercial fit, entitlements and responsibilities. A useful comparison considers what each option includes, as well as its price.
Look ahead together
The renewal triggers a general check-in, a version review and a discussion of capabilities that could help your team.
That is the core of our renewal service. Upgrade delivery, support plans, training and SmartTool licences have their own scope and terms.
Still call it TRIM, HP TRIM or Micro Focus Content Manager? Start with the version and arrangement you have today.
Start with the requirement
Does your licensing still fit?
The right outcome may be to retain your current model with a clearer understanding of what it covers.
| What we review | What it helps clarify |
|---|---|
| People and tasks | The roles, access requirements and business processes CM needs to support. |
| Existing entitlements | Licence quantities, modules and counting definitions in your current written terms. |
| Changes ahead | The effect of growth, restructuring, new integrations or a change in how teams work. |
| A like-for-like offer | Software rights, maintenance, hosting, partner support, tools and project work, with inclusions and exclusions separated. |
Perpetual licenceCheck the rights already held and the maintenance arrangements.
SubscriptionCheck the term, covered use, renewal conditions and responsibilities.
Cloud managed serviceCheck the service scope, data arrangements and operational ownership.
These are broad purchase options described by OpenText. Availability and customer entitlements depend on the current written offer and agreement. A licensing model does not, by itself, settle every hosting decision.
Two decisions, clearly separated
A renewal is not an installation plan.
A renewal concerns your commercial arrangements. An upgrade changes the software or environment you run.
Renewing maintenance does not install a newer release or extend an older release's published lifecycle. Software upgrade entitlement and the work to assess, test and implement it are different things.
Explore what has changed in CMOpenText's upgrade services overview describes separately scoped delivery. The categories here are practical planning distinctions, not formal OpenText pricing categories.
Patch or hotfix
Investigate a specific issue. Confirm the eligible source build, supported installation route and regression tests before applying a fix.
Feature or major release change
Identify the useful capabilities, supported upgrade path, database changes, integration dependencies and impact on users.
Infrastructure modernisation
Check operating systems, database and client components. Agree testing, recovery and rollback responsibilities.
Hosting or deployment change
Review data location, access, recovery, service ownership and exit arrangements alongside the commercial model.
Licence, module or capacity change
Confirm the requirement and entitlement. A commercial change may also require configuration or technical implementation.
Value before change
What is right for your organisation?
Start with your support position, business needs, dependencies and a realistic testing window.
Retain the current arrangement
Confirm its fit, support position and limitations. Agree when the decision should be revisited.
Investigate a targeted update
Check a relevant fix when your current release otherwise meets the requirement.
Plan a release upgrade
Build the case around specific capabilities or support needs, with owners for testing and adoption.
Assess a wider improvement
Consider configuration, training, integration or hosting when the issue extends beyond the version number.
These are options to assess, not a recommendation for an unreviewed environment. Confirm the exact CM build and contracted support position before acting.
Bring the right questions
Make the check-in useful.
Bring one or two recurring frustrations as well as the renewal date. Difficult searches or repeated manual work may point to training or configuration rather than another licence.
-
Establish the current position
Review the arrangement, licence requirements and exact CM version.
-
Discuss what is changing
Include team changes, new processes and capabilities worth investigating.
-
Agree the next step
Separate the renewal decision from any work that needs its own scope, owner and quotation.
Explore before you decide
Put the opportunities in context.
Follow the topic that matters to your team. These are separate services and resources, not automatic renewal inclusions.
For release-specific detail, read our CM 26.2 article and CM 25 article, or consult the version history and maintenance reference.
Before your renewal
Your questions, answered.
A review should leave you clearer about what you have, what you need and what deserves a closer look.
Can you help if another provider handles our renewal?
Yes. We can discuss your requirements and available next steps. Any change of renewal arrangements must follow the relevant customer, vendor and reseller processes. An enquiry does not transfer your agreement.
Does renewal management include an upgrade or support plan?
The core focus is licensing requirements and model suitability, with a renewal check-in and a review of version and capability opportunities. Upgrade delivery, support plans, training and SmartTool licences have separate scope and terms. Your agreed quotation determines inclusions.
Will you always recommend a newer version or different model?
No. The right outcome may be to keep the current arrangement with a clearer understanding of its fit and limitations. We discuss useful change, not change for its own sake.
What should I send with an initial enquiry?
Start with your renewal date, CM version and the question you need to resolve. Do not send licence keys, confidential contracts or sensitive records through a general enquiry form.
Your next CM decision
Let's make your renewal worthwhile.
Bring your renewal date, current version and the priorities you want to discuss.