
A renewal quote arrived with a small uplift, a three-year term and a discount that expires at quarter end. Fourteen days to sign. The committee rehearsed whether the uplift was fair. The question that mattered was what the same platform costs in 2029 if the licence metric changes, the connectors move to a separate SKU, and nobody has ever run the export. The quote looked small. That was the problem. Everything below is dated November 2026.
What changed
30 September 2026. FileNet 5.5.x, GA 26 June 2018, left End of Usage Support; Extended Support ends 30 September 2030. Renewing 5.5.x renews an unsupported system.
1 July 2025. The Law on Archives 2024 took effect; Decree 113/2025, dated 21 July 2025, allows 24 months to build or upgrade a digital archive system, 36 for the state archive database, 60 for redundant infrastructure.
1 July 2025. Circular 05/2025/TT-BNV fixed the archive data structure and the eight-step digitisation process. No platform ships it; replacing means building it twice.
1 January 2026. Law 91/2025 with Decree 356/2025 — data-subject requests in two working days, cross-border transfer sanctioned up to 5% of prior-year revenue. "Delete one person's records" is now a contract clause.
1 July 2026. Decree 337/2025 set the bar for electronic signatures in employment contracts: identity at signing, trusted timestamps, tamper-evident audit log. Expect the same bar at an archive inspection.
December 2025. OpenText's Content Manager 25.4 became the LTS release, supported to 30 November 2028; non-LTS windows lasted about three months — 25.1 ended 28 February 2026, 25.3 on 31 August 2026.
The metric moved too: consumption on top of seats — Laserfiche AI Units, M-Files Aino capacity, SharePoint Premium near USD 0.05 per page.
The decision framework
Five questions, in the order I would put them in writing. The weights are mine, tuned for a lender mid-core-replacement.
| # | Question | Weight | What "high" looks like |
|---|---|---|---|
| 1 | Usage — what are we buying? | 20% | Named user defined in the contract, the metering metric, consumption against entitlement, true-down rights |
| 2 | Egress — what does data out cost? | 20% | Export, API calls and page events priced in the contract, not a rate card the vendor can revise |
| 3 | Connectors — what is in the licence? | 15% | Every live interface named with a support status; nothing that exists only in a services SOW |
| 4 | Migration — what must be rebuilt? | 25% | The vendor names in writing what will not migrate; you count the exceptions yourself |
| 5 | Exit — what can we prove? | 20% | Content, metadata and audit log export in an open format, tested and minuted annually |
Two are pass/fail: a written named-user definition, and an export that has been executed and minuted. Price mechanics — escalation cap, price hold, re-compete right — wrap whatever the five answers produce.
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 |
|---|---|---|---|
| Renew 3–5 years with caps and a dated upgrade | Cheapest five-year cash, near-zero migration, upgrade covered by Essentials at the same price point | Locks an unpublished pricing basis; if escalation is under-estimated you learn in year four | 0.73L, then 1.10L and 1.05L — about 2.88L |
| Bridge 12 months, then re-compete | Keeps optionality, forces comparison, no five-year bet on an unpublished metric | Uplift risk moves into next year; two procurements; a year comparing, not upgrading | 1.0L, then the 2.88L or 6.35L curve |
| Replace now | Removes the incumbent's pricing leverage | 3.50L in year one, dual-run, ten classes of evidence to reproduce, inside the core window | 3.50L, 1.50L, 1.35L — about 6.35L; 9.05L over five years |
A bridge is honest only if the re-compete is funded. Otherwise it is a three-year renewal delayed by one.
The numbers
Normalised to L, current annual licence and support, so conclusions hold when L is real; probabilities and damages are subjective estimates.
| Scenario | Five-year cash | Risk event | Damage | Expected cost |
|---|---|---|---|---|
| Keep and upgrade | 4.98 L | 5% | 1.5 L | 5.06 L |
| Replace with a peer ECM | 9.05 L | 25% | 1.5 L | 9.43 L |
| Microsoft 365 | 4.05 L | 20% | 2.0 L | 4.45 L |
| Do not upgrade | 5.20 L | 40% | 2.5 L | 6.20 L |
Replacement is about 1.82 times the upgrade path before risk, 1.86 times after. Microsoft is 0.81 times in cash with the largest damage estimate, its exposure being regulatory. The expected-cost gap between keeping and Microsoft is roughly 12% — that is where the argument lives.
What the quote will not show:
- Implementation and services at 50–150% of the year-one licence (CostBench, OpenText example; one cited case near USD 2.4 million over three years).
- Dual-run of 6–12 months with both systems licensed, then 12–18 months of hypercare.
- Ten classes of evidence to rebuild: checksums, classification, metadata, versions, retention, legal hold, entitlements, audit trail, signatures, deep links.
- Exception handling, priced per record. Double-digit rates in a large financial record store mean hundreds of thousands to millions of manual records — an estimate, and the exclusion in migration contracts.
- Public anchors: M-Files USD 65 per seat per month, Laserfiche USD 73 and 93 by tier, SharePoint Premium about USD 0.05, 0.10 and 0.15. IBM, OpenText and Hyland publish nothing.
The one page the board needs
| Line | The number |
|---|---|
| Destination release and date | 5.7 in six months, Cortex in 12–18 |
| Users, documents, interfaces, cost each | From the baseline, not the vendor |
| Last successful export test | Dated and minuted |
| Alternative, same scope, five years | 9.05L against 4.98L |
| Re-decision trigger | No quote in 60 days, uplift above 25% a year |
What I would do in 30 / 60 / 90 days
Days 1–30. Take ECM out of the replacement programme's scope in writing. Baseline: users, documents, live interfaces, annual cost, three years of incidents. Inventory the ten evidence classes and rate their difficulty.
Days 31–60. Send one quote template to the incumbent and two alternatives: five years, six cost lines, same scope. Run three demos on your data — extract one customer's full record in two working days, place and release a legal hold, export three years of audit trail. Minute pass or fail.
Days 61–90. Rebuild the TCO with real inputs and run the sensitivity. Take it to architecture, compliance, legal and internal audit before the board. Negotiate three to five years with an escalation cap, a price hold, an annually tested export clause. Sign, with upgrade dates in the minutes.
What I would not do
- I would not sign before an export test has been run and written down. An untested exit clause is a sentence, not a right.
- I would not accept "per user" without a definition. Named or concurrent, human or robot — the definition is the price.
- I would not let a discount decide the term. An uplift argument is noise beside a five-year bet on an unpublished metric.
- I would not replace the repository in the core-banking window. Two moving variables in one release destroys attribution.
For the non-technical sponsor
The renewal quote is the smallest number in this decision. The larger costs are finding and moving records the bank must keep, running two systems during the switch, and proving to an auditor that nothing was lost. Five questions — usage, egress, connectors, migration, exit — decide whether the three-year price is a price or an opening position.
Sources
- IBM, FileNet Content Manager 5.5.x lifecycle
- IBM, What's new in Content Cortex 26.0.0
- ISR, IBM Content Cortex for existing FileNet customers
- CostBench, OpenText Content Suite cost calculator
- M-Files, pricing
- Laserfiche, pricing
- Decree 113/2025/ND-CP
- Circular 05/2025/TT-BNV
- Law 91/2025/QH15 with Decree 356/2025
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.




