// Lifecycle dates verified July 24, 2026

OpenText Captiva OCR: Captiva Capture Versions, Support Lifecycle and the Migration Path

Captiva is now sold as OpenText Intelligent Capture. Every release that still carries the Captiva name is past primary maintenance, and the oldest Intelligent Capture versions are reaching their dates now. Here is the full published lifecycle, with the ownership chain that explains the four names on your install.

  • Every version and its end date
  • Captiva to Intelligent Capture, explained
  • What sustaining maintenance costs you
  • How to scope a migration
Upload a document, no signup

PDF, JPG, PNG, BMP, HEIC, TIFF

Upload a document to extract

Run the document type your hardest Captiva flow handles and compare the fields you get back.

SOC 2 Type II
No capture server to deploy
US data handling
Fields, not just text
2019
the last Captiva-branded release
5 years
maintenance from every release date
0
Captiva versions in primary maintenance
1 Nov 2026
when 21.4 maintenance ends

The short answer

OpenText Captiva is enterprise document capture software that scans, classifies and extracts data from documents, then routes the results into a business system. It started life as Captiva Software Corp, whose flagship product was InputAccel, was acquired by EMC in 2005, passed to Dell with EMC in 2016, and was sold to OpenText in 2017 as part of a $1.62 billion acquisition of EMC's Enterprise Content Division. OpenText renamed it OpenText Intelligent Capture.

The part that matters if you run it: no release that still carries the Captiva name is in primary maintenance. Captiva Capture 16.6, the final Captiva-branded version, shipped in May 2019 and entered sustaining maintenance in May 2024. Captiva Capture 7.7 did so in January 2023. Sustaining maintenance is not a shutdown, but it does mean an Extended Support Fee applies and the version is no longer getting functional updates.

Last updated July 2026. Dates below are taken from the published OpenText Capture product lifecycle document dated 27 May 2026 and cross-checked against a partner-maintained lifecycle page.

OpenText Captiva and Intelligent Capture support lifecycle

Every release gets five years from its release date. The published document holds to that exactly on every row, which makes your own end date easy to work out even for a version not listed here: take the release date and add five years.

Release Release date Maintenance ends Status, July 2026
OpenText Intelligent Capture 24.2 01 May 2024 01 May 2029 In maintenance
OpenText Intelligent Capture 24.1 01 Jan 2024 01 Jan 2029 In maintenance
OpenText Intelligent Capture 23.4 01 Nov 2023 01 Nov 2028 In maintenance
OpenText Intelligent Capture for SAP Solutions 23.4 01 Nov 2023 30 Nov 2028 In maintenance
OpenText Intelligent Capture 23.3 01 Aug 2023 01 Aug 2028 In maintenance
OpenText Intelligent Capture 23.2 01 May 2023 01 May 2028 In maintenance
OpenText Intelligent Capture 23.1 01 Feb 2023 01 Feb 2028 In maintenance
OpenText Intelligent Capture 22.4 01 Oct 2022 01 Oct 2027 In maintenance
OpenText Intelligent Capture 22.3 01 Aug 2022 01 Aug 2027 In maintenance
OpenText Intelligent Capture for SAP Solutions 22.2 01 May 2022 01 May 2027 In maintenance
OpenText Intelligent Capture 22.2 01 Apr 2022 01 Apr 2027 In maintenance
OpenText Intelligent Capture 22.1 01 Feb 2022 01 Feb 2027 In maintenance
OpenText Intelligent Capture for SAP Solutions 21.4 01 Dec 2021 01 Dec 2026 Ends this year
OpenText Intelligent Capture 21.4 01 Nov 2021 01 Nov 2026 Ends this year
OpenText Intelligent Capture 20.2 01 Jun 2020 01 Jun 2025 Past primary maintenance
OpenText Captiva Capture 16.6 05/2019 05/2024 Past primary maintenance
OpenText Captiva Capture 7.7 01/2018 01/2023 Past primary maintenance

The two Captiva Capture rows come from a partner-maintained lifecycle page that lists them as sustaining support start dates; the Intelligent Capture rows come from the OpenText Capture product lifecycle document dated 27 May 2026, which also lists a "Current Version" row with maintenance ending 1 May 2029. OpenText publishes sustaining maintenance start dates rather than hard end-of-life dates, and Extended Support can be purchased beyond them.

The rename was also a support boundary

Most write-ups treat the Captiva to Intelligent Capture change as a marketing decision, and OpenText's own framing supports that reading. Its blog says the change is "an evolution, not a replacement", that "all existing CaptureFlows created within the Captiva CaptureFlow Designer are fully supported", and that "licensing remains the same for existing Captiva customers".

