Kofax Capture Support Ends March 2027: What Actually Happens to You?
Short answer: your batches keep running on March 4, 2027. What stops is everything that keeps them safe to run. Kofax Capture 11.1 entered Limited Support on March 3, 2026, and reaches End of Support on March 3, 2027. KTM 7.1 follows on May 9, 2027, and Kofax Import Connector 2.11 in March 2028. There is no Capture 12 coming; Capture and KTM are marked Discontinued. That leaves you four real options: get current within Capture, take Tungsten’s Move Up path to TotalAgility, leave for a modern IDP platform, or wait with your eyes open. Here’s what each one actually means, and a 90-day plan to pick one.
The dates, in order
If you’re on anything older than 11.1 (and plenty of estates still run 9.x and 10.x), you’re already past your version’s dates. The 2027 deadline is for the people who kept current.
What Limited Support means in practice
Right now, in Limited Support, you can still open tickets and download existing fixes. What you’ve lost is the future tense: no new fix packs, no new patches for freshly discovered issues, and no certification against new environments. When the next Windows update, browser change, or security mandate collides with your capture stack, the answer is a workaround, not a fix. After End of Support in March 2027, the ticket queue closes too. These are real questions from the Tungsten community, and they show what that erosion feels like from the inside.
“When I upgrade to Kofax Capture 11, can we still use 10.2 until I get everyone across?”
“Is there a plan to update the email export connector to support TLS? Currently it only supports Exchange or SMTP without TLS.”
“Would it be possible to advise where I can download the VRS 5.3 software from, please?”
Notice what those have in common. Nobody’s asking about digital transformation. They’re asking whether the thing they run today will still be there tomorrow: coexistence during upgrades, aging components blocking security compliance, and installers that got harder to find after the rebrand. That’s what end of support looks like before the date arrives.
What breaks first
Not the software. Capture is stable, that’s why you still run it. The first breakage is environmental, and it usually arrives in this order:
- Security compliance. A connector without TLS support, an old protocol, a component your CISO’s scanner flags. The finding lands before anything technically fails, and “vendor won’t patch it” is not an answer auditors accept.
- The environment moves. A Windows patch, an Exchange change that breaks email import, a scanner driver that no longer ships. Capture was never tested against any of it, and nobody’s going to test it now.
- People and parts. The admin who built your batch classes retires. The installer you need lives behind a support login. The expertise market for a discontinued product shrinks every quarter.
Check where you stand: your exact version’s dates live on the Tungsten Automation support portal’s product lifecycle pages (some legacy Kofax articles are still hosted on partner knowledge bases, which adds to the confusion). Two minutes: open Capture Administration, note your exact version under Help, then match it against the lifecycle table. If it says anything below 11.1, your dates already passed.
Your four real options
1. Get current within Capture
- If you’re on 9.x or 10.x, upgrade to 11.1. You get a supported footing and a cleaner starting point for whatever comes next.
- But 11.1’s own clock runs out March 3, 2027, and there’s no 12 behind it. This is a bridge, not a destination.
- Effort: a version upgrade project, familiar territory for your team.
2. Move Up to TotalAgility
- Tungsten’s own successor path, with a formal “Move Up” incentive program and converter tooling for Capture and KTM assets.
- You stay with your vendor, keep your relationship and your entitlements conversation in one place, and carry your extraction investment forward with rework where scripts run deep.
- It’s a genuine replatform onto a process platform. Budget for services, retraining, revalidation, and parallel running. The incentive terms are negotiated per account, so get them in writing.
3. Leave for a modern IDP platform
- Replace the capture stack with a modern intelligent document processing platform outside the Tungsten ecosystem.
- Nothing converts. Batch classes, extraction logic, and integrations are rebuilt from requirements. That’s a cost, and sometimes it’s also the point: you rebuild only what still earns its place.
- Right when your platform strategy has already shifted, when your Capture footprint is small, or when the estate needs rethinking anyway.
4. The documented wait
- Keep running past end of support, deliberately. It happens more than anyone admits, and done honestly it’s a risk decision, not an accident.
- Honest means: a written risk acceptance signed by whoever owns the risk, the system isolated and its environment frozen, installers and license files archived while you can still get them, and a funded migration with a date on it.
- What it never means: drifting past March 2027 because no one decided anything.
there’s no Capture 12 to wait for. 11.1 is the end of the line, so “we’ll upgrade when the next version ships” stopped being a plan
Your next 90 days
- Days 1 to 30: know what you have. Confirm your exact Capture, KTM, and connector versions against the lifecycle dates. Inventory batch classes (and which ones actually ran this year), KTM projects, custom scripts, and every import and export connection. Download and archive installers, service packs, and license files while your support login still works.
- Days 31 to 60: price the paths. Take your inventory to the market. Ask Tungsten (or a partner) what Move Up means for your account, and get the incentive terms in writing. Ask an independent partner to size both the Move Up path and the leave path against the same inventory, so you’re comparing real numbers, not brochures.
- Days 61 to 90: decide and calendar it. Write the decision memo: chosen path, budget, owner, and dates. Work backwards from March 3, 2027 and book the migration, parallel-run, and validation windows now. If the honest answer is a documented wait, write the risk acceptance and put the end date in it.
Why hear this from us
We deliver both paths, Move Up to TotalAgility and migrations off it, so we’ve got no reason to skew the comparison. On our delivered TotalAgility IDP projects, clients cut manual document errors by 98%, saved $50-70k a year, and got 100+ hours a month back, with payback in six to twelve months. That’s from roughly twenty automation case studies, not a slide. When staying put (briefly, in writing) is the right call, we’ll say that too.
Frequently asked questions
Will our batches stop working on March 3, 2027?
No. Nothing switches off. Capture keeps processing the day after exactly as it did the day before. What ends is vendor support: no fixes, no patches, no help when something in the environment changes. The risk isn’t a stoppage on the date, it’s that every month after it, the odds of an unfixable incident go up and your options get more expensive.
What’s the difference between Limited Support and End of Support?
In Limited Support (where Capture 11.1 has been since March 3, 2026) you can still open tickets and download existing fixes, but no new fixes get built and no new environments get certified. At End of Support (March 3, 2027) the support relationship ends entirely. Practically: you’re already living with most of the downside, you just still have someone to call.
Can we run two Capture versions side by side during an upgrade?
Phased rollouts are the normal pattern, and coexistence questions (“can we still use 10.2 until everyone’s on 11?”) are among the most asked in the Tungsten community. Plan the parallel period deliberately: pin the versions, freeze the environment around the old one, and set an end date. The same logic applies at larger scale if you move to TotalAgility, where running Capture and TotalAgility in parallel during the transition is standard practice.
When does Kofax Import Connector reach end of support?
KIC 2.11 reaches End of Support in March 2028, a year behind Capture itself. Don’t let that lull you: the connector is only useful attached to a supported Capture, and email ingestion is one of the components most exposed to environmental change (Exchange updates, TLS requirements). Treat the Capture date as the real deadline for the whole stack.
Is a Kofax Capture 12 coming?
No. Capture and KTM are marked Discontinued in Tungsten’s lifecycle, and 11.1 is the final version. Tungsten’s forward path for this product family is TotalAgility, backed by the formal Move Up program. Any plan built on “wait for the next Capture release” needs rewriting, because there isn’t one.
We have KTM. Do the same dates apply? And what’s KTT?
KTM 7.1 has its own dates: Limited Support since May 9, 2026, End of Support May 9, 2027, two months after Capture. The KTM-versus-KTT naming confusion comes up constantly: KTM (Transformation Modules) is the packaged extraction add-on that runs inside your Capture batch classes; KTT (Transformation Toolkit) is older toolkit branding. If your extraction projects live in Capture batch classes, you’re on KTM and the May 2027 date is yours.
Where do we get installers and fixes now that Kofax is Tungsten?
Through the Tungsten Automation support portal, with a valid support login. The rebrand scattered older knowledge-base articles and download links, which is why “where can I download VRS?” style questions fill the community forum. The practical move: while your entitlement is active, download and archive every installer, service pack, and license file you might ever need. Future you, running a documented wait or a slow migration, will be grateful.
What does the Move Up to TotalAgility program actually give us?
It’s Tungsten’s formal incentive program for Capture and KTM customers moving to TotalAgility. The terms (credits, transition licensing, conditions) are negotiated per account rather than published, so treat any specific figure you hear as an opening position and get your offer in writing, including its expiry. Remember it addresses licensing, not the services side: migration work, script rebuild, revalidation, and retraining are budgeted separately whoever does them.
Want the 90-day plan filled in with your estate’s specifics?
Book a Tungsten Migration & AI Readiness Session. We check your versions against the lifecycle dates, inventory your batch classes, KTM projects, scripts, and connectors, and hand you a sized comparison of all four options. We deliver Move Up and move-out migrations alike, so you get the honest version. No pitch.