Skip to content
Global expertise. Practical outcomes.
Talk to an Expert ↗
TechTiera
Kofax Capture end of support: verify dates and plan the next step
AI & Intelligent Automation

Kofax Capture end of support: verify dates and plan the next step

Build a version-specific lifecycle plan for Capture and the connected products your document workflows rely on.

Short answer

Check the installed product and version against Tungsten Automation’s current Product Release and Sunset Schedules, then confirm your maintenance entitlement. Plan around the whole capture workflow, not just the Capture server. The Kofax-to-Tungsten rename is not evidence that every Capture release or connected product has the same support deadline.

Verified Kofax and Tungsten support dates

The vendor’s Product Release and Sunset Schedules dated November 11, 2026 lists the following version-specific milestones. Confirm your installed version and maintenance entitlement before making a production decision.

Selected Capture workflow components — vendor schedule issued November 11, 2026
Product and versionLimited support startsEnd of support
Capture 11.1March 3, 2026March 3, 2027
Capture 11.2No date assignedNo date assigned
Transformation Modules 7.1May 9, 2026May 9, 2027
Transformation Modules 2025.1March 11, 2028March 11, 2029
Import Connector 2.11March 4, 2027March 4, 2028
Import Connector 2025.1January 16, 2028January 16, 2029

No assigned date is the status of that release in this schedule, not a promise of indefinite support. The Capture 11.1 deadline does not mean that the entire Capture product line ends.

Source: Tungsten Automation’s November 11, 2026 release and sunset schedule, pages 3 and 11. For later revisions, use the vendor lifecycle policy and support dates article. Record the schedule’s issue date with your planning evidence.

Distinguish the rename from the release lifecycle

Tungsten’s release notes identify Capture 11.2.0 as Tungsten Capture and explain the former Kofax branding. That is evidence of a continuing product release; an old statement that the end of one version is the end of the entire Capture product line should not be reused.

The product name alone does not establish whether your deployed build is supported. Confirm version, patch level, enabled modules and entitlement. Review release notes and technical specifications for the exact target version before selecting an upgrade path.

Build a lifecycle timeline for the whole workflow

Maintain one planning record per product and version. Include Capture servers and workstations, transformation or extraction components, import services, scanning dependencies, analytics, export connectors and downstream integrations where they are part of your estate. Their deadlines and compatibility constraints may differ.

  • Record the installed version, deployment owner and current support arrangement.
  • Record the verified support milestones and the source schedule’s issue date.
  • Identify supported target releases and required operating-system or database changes.
  • Work backwards through assessment, licensing, test, recovery rehearsal and business acceptance.
  • Name the decision owner and escalation path if the plan cannot meet a confirmed deadline.

A versioned register is more useful than a single corporate-wide countdown. Review it when the vendor updates its schedule or your installed estate changes.

Assess the actual capture and export behavior

Inventory batch classes, document types, validation rules, recognition settings, scripts, service accounts and export destinations. Capture representative input samples, including difficult documents and exception cases. Document throughput requirements and the way users recover a failed or suspended batch.

An assessment should separate the product upgrade from changes to business rules or document models. Keeping those changes explicit makes it easier to explain differences in recognition, routing or export results during testing.

Choose and test an upgrade or replacement

Compare a supported Capture upgrade with a broader document-processing change using the same business requirements. A replacement may require redesign of capture logic, integrations and operating procedures; it should not be priced or scheduled as a simple version change.

Rehearse on a test environment. Compare document counts, extracted values, validation behavior, routing and exported records. Prove backups and recovery, agree the cutover handling of in-flight batches and obtain business acceptance before retiring the previous route.

Keep ownership clear after the change

Assign responsibility for monitoring, failed exports, credential rotation, patch testing and supplier escalation. Retain a documented dependency inventory and the evidence used to approve the release.

For implementation or upgrade scope, explore Tungsten Capture and Kofax Capture consulting. For a wider estate, review Tungsten Automation consulting and support. To compare a broader change, read the intelligent document processing guide.

Sources and further reading

Continue your research

Plan the next step

Connect this guide to the relevant service scope and related planning guidance.

How can we help?

Complete the form to contact our team.