Every Kofax End-of-Support Date, On One Page
Tungsten Automation publishes these dates in a lifecycle PDF most Kofax admins have never opened. If your invoices, claims, or remittances flow through Kofax Capture or KTM today, this timeline is your timeline.
Map my exposure, free sessionJump to the dates
Sound familiar?
“Our Kofax version is ancient, and the one person who knew it left two years ago.”
“The vendor keeps saying ‘Move Up to TotalAgility,’ but nobody can tell me what it costs us.”
“Quarter-end volume breaks the process every time, and now they’re telling me support ends too?”
You’re not behind because you missed a memo. No official web page lists these dates. The answer lives in the Tungsten Software Lifecycle Policy (v12), a PDF that changes without announcement. We maintain this page from that policy, the Tungsten sunset schedule, and partner-community updates, so you don’t have to.
The dates that decide your 2026–27
- 2018–2021: already passed
Kofax Capture 10.x and 11.0 end of support. If you’re on these versions, you’ve been unsupported for years. Every audit and OS upgrade is a risk event. - 2022 / 2024: already passed
Kofax RPA 10.2 and 10.3 end of support. Robots keep running quietly, until a target app changes and there’s no supported way to fix them. - March 3, 2026: already in effect
Kofax Capture 11.1 enters Limited Support. Critical defects only, fixed at the vendor’s discretion. No compatibility updates for new Windows, SQL, or browser versions. - May 9, 2026: already in effect
KTM 7.1 enters Limited Support. Your extraction and classification layer is now on the same reduced footing as Capture. - August 2026: you are here
Enough time to run a proper migration if you scope now. Not enough if you start in Q1 2027. - March 3, 2027
Kofax Capture 11.1 End of Support. No patches, no security fixes, no vendor escalation. Ever. - May 9, 2027
KTM 7.1 End of Support. Capture and KTM migrate together or not at all. This date seals both. - March 2028
Kofax Import Connector 2.11 End of Support. Don’t let the later date lull you: KIC exists to feed Capture, and Capture goes first.
Not sure which version you’re on? Open Batch Manager and check Help → About Kofax Capture. The first two digits decide which of these dates is yours.
→ Limited Support now · End of Support March 3, 2027
Kofax Capture 10.2.0.514
→ unsupported since 2018
“Limited Support” means less than you think
Since March 3, 2026, Capture 11.1 gets: critical defects only, at the vendor’s discretion. No non-critical patches, so a broken export connector that doesn’t crash the product is your problem. No compatibility certifications for new Windows Server, SQL Server, or browser releases. No feature changes of any kind.
And there is no Capture 12 coming. Tungsten has marked Capture and KTM as Discontinued in its catalog and runs a formal “Move Up to TotalAgility” incentive program. Vendors run migration incentives for products they intend to retire, not products they intend to revive.
no capture 12 is coming. this is the end of the line, not a gap between versions.
Not sure which dates apply to your stack?
60 minutes, free. We map your Capture/KTM footprint against these dates and put the recommendation in writing, even if it’s “wait.”
What to do, based on where you are today
| Your version | Your reality | Urgency | Your move |
|---|---|---|---|
| Capture 11.1 | Limited Support now; End of Support March 2027. The most room, and the most reason not to waste it. | Decide in 2026 | Inventory batch classes, scripts, and integrations now. Get Move Up terms in writing. Decide with data, not under deadline pressure. |
| Capture 11.0 / 10.x | Unsupported for 4–7+ years, often on unsupported Windows Server too. | Active risk | Skip the 11.1 detour. It buys 12 months at the cost of a real project. Point the same effort at your destination platform. Current-year project. |
| KTM 7.1 | EOS May 2027, two months behind Capture. KTM is where the real migration effort and the biggest gains live. | Scope first | Scope KTM before Capture; it drives the whole timeline. Modern trainable extraction typically replaces years of hand-tuned locators. |
| Kofax RPA 10.2 / 10.3 | Both already past End of Support (2022 / 2024). | Unsupported | Audit which robots still run on these versions. Upgrade or fold them into your platform decision. |
Fewer manual errors after rebuilding an aging capture stack
A financial services back office ran high-volume customer documents through an aging capture setup: heavy manual indexing, constant correction. Rebuilding the extraction layer on modern trainable document intelligence, instead of porting old zone-and-locator rules, cut manual errors by 98% and returned 100+ hours a month to the team. The compliance team cared about the error number, not the speed.
One of roughly 20 delivered automation case studies. Typical results across projects: $50–70k annual savings, 6–12 month payback.
Your next 90 days, in four moves
- Inventory the estate. Batch classes, KTM projects, custom scripts, export connectors, downstream integrations. The script inventory is the single best pre-migration investment.
- Get Move Up terms in writing. The incentive is real but negotiated per account and changes over time. Never plan against a verbal number.
- Pick your path with data. Upgrade, Move Up, leave, or a documented wait: each is right for someone. Deciding late is the only universally wrong answer.
- Set the date. A medium deployment should be scoping by mid-2026 to land before March 2027. Write the decision down with a date attached.
The migration window is your one chance to make 20 years of documents AI-ready.
Every document that passes through the new pipeline comes out structured and searchable. Teams that treat migration as a lift-and-shift pay for the project twice.
Questions everyone asks
When exactly does Kofax Capture 11.1 lose support?
It entered Limited Support on March 3, 2026. That already happened. Full End of Support is March 3, 2027. After that: no patches, no security fixes, no vendor support of any kind.
Will there be a Kofax Capture 12?
No. Tungsten has marked Capture and KTM as Discontinued and runs a formal Move Up incentive to TotalAgility. The 11.1 and 7.1 dates are the end of the product line, not a gap between versions.
Did the Kofax-to-Tungsten rebrand change my support contract?
No. The January 2024 rebrand carried contracts, entitlements, and lifecycles over unchanged. Your dates are exactly what the lifecycle policy says.
Can we just keep running Capture after March 2027?
The software won’t stop on March 4, 2027. What stops is any path to fix it: no security patches, no compatibility fixes, no escalation when a batch stops exporting. For a system handling invoices, claims, or customer documents, most compliance and security teams treat that as an unacceptable standing risk, and migration effort grows every year the environment drifts.
Is there ever a good reason NOT to migrate yet?
Honestly, yes. If the process Capture serves is being retired within 12–18 months; if a larger ERP/ECM program will absorb capture anyway; or if your 11.1 footprint is small, isolated, and stable through March 2027. The mistake isn’t waiting. It’s waiting without a written decision and a date. If none of those apply, 2026 is your planning horizon.
Does KIC’s 2028 date buy us time?
No. Kofax Import Connector 2.11 runs to March 2028, but it exists to feed Capture, and Capture loses support in March 2027. An import layer with nothing supported behind it isn’t a plan.
Automation work like yours, delivered
Real engagements from the portfolio: same platforms, same problems.
Get your exposure map before the dates decide for you
Free 60-minute Tungsten Migration & AI Readiness Session. You leave with a written recommendation (upgrade, Move Up, leave, or wait) with the reasoning attached. No pitch, no proposal unless you ask.