Read the policy by product and release
The April 13, 2026 Oracle Lifetime Support Policy lists the relevant Fusion Middleware 12.2.x family boundaries as December 2026 for Premier Support and December 2027 for Extended Support. The corresponding 14.1.x family dates are December 2030 and December 2033. Product entries, exceptions and patch requirements still matter.
Extended Support includes eligible updates, fixes and security patches under Oracle’s terms; it is not a blanket severity-one-only service. Sustaining Support provides access to existing support resources and fixes, without the same new-fix and certification coverage. Confirm any additional arrangement with Oracle rather than assuming entitlement.
The support dates tool provides the component view. Database releases have their own policy and should not inherit these middleware dates.
Map the estate before scheduling it
Inventory product versions and patches, domains, schemas, directories, storage, customizations and external interfaces. Include separately versioned WFR, identity, analytics, search and third-party dependencies.
Oracle’s upgrade documentation is product-specific. Forms, ODI, WebLogic, SOA/BPM and WebCenter do not all have identical starting points or upgrade steps. Standalone OUD is not a WebLogic application, and WFR has its own Windows runtime.
Use the product path map to find the relevant planning pages, then establish the executable procedure for each installed release and topology.
Make four decisions explicit
- Coverage: what support and patches apply during the transition, and who confirms the terms?
- Target: which components upgrade, change hosting, are replaced or remain temporarily?
- Dependencies: which combinations must coexist, and what sequence is supported?
- Acceptance: what business, data, security and recovery evidence permits cutover?
Estimate duration from the inventory and rehearsal. A shared lifecycle date does not require all components to change in one window, and it does not prohibit a combined cutover where the dependency and recovery plan supports it.
Rehearse the shared-state changes
A new Oracle home separates binaries but does not preserve old schemas or domain configuration unchanged. Define consistent backups and recovery for the affected state, then test on isolated copies with production side effects contained.
For invoice processing, first assess whether SOA workflow can finish before migration. Plan active-instance handling only when needed, and reconcile unfinished ERP invoices independently. The coordinated upgrade guide covers those boundaries.
ECMWorks can help produce an estate inventory, supported dependency plan and acceptance scope. The WebCenter decision guide compares the available business choices without assuming a fixed schedule or cost advantage.