Kofax Capture support ends March 3, 2027

Stay in the Tungsten ecosystem or leave it. Two good answers, and everyone quoting you only sells one.

The vendor sells Move Up to TotalAgility. Replacement vendors sell the exit. We deliver Move Up projects and full platform exits, so the recommendation you get is the one that fits your estate. Even if that recommendation is “stay put and plan.”

⏳ 7 months until Capture 11.1 support ends. Transformation Modules follow in May 2027, Import Connector in March 2028

Plan my Move Up Plan my exit

If any of this sounds like your Monday, this page is for you

“We went looking for an installer after the rebrand and couldn’t even find the download page. If it’s this hard to get the software now, what does support look like after March 2027?”
IT Manager, shared services

“The vendor says Move Up to TotalAgility. Nobody can tell me what that actually costs, or what happens to fifteen years of batch classes when we do.”
Finance Operations Director

“Quarter-end volume breaks the process every single quarter. We staff around it like it’s weather.”
Shared Services Manager, manufacturing

Every page ranking for “Kofax Capture replacement” is written by a vendor selling the replacement. Every page about Move Up is written by the vendor selling Move Up. Nobody is paid to weigh both, except a partner who delivers both. We do Move Up migrations and platform exits. That’s the whole point of asking us.

The fork in the road: two paths, honestly compared

Stay: Move Up to TotalAgility

The right call when your extraction projects are deeply tuned, your team’s skills live in the Tungsten stack, and capture is the heart of processes you can’t afford to destabilize. There’s an official Move Up program behind it: training, migration tooling, and partner incentives designed to make staying the easy answer.

The reality nobody prices out loud: Move Up is not an upgrade installer. TotalAgility is a different platform, and your batch classes, transformation projects, custom scripts, and release setups get rebuilt on its model. Converter tooling handles the mechanical translation; the scripts and integrations are the real project.

Our proof: we rebuild these exact flows on TotalAgility’s intelligent document processing. In our delivered work that rebuild cut manual errors by 98% and returned 100+ staff hours a month. Staying is not settling, if the rebuild is done properly.
Leave: move to another IDP or capture platform

The right call when the license bill no longer matches your scan volume, your organization has a cloud-first or consolidation mandate, or capture is becoming one input to a wider automation program that already lives elsewhere.

The honest part: leaving means walking away from years of batch-class tuning, trained extraction projects, operator muscle memory, and every downstream integration wired to the old release setups. None of that copies across. Anyone quoting an exit without pricing that walk-away is quoting a demo, not your estate.

Our proof: we build document automation off the Tungsten stack too, with roughly 20 delivered automation case studies across deductions, remittance, and AP. The destination is home turf either way, which is why we don’t need you to pick one.

One thing both paths share: your migration is your one chance to make 20 years of documents AI-ready. In the flows we’ve rebuilt, moving extraction onto intelligent document processing instead of porting the old rules is exactly what produced the 98% error reduction and the returned hours. Skip that during the move and there won’t be a second budget to do it later.

either path rebuilds your batch classes. so pick the destination worth rebuilding for, not the path of least resistance

How to decide: the five questions we’ll ask you

Which products are you actually running? Capture, Transformation Modules, and Import Connector have three different end dates (March 2027, May 2027, March 2028), and the mix changes the answer. Most teams we talk to aren’t sure until we map it.
How deep is your transformation investment? Years of tuned extraction projects and custom scripts give Move Up a head start. Light, mostly out-of-the-box usage leaves the exit wide open.
What do your volumes do at quarter-end? If the process breaks under surge and you staff around it, that’s a rebuild argument on either path, and it belongs in the business case, not the risk register.
What does the license math say over the life of the path? Not this renewal. The full run: licenses, migration effort, and the cost of keeping unsupported components alive while you decide.
Where does document automation sit in your five-year plan? If capture feeds a wider AI and automation program, the destination platform matters more than what your team already knows.

You could answer these yourself with a few weeks of internal workshops. Or bring them to the free session below and we’ll work through them with you in 60 minutes.

Why you can trust the answer either way

98%fewer manual errors on rebuilt document flows

$50–70ktypical annual savings on rebuilt invoice and order flows

100+staff hours returned per month

6–12 motypical payback, inside the support window if you start now

High-volume document processing in a financial services back office

Both paths, delivered

The same team that rebuilds flows on TotalAgility also builds document automation off the Tungsten stack

