Not every Oracle shop running accounts payable on WebCenter is ready to re-platform onto Fusion. Many have years of invested process in WebCenter Imaging, Forms Recognition and Enterprise Capture, and the immediate goal is simpler: get off aging on-premises hardware and onto Oracle Cloud Infrastructure without breaking AP.
A hosting move needs its own compatibility, migration and acceptance plan. This note outlines the decisions: which application behavior to retain, which OCI services fit, how the dependencies determine sequencing, and what evidence is needed for cutover. It does not prescribe one architecture or promise a performance improvement.
If the roadmap includes Fusion, read this beside Migrating AP from WebCenter to Fusion Cloud. Decide whether an interim hosting move adds value before making it a separate project.
Why lift-and-shift before re-platforming
An ERP migration and an infrastructure move change different parts of the environment. A hosting-only project aims to retain the WebCenter process and ERP integration, but connectivity, configuration and operating assumptions may still change. Make those dependencies visible in the plan.
Assess the proposed benefits against the current baseline:
- Capacity and performance. Size the target from measured workloads and test peak processing; newer infrastructure alone does not establish a faster application.
- Cost. Compare compute, database, storage, licensing, network, operations and transition costs over the intended period.
- Future integration. Decide whether any additional cloud service is needed. Its availability does not establish compatibility or eliminate implementation work.
Staging changes can simplify a project, but it also adds transition work. Compare a combined move with staged options against the same acceptance and recovery requirements.
What maps to what
The table identifies architecture decisions to confirm, rather than automatic service mappings:
| On-premises today | On OCI |
|---|---|
| Invoice archive and repository | A storage design supported for the selected product release. OCI Object Storage is an optional configuration requiring a planned content migration and retrieval checks. See the repository planning guide. |
| WebCenter and AP schemas | A database deployment certified for the exact product combination, with capacity, backup, recovery and connectivity validated. |
| Point-to-point and middleware integrations | Retain and test supported interfaces, or scope a separate redesign where needed. Moving hosting does not automatically move flows into Oracle Integration. |
| Web tier and traffic | OCI Load Balancer in front of the WebCenter web tier, inside your own VCN. |
| Reporting and UI extensions | Inventory runtime and data dependencies, then test reports, output delivery and user workflows on the target. |
Verify available deployment images and their exact versions, licensing and prerequisites. Estates range across 11g, 12c and 14c, and a Marketplace image does not establish the migration path for every customization. The Marketplace comparison introduces that decision.
How to sequence the migration
Use these planning checkpoints to establish the sequence for the selected architecture:
- Inventory the WebCenter footprint. Every Imaging, Forms Recognition and Capture customization — Verifier fields, email import processors, the workflow hooks into EBS. Undocumented customizations are where lift-and-shifts go over budget.
- Design the target. Select supported hosting, database, network and storage services, with security, connectivity and operational ownership defined before migration.
- Rehearse the data and storage plan. Decide whether content storage changes. If it does, test the migration, reconciliation, image retrieval and ERP links on isolated copies before setting the production order.
- Rehearse application and database changes. Follow the applicable product procedures, coordinate dependent state and confirm recovery from the planned checkpoint.
- Reconnect to EBS and validate. Capture, recognition, routing and posting against a representative invoice sample in a non-production environment.
- Agree cutover and recovery. Define intake controls, synchronization, acceptance, reconciliation and recovery criteria. Test with production-shaped workloads while preventing duplicate posting to the ERP.
What the move does not change
Retaining the AP process is an acceptance objective, not an automatic result. Compare correctness, performance and operating effort with the baseline. Separate the hosting change from any product upgrade or process redesign included in the program.
The support timeline. Hosting alone does not extend the lifecycle of an installed release. Confirm each component’s target release, patch level and support position, including any upgrade performed alongside the move.
The process. Hosting alone does not redesign verification, coding, exception handling or approval routing. If those are improvement goals, include the design and acceptance work explicitly. The 12c decision guide introduces the alternatives.
How ECMWorks does this
We inventory the running products, customizations, integrations and content, then produce a scoped OCI plan. The work can include architecture, rehearsal, data and configuration migration, process validation and cutover support. Sequence and duration follow the dependencies and acceptance evidence for the selected design.