
Two things arrived in the same quarter for the person holding the renewal signature: the product was renamed, and the version in production left support. Neither changed a single document in the repository. Both changed the answer to a question nobody had asked — what exactly is being renewed: a repository, a brand, or a support contract that expired seven weeks ago?
What follows is dated November 2026.
What changed
28 April 2026. Gartner published the Magic Quadrant for Document Management 2026 — 16 vendors, six Leaders: Box, Doxis (ex-SER), Hyland, Laserfiche, M-Files, Microsoft. The Content Services Platforms quadrant is retired.
June 2026. IBM Content Cortex 26.0.0 reached GA. IBM's wording: "Content Cortex is IBM's next-generation content services system, and the successor to FileNet." It absorbs FileNet Content Manager, CMOD, Content Manager (CM8) and FileNet Image Services.
30 September 2026. FileNet Content Manager 5.5.x, GA 26 June 2018, left End of Usage Support. Extended Support completes 30 September 2030. FileNet 5.7.x, GA 20 June 2025, is the interim release IBM recommends.
September 2026. A paid Premium Edition went on sale. IBM partner ISR reports existing FileNet Content Manager and Cloud Pak licensees receive Essentials "at the same price point"; Premium adds LegalHold MCP, Redaction MCP, a Model Gateway and WDU Services.
March 2026. Hyland released Alfresco Content Services v26 — full support, deprecation March 2028, end of maintenance March 2029. Nuxeo LTS 2025 runs to 28 April 2028.
December 2025. OpenText made Content Manager 25.4 the LTS release, supported to 30 November 2028. Non-LTS windows ran about three months: 25.1 ended 28 February 2026, 25.2 31 May 2026, 25.3 31 August 2026.
The change with no clean date unsettles committees most. OpenText moved from Leader to Visionary, a year after Forrester's Q1 2025 Content Platforms Wave named it a Leader. Hyland and M-Files were promoted from Challengers. IBM lands last of 16 on both axes in secondary analysis of the reprint — a number to use internally, not to quote. OpenText also sold eDOCS to NetDocuments for approximately USD 160 million.
The decision framework
Seven criteria, weighted for a lender already replacing its core system. Write the weights down before the demo.
| # | Criterion | Weight | What "high" looks like |
|---|---|---|---|
| 1 | Evidence and audit capability | 20% | Retention per record class, tested legal-hold release, tamper-evident audit trail, ten-year signatures |
| 2 | Programme risk | 20% | No second replacement inside the core-banking window; dated milestones, named owner |
| 3 | Five-year TCO | 20% | Six lines costed: licence, implementation, infrastructure, migration, dual-run, retraining |
| 4 | Integration and business fit | 15% | Every live interface re-proven, including APIs that are themselves changing |
| 5 | Operational maturity | 10% | Three years of availability, P1/P2 counts, DR tests, runbooks |
| 6 | Roadmap and AI capability | 10% | Kubernetes 1.29+, OpenShift 4.16+, Helm 4.0+, MCP agent access, a dated release train |
| 7 | Vendor and lock-in risk | 5% | Annual export test, escalation cap, ownership changes counted |
Two are pass/fail: a supported release path with a date and an owner, and a full export — content, metadata, audit trail — that has actually run on your data.
Options and trade-offs
Costs are multiples of L, current annual licence and support — five-year model estimates, not quotes.
| Option | Strength | Risk | Three-year cost shape |
|---|---|---|---|
| Upgrade in place — 5.5.x → 5.7 → Cortex 26.x | ISR reports back-end, data model, database and interfaces unchanged, migration not required | Brand reads "legacy" while delivery does not; last of 16; renewal price unpublished; scarce skills | 0.73L, then 1.10L and 1.05L — about 2.88L, front-loaded |
| Move to a peer platform — Alfresco 26 or Nuxeo LTS 2025 | Open standards, CMIS endpoints, governance, rising analyst standing | ~20% of Hyland staff cut; Gartner-named packaging complexity; ten classes of evidence to reproduce | 3.50L, then 1.50L and 1.35L — about 6.35L, peak inside your core replacement |
| Consolidate on Microsoft 365 — SharePoint, Purview, Premium | Cheapest cash, usually already licensed, labels in Purview, Copilot | 1,000 retention labels per tenant, 13 policies for all sites, 100 sites per policy; shallow file plan | 1.85L, then 0.55L — about 2.95L, largest expected compliance damage |
There is no fourth option called "extend as we are". After 30 September 2026, 5.5.x is unsupported; a renewal that funds that state is a deferral with a signature.
The numbers
| Scenario | Five-year cash | Expected cost with risk |
|---|---|---|
| Keep and upgrade | 4.98 L | 5.06 L |
| Replace with a peer ECM | 9.05 L | 9.43 L |
| Microsoft 365 | 4.05 L | 4.45 L |
| Do not upgrade (reference) | 5.20 L | 6.20 L |
Replacement costs about 1.82 times the upgrade path over five years, more with risk priced: 25% probability of a major event at 1.5L damage, against 5% for the upgrade. Microsoft is cheaper in cash — 0.81 times — with the largest damage estimate, 2.0L at 20%, its exposure being regulatory.
- Implementation and services run 50–150% of the year-one licence on commercial ECM (CostBench, OpenText example). A quote below 50% has exclusions.
- Dual-run is 6–12 months, both systems licensed and operated. No vendor quotes that line.
- Hypercare for a new platform is 12–18 months, landing on the stressed half of a core programme.
- Migration scales with exceptions, not documents. Double-digit exception rates mean hundreds of thousands to millions of records by hand — an estimate, and the part migration contracts exclude.
- Public anchors: M-Files USD 65 per seat per month; Laserfiche USD 73, 93 and 42 by tier; SharePoint Premium about USD 0.05 per page prebuilt, 0.10 custom, 0.15 per document; Box near USD 36.5k a year by third-party estimate. IBM, OpenText and Hyland publish nothing: the incumbent's business case is a quote that has not arrived.
What I would do in 30 / 60 / 90 days
First 30 days. Put every content product's lifecycle on one page — version, GA, support end, owner — from vendor pages, not a slide. Baseline users, documents, live interfaces, annual cost, three years of incidents. Request a written Cortex upgrade quote.
Days 31–60. Run three scenarios on your data: extract one customer's full record within two working days; place and release a legal hold on a disputed set; export three years of audit trail for one document. Take two alternative quotes on one template, five years, six cost lines. Test the exception cases.
Days 61–90. Build the TCO in L, replace L with the real figure, run the sensitivity: compliance at 10%, TCO at 30%; if the ranking flips, it was political. Negotiate three to five years with an escalation cap, a price hold, an export right tested annually. Put upgrade dates in the minutes.
What I would not do
- I would not sign a renewal that names a price but not a destination release and a date.
- I would not let the quadrant decide, in either direction. It ranks cloud document management for the mass market, not survival under inspection.
- I would not buy Premium before a process owner names the LegalHold or Redaction dependency. Otherwise it is a subscription.
- I would not migrate the repository inside the core-banking window. Two moving variables in one release destroys attribution.
For the non-technical sponsor
FileNet has a new name and a new version; the old version stopped being supported on 30 September 2026. Staying is the cheapest and safest route, but only with a dated upgrade plan. Replacing costs roughly 1.8 times as much over five years and puts audit evidence at risk. The decision is a date, not a logo.
Sources
- IBM, What's new in Content Cortex 26.0.0
- IBM, FileNet Content Manager 5.5.x lifecycle
- IBM, FileNet evolves to Content Cortex
- ISR, IBM Content Cortex for existing FileNet customers
- Silicon.fr, secondary analysis of the 2026 Gartner MQ
- Hyland, Alfresco product support status
- Microsoft Learn, retention policy and label limits
Personal views. Client and employer details are anonymised. Figures are third-party estimates, not vendor quotes, and are dated November 2026.
Comments
Join the discussionNo comments yet. Be the first to comment.




