Oracle E-Business Suite to Fusion Cloud ERP
To move from Oracle EBS to Fusion Cloud ERP, sort every customization into what Fusion covers, what becomes an extension and what goes away. Then settle the ledger design, convert data through FBDI and rebuild integrations on REST APIs or Oracle Integration. Cohash runs that work, sets up quarterly update testing and archives EBS history.
- 01Customization inventory
- 02Financial design
- 03Data conversion
- 04Integrations and extensions
- 05Quarterly update readiness
- 06Cut-over and EBS archive
The story
Told without the client's name or anything that could identify them.
A manufacturer's finance and IT teams ran Oracle E-Business Suite 12.2 with a large stack of custom forms, reports and interfaces, and every patch cycle was slow. Demantra, which loses Premier Support in December 2026, ran the demand plan, finance wanted a new chart of accounts built once, and the DBA team was shrinking. We sorted every customization into what Fusion covers, what becomes an extension and what goes away, gave planning its own track, and redesigned the ledger. Mock conversions ran through FBDI with reconciliation after each, interfaces moved to REST APIs and Oracle Integration, and the business went live on Fusion Cloud ERP by business unit with EBS history archived for auditors.
why it was urgentNothing forces you off EBS yet. Oracle lists EBS 12.2 Premier Support through at least December 2037. The pressure comes from the edges instead. Demantra and EBS Value Chain Planning lose Premier Support in December 2026, the Sales and Marketing products in December 2027, and Fusion keeps moving with quarterly updates such as 26D.
- openThe demand plan lives in Demantra or Value Chain Planning, and its Premier Support ends in December 2026.
- recurringHundreds of custom forms, reports and interfaces make each EBS patch cycle slow.
- blockedFinance wants a new chart of accounts and doesn't want to build it twice.
- openThe DBA team supporting EBS is shrinking and hard to hire for.
The estate, before and after
Before: EBS 12.2 with custom code at every edge
Finance and procurement worked in EBS 12.2, with Demantra feeding the demand plan and custom forms, reports and interfaces around it. Each patch cycle had to retest all of that custom code.
After: finance on Fusion Cloud ERP, interfaces on supported APIs
Finance runs on Fusion Cloud ERP. Reports come from OTBI and BI Publisher, custom logic sits in supported extensions, and Oracle Integration and REST APIs carry the interfaces. Each quarterly update goes through a regression suite, and EBS history lives in an archive auditors can query. Planning moved on its own track, not shown here.
How we run it, phase by phase.
6 phases take you from Oracle E-Business Suite 12.2 to Oracle Fusion Cloud ERP. Each one ends with something you can check before the next starts. As you scroll, the blocks show the estate moving across.
- phase 01
Customization inventory
Go through every custom form, report, interface, workflow and extension and mark it. Fusion covers it, or it's rebuilt as an extension or integration, replaced by a report in OTBI or BI Publisher, or retired.
- phase 02
Financial design
Decide whether the ledger, chart of accounts and legal entity structure carry over or get redesigned, and agree how open balances and history move.
- phase 03
Data conversion
Extract and clean suppliers, customers, items and open transactions, load them with FBDI templates, and reconcile counts and balances after every mock conversion.
- phase 04
Integrations and extensions
Rebuild EBS interfaces on Fusion REST APIs, FBDI or Oracle Integration. Move custom logic into supported extensions, out of code inside the ERP.
- phase 05
Quarterly update readiness
Automate regression tests for key processes and run them in a test pod with every quarterly update, so key users aren't doing it by hand.
- phase 06
Cut-over and EBS archive
Convert final balances and go live by ledger or business unit. EBS transaction history goes into an archive auditors can query once the instance is switched off.
What the client got
What changed for the client once the work was done. Described, not scored: we don't publish client figures.
- result 01
Each customization has an owner and a decision
No customization was carried over by default. Each form, report, interface and workflow was marked covered by Fusion, rebuilt as an extension or integration, replaced by an OTBI or BI Publisher report, or retired.
- result 02
Finance works on a new chart of accounts
The ledger, chart of accounts and legal entity structure were redesigned once, in Fusion, with open balances and history moved as agreed.
- result 03
Converted data reconciles at every mock run
We load suppliers, customers, items and open transactions through FBDI templates. Counts and balances reconcile after each mock conversion.
- result 04
Integrations run on supported interfaces
What used to be EBS interfaces now runs on Fusion REST APIs, FBDI or Oracle Integration. Custom logic lives in supported extensions instead of inside the ERP.
- result 05
Quarterly updates are tested automatically
An automated regression suite for key processes runs in a test pod each time a quarterly update arrives, so key users aren't pulled off their jobs.
Risks we plan for
-
Recreating EBS in the cloud
Rebuilding every customization as an extension brings the old patching pain back. Each one needs a business owner who confirms it's still needed.
-
Open transaction conversion
Open purchase orders, invoices and projects are harder to convert than master data. Teams that leave them to the last mock run find the reconciliation gaps too late.
-
Planning tools on a deadline
Demantra and Value Chain Planning lose Premier Support before most ERP moves finish. Planning may need its own track and timeline.
-
Update fatigue
Quarterly updates change screens and behavior. If testing isn't automated, every update drags key users away from their actual jobs.
Where AI helps, and where it needs guardrails
Fusion has AI Agent Studio, where you can build your own agents next to the ones Oracle embeds. Check how agent usage gets billed on your subscription before you plan around it. Any agent that creates or approves transactions should run as a dedicated user with a narrow role and still go through Fusion's approval rules. During the move, an LLM can draft field mappings and test cases from EBS metadata, and consultants check them.
forward deployed engineers →What you're left with
We write these for your setup, and they're working documents. Your team should be able to keep things running from them long after we've gone.
- inventory01
Customization inventory. Each object gets a business owner and a keep, rebuild or retire call
yours to keep - design02
Ledger and chart of accounts design
yours to keep - code03
FBDI conversion scripts and reconciliation reports per mock run
yours to keep - design04
Integration designs on REST APIs or Oracle Integration
yours to keep - tests05
Automated regression suite for quarterly updates
yours to keep - plan06
EBS archive plan and retention schedule
yours to keep
Platforms and services on this move
Learn the background
Terms from this page in plain English. If you want the why, the field note behind it is right there.
- 01ERP
- Enterprise resource planning. It's the system finance and operations staff live in: the ledger, purchasing, sales orders, stock and often production, all in one database.in context →
- 02Extension
- Your own code sitting on top of the standard product, which stays untouched underneath. Business Central extensions are written in AL, Finance and Operations ones in X++.in context →
- 03extensions
- Custom code that sits beside Microsoft's code and adds to it without editing it. This is what lets Microsoft update Finance and Operations several times a year.in context →
- 04Premier Support
- The first stage of Oracle's support policy. You get CPU patches here and in Extended Support, which you pay extra for. Once both end, the patches stop coming.in context →
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Onsite
Engineers at your sites in the US
Nearshore
Overlapping hours with US teams
Offshore
Overnight progress on your backlog
All time zones
Coverage handed over across time zones
01We run Oracle EBS. How do you migrate from EBS to Fusion Cloud?
Start with the customization inventory, because it sets the size of everything after it. Then settle the ledger design, run mock conversions through FBDI and reconcile each one, and rebuild interfaces on REST APIs or Oracle Integration. Go live by ledger or business unit, and archive EBS history so auditors can still query it.
02EBS is supported to 2037. Why move now?
Many shouldn't yet. Moving makes sense if planning tools are losing support, if you're redesigning finance anyway, or if the cost of running EBS is rising. If none of that applies, an EBS upgrade to 12.2.15 and a later move can be the right call, and we say so.
03Can we keep some EBS modules running?
Yes, for a while. Finance can move first while manufacturing or projects stay on EBS, connected through integrations. That adds interface work, so keep the gap between phases short.
04What drives the cost?
The number of customizations and interfaces, how many ledgers and countries go live, data quality and how much history you need to convert instead of archive.
Often on the same roadmap
On-premises Active Directory to cloud-first Microsoft Entra ID
We shrink on-premises Active Directory one application at a time, moving groups, users and app authentication to Microsoft Entra ID as each app is ready.
read the case studyAD FS federation to Entra ID authentication
Converting federated domains from AD FS to Entra ID cloud authentication, moving relying parties app by app and retiring the AD FS farm.
read the case study
Apache Airflow 2 to Airflow 3
Upgrading self-managed Apache Airflow 2, now past end of life, to Airflow 3, and fixing removed features, auth and scheduling changes before DAGs move.
read the case studybf22ec71 - 01Book a 30-minute working sessionsenior engineer
- 02Talk to an engineer about your setupreply within 24 hours
- 03See how similar projects wentcase studies
Planning this move?
A 30-minute working session with a senior engineer. No slides.
- The platform and the version you're on
- Where you need to get to, and by when
- What's custom: rules, plugins, integrations
- Any audit finding or deadline driving it