All of that is true and worth knowing. But the dates tell you something the naming discussion does not. The rename happened at a version boundary, and that boundary is now also the line between releases that are in maintenance and releases that are not. Captiva Capture 16.6 is the last release on the old side of it, and its maintenance ended in May 2024. There is no Captiva-branded version you can be running today that is still inside primary support.

The same clock is now reaching the early Intelligent Capture releases. Maintenance on 20.2 ended on 1 June 2025. Maintenance on 21.4 ends on 1 November 2026, and on Intelligent Capture for SAP Solutions 21.4 a month later. If you upgraded off Captiva in 2021 and have not moved since, your next date is this year rather than some time in the future.

What sustaining maintenance means

It is a paid tier, not a cutoff. The published guidance is direct: an "Extended Support Fee is required once a product version enters Sustaining Maintenance". Extended Support is offered to give you room to time a migration, and OpenText positions it that way.

We do not publish an OpenText price on this page. Intelligent Capture, Core Capture and Extended Support are all quoted per customer and no rate card is public. Any figure you see stated as OpenText's fee is somebody's guess.

Why your install has four different names on it

InputAccel, Captiva, EMC Captiva, OpenText Captiva, OpenText Intelligent Capture. They are all the same product line at different points in its ownership. This is the chain, with the dates.

2005

EMC acquires Captiva Software Corp

The acquisition closed 30 December 2005. Before it, the company was known to most of the market by its flagship product rather than its name: InputAccel.

2016

EMC becomes part of Dell

EMC became a wholly-owned Dell subsidiary on 7 September 2016. Five days later, on 12 September, EMC signed a Master Acquisition Agreement to divest its Enterprise Content Division.

2017

OpenText buys the division for $1.62 billion

The acquisition closed 23 January 2017. The division included Captiva alongside Documentum, ApplicationXtender and InfoArchive. The cash consideration is stated in Open Text Corp's SEC filing.

2019

Captiva Capture 16.6 ships

This is the last release to carry the Captiva product name. It entered sustaining maintenance in May 2024.

2020

The product becomes OpenText Intelligent Capture

Version numbering restarts on the OpenText calendar scheme, beginning with 20.2 in June 2020. OpenText describes the change as "an evolution, not a replacement".

2026

The oldest Intelligent Capture releases reach their dates

Maintenance on 20.2 ended in June 2025. Maintenance on 21.4 ends 1 November 2026, and on Intelligent Capture for SAP Solutions 21.4 on 1 December 2026.

A capture platform and an extraction API are not the same purchase

This is the distinction that decides whether replacing Captiva is a large project or a small one, and it is worth being blunt about in both directions.

1

What Captiva does that an API does not

A capture platform owns the physical side of the process: scanner operation, batch assembly, multi-function device intake, mailroom scanning, operator workstations and the routing of exceptions between them. If your documents arrive as paper and the scanning operation itself is part of the workflow, that is a real requirement and an extraction API does not replace it.

2

What an API does that Captiva does not

A modern extraction API reads unseen layouts without a template or a trained batch profile, returns structured fields with per-field confidence, and runs from a single REST call. There is no capture server to size, no designer to learn, and no version whose maintenance date you have to track. Volume scales with the meter rather than with hardware.

3

Where the honest line sits

DocuOCR is a cloud product. If your documents cannot leave your network, we are not the swap for an on-premises Captiva install and we will say so rather than sell around it. If the constraint is really about control and auditability rather than physical location, that is a solvable conversation about data handling terms.

If you want the platform-to-platform view instead, the closest comparisons to Captiva are Kofax, now Tungsten Automation, Hyland OnBase and IBM Datacap. All three are deployed and configured on a similar model, so a move between them is a migration rather than a signup.

How to scope this properly, in five steps

1

Find out which version you actually run

Captiva 16.x and Intelligent Capture 20.x and later are different support conversations. The version determines whether you are inside primary maintenance, buying Extended Support, or past both. Anything numbered 16.x or 7.x is Captiva-branded and out of primary maintenance.

2

Put your maintenance end date on the calendar

It is the release date plus five years, and the published document holds to that exactly on every row. If you are on 21.4 that date is 1 November 2026, which is inside this fiscal year for most US buyers.

3

Price the extended fee against the migration

Extended Support is a recurring cost on a version that is not receiving functional updates. Compare a year of it against the one-time cost of moving the workload, rather than against zero.

4

Separate the capture problem from the extraction problem

Many Captiva installs were built when scanning paper was the hard part. If most of your volume now arrives as PDF or email attachments, you may be maintaining a batch scanning platform to solve a problem you no longer have.

5

Test a real document before you commit to anything

Take the messiest document type in your Captiva flow, the one with the template nobody wants to touch, and run it through a modern extractor. That single test tells you more about your options than a feature matrix.

