Migrating From Kofax to Tungsten Automation Capture

If your team runs Kofax Capture, you have probably noticed the name change. Kofax became Tungsten Automation in January 2024, and the capture product now goes by Tungsten Capture (often searched as Tungsten Automation Capture). That raises a fair question: does this mean you have to migrate?

For most teams, the honest answer is “not in the way you might fear.” The rename is not a forced replatform. But there are real migration decisions sitting behind it: upgrading to a current version, moving to TotalAgility, or modernizing the environment Capture runs in. This guide explains what actually changes, separates those paths, and covers what to plan before you start.

What Changed in the Kofax-to-Tungsten Transition

On January 16, 2024, Kofax announced its new name: Tungsten Automation. The company described a business with roughly 40 years of history and more than 25,000 customers that was keeping its focus on intelligent document processing and automation. The announcement was about the company name and brand direction. It did not describe a set of product renames or replacements.

The product documentation followed. The release notes for Tungsten Capture 11.2.0 describe the product as renamed Tungsten Capture, and the company as formerly Kofax, Inc. In other words, the 11.x version line you may already know as Kofax Capture carries on under the new name.

In practice, that means a few things:

• A rename on its own does not require you to rebuild batch classes, workflows, or integrations.
• You will see both names for a while. Older documentation, installers, vendor emails, and internal runbooks still say Kofax. Newer material says Tungsten.
• The real work comes from the version, platform, and environment decisions that the rebrand tends to bring to the surface.

For a plain-English overview of the rebrand and what the product does, see our guide: What Is Tungsten Automation Capture?

Which Kind of Migration Are You Actually Facing?

Teams use “migration” to describe three different projects. Knowing which one you have decides the scope, the risk, and the budget.

Path 1: Upgrade Within Tungsten Capture

Most Kofax Capture customers are here. You stay on the same product and move to a newer version. The work typically includes updating the server and workstations, bringing existing batch classes forward, retesting custom scripts and modules, and confirming your export connectors still behave.

Newer releases add practical improvements, such as support for Group Managed Service Accounts when installing or configuring the Capture service, and better batch management tools for operations teams. Tungsten’s documentation also covers a batch class update step for existing batch classes. Check the “Changes in behavior” notes for your starting version, and run the update on a copy of your environment before touching production.

This is the kind of work our platform upgrades team handles most often.

Path 2: Move Up From Capture to TotalAgility

TotalAgility is Tungsten’s broader automation platform, and Tungsten promotes the move from Capture as a “Move Up.” Capture is a client-server product built around stations like scan, validation, and verification, while TotalAgility is a cloud-capable platform that also handles process automation. Moving to it is a choice, not a requirement of the rebrand.

Capture or TotalAgility? A few rules of thumb:

• Staying on Capture usually fits if your workflows are stable, your volumes are predictable, and the system is doing its job.
• TotalAgility is worth a look if you want cloud deployment, more process automation around capture, or newer AI-assisted extraction.
• Either way, the decision should follow your documents and workflows, not the name on the box.

Tungsten provides a converter for Capture batch class files and Transformation Modules projects, which saves you from starting from scratch. It does not finish the job. According to Tungsten’s migration guide:

• Only some validation methods and formatters convert. Others are dropped or come across with settings blank.
• Foldering must be reconfigured, and validation forms must be recreated.
• Scripts that trigger batch events must be rewritten.
• Online learning works differently and needs to be configured in the new platform.
• The converted project cannot be updated with the converter afterward, so finish all changes in the original project first.

Plan extra time for older Transformation projects, and plan for ongoing retraining after the move. Our Tungsten TotalAgility services page covers how we approach it. Because DAS implements both Capture and TotalAgility, we would rather help you pick the platform that fits than push one.

Talk to DAS about your Kofax-to-Tungsten move →

Path 3: Change the Environment Around Capture

Sometimes the product stays the same and everything around it changes: new servers, a newer Windows Server or SQL Server version, virtualization, or a new destination for captured documents such as IBM FileNet, SharePoint, or another ECM platform.

Check Tungsten’s technical specifications for your target version before you buy hardware or schedule operating system upgrades. If the destination is changing, also read about systems integration and content migration, since moving documents that were already captured is a separate project from moving the capture system itself.

One more note. If your real problem is documents your templates cannot handle, such as handwriting or phone photos, a migration may not fix it. Our post Legacy Capture, Modern Gaps covers when a targeted layer beats a replacement.

The Risks Worth Planning For

Most migration problems come from the same handful of places:

• Custom scripts and modules. These are often years old, lightly documented, and owned by someone who has moved on. Find them early.
• Extraction projects and training data. Re-measure accuracy after any move. Do not assume results carry over unchanged.
• Integrations and export connectors. ECM, ERP, and line-of-business systems all depend on what Capture sends them.
• Batches in flight. Decide what happens to batches that are mid-process at cutover, and pick a low-volume window.
• Lifecycle and support dates. Support timelines depend on your exact version. Check Tungsten’s published end-of-support information for the version you run.
• Licensing and maintenance. Terms are set by Tungsten and your reseller, so confirm them before you commit to a path.
• People. Operators and administrators have habits built around the current setup. Training and updated runbooks matter.

A Practical Migration Planning Checklist

1. Take inventory. List versions, modules, batch classes, scripts, connectors, and document volumes.
2. Document what each batch class does and who owns it. Retire anything nobody uses.
3. Choose your path. Upgrade, TotalAgility, environment change, or a combination.
4. Read the target version’s documentation. Start with the technical specifications and the changes in behavior notes.
5. Build a test environment. Use copies of your batch classes and a representative set of documents. Compare extraction accuracy and export results against production.
6. Plan cutover and rollback. Pilot with one batch class or department first.
7. Train people and clean up the naming. Update runbooks, and decide how your team will refer to the product going forward.

Where DAS Fits

DAS is a certified Tungsten Automation partner with more than a decade of experience configuring Capture for financial services, insurance, healthcare, and public sector organizations. We handle upgrades, TotalAgility migrations, and the integrations around them. Learn more about our Tungsten Capture services and our wider Tungsten Automation practice, or read the full Tungsten Automation Capture overview.

Not sure which path you are on? Get a second set of eyes on your Capture environment. Schedule a Capture Consultation →