On the “stay” side: a financial services back office running high-volume documents through manual indexing had its extraction layer rebuilt on intelligent document processing, cutting manual errors by 98% and returning 100+ hours a month. On the “leave” side: roughly 20 delivered automation engagements across deductions, remittance, and AP on other stacks. We don’t lose the deal whichever way you go. That’s exactly why the recommendation you get is clean.

Anonymized results from TechTiera’s delivered automation case studies.

The offer: a free Tungsten Migration & AI Readiness Session

60 minutes with people who deliver both paths. No fee, no prep documents required, no proposal unless you ask for one. You walk away with four deliverables:

End-of-support exposure map: component by component, which pieces of your Capture, Transformation Modules, and Import Connector estate lose support on which date, and what breaks first.
Both-paths comparison for your estate: Move Up to TotalAgility versus a platform exit, compared on the cost drivers that actually move quotes: batch classes, transformation projects, custom scripts, and connectors.
AI-readiness map of your document flows: the specific capture and extraction points where intelligent document processing has already paid off on flows like yours, and where it hasn’t.
A stay-or-leave recommendation in writing. Even if the recommendation is “stay put and do the minimum.” You can put it in front of your CFO with our name on it.

Book the free session

Tungsten Automation partner~20 delivered automation case studiesTotalAgility IDP delivery, with numbersDeductions · Remittance · APWe deliver both pathsDeliverables yours to keep

Questions people ask before booking

We’re still on Kofax Capture 9 or 10. Does the March 2027 date even apply to us?

It applies more, not less. March 3, 2027 is the end of support for Capture 11.1, the current version. Older versions like 9.x and 10.x left support years ago, which means you’re already running unsupported software and the 2027 date closes the last supported landing spot inside the product line. That makes the stay-or-leave decision more urgent for you, not optional.

Can we run the old and new environments side by side during the transition?

Yes, and you should plan to. Parallel running is the standard pattern for both paths: old batch classes keep processing while rebuilt flows are validated document type by document type. The catch is governance. You need a dated plan for retiring the old environment, or “transition” quietly becomes two systems forever, at two systems’ cost.

What about Transformation Modules and Import Connector? When do those lose support?

Transformation Modules 7.1 support ends May 9, 2027, about two months after Capture. Import Connector 2.11 runs to March 2028. These dates are surprisingly hard to find publicly, which is why customers end up asking for them on the community forum. The exposure map in the session lays your exact components against all three dates.

Do we still get patches and security updates until March 2027?

Until end of support, yes, under an active support agreement. What you should watch is cadence: aging components in the family have gone long stretches without updates, and some, like older export connectors that still can’t do TLS, have open gaps today. If a security or compliance review is coming, don’t assume “supported until 2027” means “current until 2027.”

Our older connectors don’t support TLS and security keeps flagging it. Does either path fix that?

Both paths fix it, because both paths retire the aging component. That’s actually a useful framing: if your security team is already writing up unsupported protocols, the migration business case is being built for you. The question is only whether the fix lands inside the Tungsten ecosystem or outside it, and that’s what the session’s comparison answers for your estate.

What actually happens to our batch classes and transformation projects if we Move Up?

They get rebuilt, not copied. TotalAgility organizes capture and extraction differently, so batch classes, tuned extraction projects, custom scripts, and release setups all translate to new structures. Converter tooling exists and handles a real share of the mechanical work, but it doesn’t understand your custom code or your integrations. In our delivered rebuilds, treating this as a redesign rather than a port is exactly where the 98% error reduction came from.

Since the rebrand we can’t even find downloads and license portals half the time. Is support going to get worse?

Your experience is common: portals moved, product names changed, and legacy installers became genuinely hard to locate. We can’t promise what vendor support looks like in 2028. What we can do is make sure you’re not depending on it: either on a current, supported TotalAgility footprint, or off the platform entirely. Both endpoints end the scavenger hunt.

What does the session cost, and what’s the catch?

Nothing, and the catch is transparent: a percentage of teams later ask us to deliver the path we recommended, and that’s the business model. The deliverables, including the written stay-or-leave recommendation, are yours to keep either way. No proposal follows unless you request one, and if the right answer is “stay put and do the minimum,” that’s what the recommendation will say.

Not ready to talk? Keep researching

Fair enough. This is a decision worth reading up on. Start with these, then come back when you want the questions answered for your estate specifically: