Not every Oracle shop running AP on WebCenter is ready to re-platform onto Fusion tomorrow. Many have years of invested process in WebCenter Imaging (WCI), Forms Recognition (WFR), and Enterprise Capture (WEC), and the more immediate goal is simpler: get off aging on-premise hardware and into Oracle Cloud Infrastructure (OCI) without breaking AP.
That move is a lift-and-shift, and it's a legitimate, lower-risk first step. We've done it — a global enterprise moved its critical AP operation from on-premise WebCenter onto OCI, then went on to invest further in Oracle Integration Cloud (OIC) once the foundation was stable. This post is the playbook for that kind of migration: what maps to what, how to sequence it, and where AP automation fits once you've landed.
If your roadmap goes all the way to Fusion, read this alongside Migrating AP from Oracle WebCenter to Fusion Cloud — the lift-and-shift is often phase one of that larger journey.
Why lift-and-shift before re-platforming
A WebCenter-to-Fusion re-platform changes your system of record, your approvals framework, and your integration model all at once. A lift-and-shift to OCI changes none of that. WebCenter keeps running — same WCI, WFR, WEC, same EBS underneath — but on Oracle's cloud infrastructure instead of your data center.
The payoff is real and immediate:
- Stability and performance. Running WebCenter on OCI tends to be more responsive and reliable than aging on-premise tin, with the headroom to scale at quarter- and year-end peaks.
- Capex to opex. You trade hardware, on-premise software, and the consulting around it for an operational cost.
- A platform for what's next. Once you're on OCI, OIC, Autonomous Database, and the rest of the cloud catalog are right there when you're ready.
It de-risks the bigger journey by separating "move to cloud" from "change the application."
What maps to what on OCI
The point of a lift-and-shift is that most of the architecture transfers conceptually intact. The mappings worth being confident about:
- Document storage → OCI Object Storage. The invoice image archive that lived on on-premise file systems and WebCenter Content moves to Object Storage — durable, cheap, and the natural home for high-volume invoice images.
- Database tier → Oracle Autonomous Database / Autonomous Transaction Processing (ATP). WebCenter and AP metadata land on a managed Oracle database, removing the patching and tuning burden.
- Integration → Oracle Integration Cloud (OIC). As you modernize, point-to-point and middleware integrations consolidate onto OIC's adapters and REST flows — the Oracle-supported path to EBS and, later, Fusion.
- Network and traffic → OCI networking with a load balancer. WebCenter's web tier sits behind an OCI Cloud Load Balancer inside your own VCN.
- Reporting and UI extensions → BI Publisher and Visual Builder (VBCS). Existing BIP reports carry forward; VBCS is available where you want lightweight cloud-native UI.
State only the mappings you're sure of, and validate the rest against your specific WebCenter version and customizations. Versions in the field range across WebCenter 11g, 12c, and 14c, and the migration path differs by where you're starting.
How to sequence the migration
Order matters more than speed. A sequence that has held up in practice:
- Inventory the WebCenter footprint. Document every WCI, WFR, and WEC customization — the verifier fields, the email import processors, the workflow hooks into EBS. Undocumented customizations are where lift-and-shifts go over budget.
- Stand up the OCI landing zone. Build the VCN, Object Storage buckets, and database tier with the right security posture before moving anything. Aim for no public IPs and private connectivity into your Oracle estate.
- Migrate the document archive first. Move the invoice image store to Object Storage and verify retrievability end to end — including the links back to EBS records — before touching the application tier.
- Lift the application and database tiers. Move WebCenter and its data onto OCI compute and Autonomous DB, behind the load balancer.
- Reconnect to EBS and validate. Confirm capture, recognition, routing, and posting all work against a representative invoice sample in a non-production environment.
- Cut over with a rollback plan. Run parallel where you can, and keep the on-premise environment recoverable until the OCI environment has cleared a real period close.
The discipline that pays off most: validate against a representative invoice sample at every stage, not just at the end. AP problems hide in the long tail — credit memos, multi-page invoices, the supplier whose layout WFR never quite learned.
Where AP automation fits after the move
Here's the trap. A clean lift-and-shift gives you the same WebCenter AP process on better infrastructure. Faster, more stable — but the manual work your team did on-premise is still manual on OCI. The migration didn't automate anything; it relocated it.
OCI is the moment to close that gap, because you're now sitting on the platform where modern AP automation runs natively:
- Capture and code invoices with AI extraction that beats WFR-era OCR and improves as it corrects, instead of the static recognition rates you migrated with.
- Match and route with tolerance handling and structured, per-approver queues rather than a shared pile.
- Prevent exceptions upstream by resolving the supplier inbox — status chasing, missing PO numbers, duplicate submissions — against live ERP data before invoices reach a workflow.
- Integrate the Oracle-supported way over OIC, so when you do take the next step to Fusion, the connective tissue is already correct. See our Oracle EBS & Fusion integration detail for how that posting model works.
That's the difference between a migration that just moves your costs and one that actually changes your AP operation.
Where EZ Cloud fits
Our roots are in Oracle AP from the WebCenter era — WCI, WFR, WEC, Managed Attachments, and the OCI services that host them: Object Storage, Autonomous DB, OIC, VBCS, and BI Publisher. We've lift-and-shifted WebCenter AP workloads onto OCI and then layered modern AP automation on top, deployed OCI-native inside the customer's own tenancy.
We're published on the Oracle Reference Architecture for OCI and featured in Oracle's own technical case studies. Oracle's published numbers put cloud AP at up to 80% faster than on-premise — but only if you use the move to fix the process, not just the hosting.
If a WebCenter-to-OCI migration is on your plan, the best time to design the AP automation layer is during the lift-and-shift, not after. That's a conversation worth having early.