OpenText Core Capture vs Intelligent Capture: What Is the Difference?

The short answer: OpenText Core Capture is a cloud SaaS capture service that uses continuous machine learning to classify documents and extract data, configured through a browser. OpenText Intelligent Capture is the enterprise capture platform you deploy and configure, and it is the product that used to be called Captiva. They are two different products on two different delivery models, not two names for the same thing. If your capture runs on a server your team maintains and has a version number like 21.4 or 16.6, you are on Intelligent Capture or Captiva. If you log into it in a browser and never patched anything, you are on Core Capture.

That confusion is worth clearing up before a renewal conversation, because the two products have completely different cost structures, upgrade obligations and migration paths. Below is the comparison, what each one actually does, and how to work out which one is running in your organization.

OpenText Core Capture vs Intelligent Capture at a glance

What is OpenText Core Capture?

OpenText Core Capture is OpenText's software as a service capture line. In OpenText's own description it uses "continuous machine learning to enable intelligent document processing and accelerate information routing to the right users and systems". You reach it through a browser, including a browser based workflow designer, and there is no capture server for your team to size, patch or upgrade.

It is sold as a small family rather than a single product: Core Capture, Core Capture for Salesforce, and Core Capture for SAP Solutions. The integration list runs to Microsoft 365, Gmail, Salesforce, SAP, OpenText Core Content Management and Documentum, with SFTP available as an import source. The most recent cloud edition documented publicly, CE 25.4 from November 2025, added direct capture from the Core Content Management interface and support for SAP Transportation and Dispute Management with 20 new standard fields.

One detail in the release history is genuinely notable and rarely mentioned in vendor comparisons: OpenText Core Capture uses Google AI services under the hood. OpenText's own release notes describe using Google Vertex AI to "automatically identify and label key data fields", and a Google Vision integration for handwriting extraction. There is also a feature that uses an LLM to create extraction profiles so that data field configuration does not need a specialist. If your procurement process cares which AI services touch your documents, that is a question to ask directly rather than assume.

What is OpenText Intelligent Capture?

OpenText Intelligent Capture is the enterprise capture platform, and it carries a long history. It began as Captiva Software Corp, whose flagship product was InputAccel. EMC acquired it in 2005. When OpenText bought EMC's Enterprise Content Division in a deal that closed in January 2017, Captiva came with it, and OpenText later renamed it Intelligent Capture.

It is an omni channel capture platform, which in practice means it handles the physical side of document intake that a cloud service does not: scanner operation, batch assembly, multi function device intake, mailroom scanning and operator verification stations. You deploy it, you configure it in the CaptureFlow Designer, and you own the upgrade schedule.

That last point is where most of the real cost sits. Each Intelligent Capture release gets five years of maintenance from its release date, and the published lifecycle document holds to that exactly. Maintenance on 20.2 ended on 1 June 2025. Maintenance on 21.4 ends on 1 November 2026. Once a version passes that date it moves into sustaining maintenance, where an extended support fee applies. We keep the full dated table, including every Captiva branded release, on our OpenText Captiva support lifecycle reference.

Does Core Capture replace Intelligent Capture?

No, and this is the most common wrong assumption. OpenText sells both. Core Capture is not positioned as the successor to Intelligent Capture, and Intelligent Capture releases are still shipping on the calendar version scheme, with 24.2 carrying maintenance through May 2029. They target different situations.

The rename that genuinely happened was Captiva to Intelligent Capture, and OpenText was explicit that this was "an evolution, not a replacement", adding that "all existing CaptureFlows created within the Captiva CaptureFlow Designer are fully supported" and that "licensing remains the same for existing Captiva customers". Core Capture is a separate line that arrived later, not the next version of anything you are running.

How do I tell which one I am running?

Four checks, in order of how quickly they settle it:

• Look for a version number. Anything of the form 16.x or 7.x is Captiva branded and out of primary maintenance. Anything of the form 20.2 through 24.2 is Intelligent Capture. Core Capture uses cloud edition labels like CE 25.4 and you generally do not have to care about them.
• Ask who patches it. If your team or your implementation partner schedules upgrades, it is Intelligent Capture. If nobody does, it is Core Capture.
• Look at where the designer lives. A thick client CaptureFlow Designer means Intelligent Capture. A designer that opens in a browser tab means Core Capture.
• Check whether scanners are configured in it. Direct scanner and mailroom batch operation is Intelligent Capture territory.

Which one should you choose?

If paper physically arrives at your building in volume and the scanning operation is part of the workflow, the deployed platform exists for a reason and a cloud capture service will not cover it. That is a real requirement and it is worth being honest about.

If most of your volume now arrives as PDFs and email attachments, which is the direction almost every US finance and operations team has moved, the calculation changes. A capture platform built around batch scanning is a lot of machinery to maintain for documents that were never on paper. At that point the question is not which OpenText product to pick but whether you need a capture platform at all, or just reliable extraction plus somewhere to send the result. Teams that land on the second answer usually end up wiring the extracted fields into their ERP or accounting system through whatever integration layer already connects their business systems, rather than through the capture product itself.

The third consideration is pricing transparency. Neither Core Capture nor Intelligent Capture publishes a rate card. Both are quoted per customer, usually with volume based licensing, and extended support is a separate negotiation once a version passes its maintenance date. If you are comparing against products with published per page pricing, insist on a modeled annual figure rather than a license number, because the license is rarely the whole cost.

Common questions

Is OpenText Core Capture the same as Captiva? No. Captiva became OpenText Intelligent Capture. Core Capture is a separate SaaS product line that does not share the Captiva lineage.

Can I run both? Yes, and some large organizations do, typically keeping a deployed platform for scanned paper while running cloud capture for a specific application such as Salesforce or SAP.

Is Intelligent Capture being discontinued? Nothing published says so. Releases through 24.2 carry maintenance dates into 2029, and OpenText continues to ship on the numbered scheme.

What happens if I stay on an out of maintenance version? You move to sustaining maintenance, where an extended support fee applies and the version stops receiving functional updates. It is a paid holding position designed to give you time to plan a migration, not a permanent state.

The practical next step

Whichever product you are on, the fastest way to find out what your options actually look like is to take your hardest document type, the one with the template nobody wants to touch, and run it through a modern extractor to see what comes back. Field level output and confidence scores tell you more in five minutes than a feature matrix does in a week. You can upload a document to DocuOCR and see the extracted fields without configuring anything, and if you want the platform to platform view instead, our OpenText Intelligent Capture alternative comparison covers where a deployed capture platform still wins and where it does not.