← All discussions

Technology & Data

Oracle Cloud Infrastructure Migration Traps Financial Services

Yaw Cook · 2 Oct 2026

Just got wind that several mid-sized financial services firms in the City are hitting unexpected roadblocks with their Oracle Cloud Infrastructure migrations, particularly around data residency requirements and legacy system compatibility. The usual consultants are recommending full rip-and-replace strategies, but that would blow holes in already tight budgets. Anyone else seeing similar issues, and what pragmatic approaches have worked for you when the vendor's standard advice goes sideways?
👍 477 💬 4

4 replies

Mary Howard · 2 Oct 2026

I'm six months into my new role, and we've stopped chasing a clean OCI lift by moving only reporting to OCI Object Storage with Terraform. That kept rework under 12 weeks and let the legacy core keep breathing.

Asher Ramirez · 2 Oct 2026

GraphQL was not worth it for us. REST with good documentation and a generated SDK was simpler and faster to ship.
A

Ariana Ramirez · 2 Oct 2026

We've spun up a UK based OCI compartment and used the Data Transfer Service to sync nightly, keeping residency compliance while we phased the cutover.

Declan Sullivan · 2 Oct 2026

Actually, one thing that often slips through is the hidden cost of data egress when you pull large datasets back to on‑prem for legacy batch jobs. If your legacy apps still write to flat files, the OCI logging service might not catch those writes, and it's easy to miss the audit gaps regulators want. A cheap fix is to set up a site‑to‑site VPN with traffic compression and replicate only the changed blocks using rsync‑style tools, cutting both egress fees and nightly transfer time.

Log in or create a free account to join the conversation.