Where DocuOCR fits, and where it does not

DocuOCR classifies a mixed file, reads layouts it has not seen before without a template, extracts the fields you define, validates them, routes low-confidence reads to a built-in reviewer, and exports through a dashboard or one REST API. There is no capture server to size, no designer to learn, and no maintenance end date to track. Pricing is published and self-serve, which is a different model from a quoted enterprise license plus annual maintenance.

What we are not: DocuOCR is a cloud product, so it does not replace an on-premises install for a workload whose documents cannot leave your network, and it does not run scanners or mailroom batch operations. If your Captiva deployment exists because paper physically arrives in your building, you need a capture platform and we will tell you that rather than sell around it. If most of your volume now arrives as PDFs and email attachments, the platform underneath it may be solving a problem you stopped having.

OpenText Captiva questions, answered

What is OpenText Captiva?
OpenText Captiva is enterprise document capture software that scans, classifies and extracts data from paper and electronic documents, then routes the results into a business system. It began as Captiva Software Corp, was bought by EMC in 2005, and came to OpenText in 2017 when OpenText acquired EMC's Enterprise Content Division. It is now sold as OpenText Intelligent Capture.
Is OpenText Captiva the same as OpenText Intelligent Capture?
Yes. Intelligent Capture is the current name for the same product line. OpenText renamed it after acquiring the technology and states that "Intelligent Capture is an evolution, not a replacement" and that "all existing CaptureFlows created within the Captiva CaptureFlow Designer are fully supported". The Captiva name survives mainly in older installs, documentation and job postings.
Is OpenText Captiva still supported?
No release carrying the Captiva name is still in primary maintenance. Captiva Capture 16.6, the last Captiva-branded version, shipped in May 2019 and entered sustaining maintenance in May 2024. Captiva Capture 7.7 did so in January 2023. Extended Support can be purchased for versions in sustaining maintenance, so a Captiva install is not cut off, but it is no longer covered by standard maintenance.
What is the latest version of OpenText Captiva?
The Captiva name stops at Captiva Capture 16.6 from May 2019. Everything after that ships as OpenText Intelligent Capture on a calendar version scheme, running 20.2, 21.4, 22.1 through 22.4, 23.1 through 23.4, and 24.1 and 24.2. If you are looking for the newest release of the product you know as Captiva, it is the current Intelligent Capture version.
When does OpenText Intelligent Capture support end?
Each release gets five years from its release date, which the published lifecycle document holds to exactly. Maintenance on 20.2 ended 1 June 2025. Maintenance on 21.4 ends 1 November 2026 and on Intelligent Capture for SAP Solutions 21.4 on 1 December 2026. The 22.x line runs out through 2027, 23.x through 2028, and 24.2 until 1 May 2029.
What happens when a Captiva version enters sustaining maintenance?
It leaves primary support and moves to a paid tier. The published guidance is explicit that an "Extended Support Fee is required once a product version enters Sustaining Maintenance". Extended Support is designed to give you room to schedule a migration rather than to keep a version alive indefinitely, and the exact terms are set between the customer and OpenText.
What is the difference between OpenText Captiva and OpenText Core Capture?
Captiva, now Intelligent Capture, is the enterprise capture platform you deploy and configure, with a designer for building capture workflows. Core Capture is OpenText's SaaS capture line, which uses continuous machine learning and large language models to classify content and extract data without a scanned-batch pipeline to build. They are different products, not two names for the same one.
What was EMC Captiva InputAccel?
InputAccel was the original Captiva product, and the name the company was best known by before EMC acquired it in 2005. It was the batch capture engine: documents entered as scanned batches and moved through a defined sequence of processing steps. The InputAccel server remained the core of Captiva Capture through the 16.x releases, which is why the term still appears in older deployments.
Do I have to migrate off Captiva?
Not immediately, and not on a deadline OpenText has set for you. What has changed is the cost and risk profile: you are on Extended Support rather than primary maintenance, on a release whose newest version shipped in 2019. The practical questions are whether you are paying an extended fee for a version that no longer receives functional updates, and whether the workload still needs an on-premises batch capture platform at all.
What are the alternatives to OpenText Captiva?
They fall into two groups. Comparable enterprise capture platforms include Kofax, now Tungsten Automation, plus Hyland OnBase and IBM Datacap, all of which are deployed and configured much like Captiva. The other group is API-first document extraction products, including DocuOCR, which give you classification and field extraction through a REST call with no capture platform to stand up. Which group fits depends on whether you need the scanner and batch infrastructure or only the data.

Test your hardest Captiva document type in about a minute

Take the document with the template nobody wants to touch, run it through DocuOCR, and look at the fields and confidence scores. That tells you more about your options than any migration deck.