Which Oracle Fusion Middleware 12c products have a 14c upgrade path?

If you run any part of your stack on Oracle Fusion Middleware 12c (12.2.1.4), the short answer is reassuring: most components have a direct 14c (14.1.2) upgrade path, and it's a real product-line continuation, not a rewrite. WebCenter, SOA Suite, WebLogic Server, BPM, ADF, Forms & Reports, Identity & Access Management, and Data Integrator all have a 14c release you can upgrade into. Only two components in the classic 12c catalog do not continue to 14c and have to be replaced with something else: Oracle BI (OBIEE) and Endeca.

That distinction matters because Fusion Middleware 12c Premier Support ends in December 2026 (Extended Support runs through December 2027). So the planning question isn't abstract — it's "which of my components upgrade, which don't, and in what order do I move." Here's the complete component-by-component map.

The Fusion Middleware 14c component list at a glance

Here is the map most teams are looking for. Every row is either a supported 14c upgrade or a documented replacement — nothing in between:

The rest of this post walks each of these in the detail that actually shapes a project plan.

WebLogic, WebCenter, SOA Suite, BPM, and ADF — the core has 14c

The backbone of most Fusion Middleware estates upgrades cleanly. WebLogic Server has a 14c (14.1.2) release, and because nearly everything else runs on top of it, the WebLogic upgrade is usually the anchor the rest of the sequence hangs off.

WebCenter — Content, Imaging, Capture, and Portal — continues to 14c, and for AP-heavy shops that's the headline: the document platform you've run for a decade has a supported forward path. We cover the specifics in the WebCenter 14c upgrade guide. SOA Suite — the integration and orchestration layer — also has a 14c migration path, and BPM upgrades alongside it since they share the same runtime. ADF has its own 14c release too, which matters twice over: it's a framework upgrade in its own right, and it's one of the sanctioned destinations for teams modernizing older Forms applications.

None of these is a re-platform. They're version upgrades within the same product families — the same reason the 14c line exists at all.

Oracle Forms & Reports: 14c is a full upgrade, released February 2025

Forms & Reports 14c (14.1.2) shipped in February 2025, and it's worth being precise about what it is. It's a full upgrade, not a patch set — you move from 12.2.1.4 (or 12.2.1.19) up to 14.1.2. The release brings genuinely modern plumbing: HTTP/2, TLS 1.3, Java Virtual Threads, and — a nice operational win — no database credentials required at deployment.

You have two mechanics for the Forms 12c to 14c upgrade. In-place reuses the same Oracle Home: it's faster, but irreversible without a backup. Side-by-side stands up a new Oracle Home, which is lower risk because your 12c environment keeps running while you validate 14c. For most teams the side-by-side path is the sane default.

There are also alternatives to upgrading Forms — moving the application to Oracle APEX, rebuilding it on Oracle ADF (which, again, has its own 14c release), or exiting Oracle Forms entirely. Be honest with yourself about these: they're rewrites, not upgrades. They're larger, different projects with their own scope and risk. The platform upgrade to 14c is the fast, low-risk first step that buys you a supported runway; a rewrite is a decision you can make deliberately afterward, not something end-of-support pressure should force.

Identity & Access Management and Data Integrator both continue to 14c

Identity & Access Management 14c (14.1.2.1) was released in March 2025 and bundles the components you'd expect — OAM, OIG, OUD, and OID — running on WebLogic 14c. The Identity Management 12c to 14c upgrade is the one people most often overlook in planning, and it shouldn't be: it comes with roughly an eight-year support runway, which makes it one of the longer-lived anchors in the whole 14c line.

Data Integrator (ODI) upgrades from 12.2.1.4 to 14c as well. The one thing to flag operationally: the ODI repository upgrade runs through the Upgrade Assistant and is irreversible, so a verified backup of the repository before you start isn't optional. Plan the backup step into the runbook, not as an afterthought.

The two exceptions: Oracle BI and Endeca

Now the two components that don't continue to 14c — and knowing this early keeps them from derailing an otherwise clean upgrade plan.

Oracle BI (OBIEE) 12c has no 14c release. The forward path is a move to Oracle Analytics Server (OAS) — the on-premise successor — or Oracle Analytics Cloud (OAC). This is more time-sensitive than the rest of the list: OBIEE 12c Extended Support already ended in August 2025. If reporting still runs on OBIEE 12c, that's the component to schedule first, because it's the one whose support window has already closed rather than one that ends with the broader 12c line in 2026.

Endeca is the other exception. It has reached end of life with no successor product. Teams still running Endeca-based search or experience management should treat replacement as a separate initiative on its own timeline, evaluated against current search and content options — it isn't a component you upgrade, and there's no like-for-like Oracle destination to upgrade it into.

How to sequence the work

Put the map together and a natural order falls out. WebLogic anchors the platform. WebCenter, SOA Suite, BPM, ADF, Forms, Identity Management, and ODI each have a supported 14c upgrade you can slot in behind it. The two that need a different plan — OBIEE and Endeca — should be identified up front so they're scoped as replacements, not discovered mid-project as surprises. And OBIEE in particular, given its August 2025 Extended Support end, usually deserves to move to the front of the queue.

If you want the whole picture — the support dates, the sequencing logic, and how the pieces fit into one program rather than eight disconnected upgrades — start with the Fusion Middleware 12c end-of-support guide. And if you'd like a second set of eyes on which of your components upgrade cleanly and which need a replacement plan, a short Decision Call is the fastest way to turn this map into a dated, ordered runbook while the support clock is still in your favor.