Skip to content

Migrations

Move the workload. Keep the estate.

A migration is a decision before it is a project: what moves, what is rebuilt, what stays. These guides set out each move — to OCI, to Fusion, to 14c-era architectures — with the constraints that decide it.

The four moves we are asked about most

  • Repository to OCI

    WebCenter Content and Imaging repositories moved to Oracle Cloud Infrastructure — the Marketplace image or a built domain — with the file store, database and integrations carried across intact.

  • AP imaging to Fusion Cloud

    When E-Business Suite moves to Fusion, the imaging and capture estate behind accounts payable has to follow, be retired, or be re-pointed. Each is a defined piece of work.

  • Forms Recognition to OCI Document Understanding

    Where WFR projects and learn-sets stop and what OCI Document Understanding can take on — decided from the actual invoice mix, not the brochure.

  • The replacement decisions

    Records retention, managed attachments, ADF non-PO forms, content alternatives. Some of the estate moves; some is rebuilt; some is left where it is on purpose.

Migration guides

Put the estate in front of an engineer.

Tell us the versions, the components and the integrations. You get a straight answer on what the estate needs, what it does not, and what order to do it in.

Talk to an engineer