Start with the decision a sponsor must make
The decision is which services and business processes the organization needs to operate, under what constraints, and who will fund and own the necessary work. The answer may involve several components and more than one project.
For published lifecycle endpoints, use the support dates reference. Oracle’s Lifetime Support Policy must be applied to the exact product and release, including its footnotes and error-correction conditions. Do not use a family date as a warranty for an installed estate.
Establish the baseline
Collect the installed releases and patches, hosting arrangement, support agreements, custom components, integrations and named owners. Map how documents enter the system, how users validate and approve work, how an ERP transaction is created or updated, and how historical documents are retrieved.
Keep unknowns visible. A missing source project, an undocumented authorization rule or an unconfirmed support term can change the options. The browser decision guide helps organize these questions; it does not inspect the estate or validate entitlement.
Compare four kinds of response
| Response | Intended change | Evidence needed before approval |
|---|---|---|
| Continue operating for a defined period | Retain the present implementation while managing its known limits | Confirmed coverage, exposure assessment, maintenance capacity, review triggers and an exit owner |
| Upgrade applicable products | Change product releases while retaining required business behavior | Supported starting points and target combinations, customization assessment, rehearsal and acceptance evidence |
| Change hosting, including OCI | Move the deployment and its operational responsibilities | Target architecture, licensing and support terms, security ownership, transfer and recovery design |
| Replace a defined workload | Move selected functions to an alternative implementation | Functional fit, interface support, records treatment, migration reconciliation and target operating capacity |
Oracle documents WebCenter Content on Marketplace. Its availability is not evidence that all existing components and customizations can be transferred unchanged. Assess each dependency and the selected offering separately.
Decide what remains
A new invoice-processing service does not automatically retire the repository holding historical records. An ERP move does not automatically settle active middleware instances. A repository upgrade does not prove that all document links and permissions still work.
For each option, list what remains in operation, what is replaced, the temporary overlap and the conditions for decommissioning. Include retained licenses, support, storage, access paths and engineering responsibilities in the cost comparison.
Require acceptance and recovery evidence
A proposed route should name representative documents, user roles, integrations and failure cases. Agree how the team will reconcile documents and business transactions, demonstrate permitted retrieval, handle active work and verify recovery.
The appropriate order depends on shared state and dependencies. A new server or Oracle Home does not by itself create an independent rollback environment. Use the exact-release product procedure and demonstrate recovery of the state it changes.
Make the decision reviewable
Record the selected scope, reasons, rejected alternatives, assumptions, unresolved conditions, owners and evidence required at the next decision point. Estimate effort from that scope. The scenario planner can compare declared cost assumptions; its outputs are not quotes or proof of feasibility.
When the baseline is incomplete, an Estate Review is a useful first engagement. A defined upgrade, migration or support retainer follows the agreed direction and boundaries.