// Source System
Oracle to Dynamics 365 Data Migration
We've moved General Ledger, receivables and fixed assets out of Oracle E-Business Suite into D365 F&O — cleanly, completely, on time.
ORACLE EBS — Entity Mapping
// The Challenge
Why Oracle migrations are hard.
Oracle E-Business Suite spreads customer data across HZ_PARTIES and HZ_CUST_ACCOUNTS in the Trading Community Architecture model, which is more normalised than most legacy ERPs and needs careful flattening before it fits D365's customer structure.
The general ledger stores balances in GL_BALANCES and journal lines in GL_JE_LINES, segmented by a flexible chart of accounts (the accounting flexfield) that's often configured with more segments than D365's account structure supports directly. Deciding how those segments map to D365's main accounts and financial dimensions is one of the first design decisions we make.
Fixed assets live in the FA_ASSETS and FA_BOOKS tables, again with multiple depreciation books running in parallel. Inventory item masters in MTL_SYSTEM_ITEMS often carry organisation-specific attributes that need rationalising if the business ran multiple operating units in Oracle.
// Mapping
Oracle entities, mapped to D365.
| Source entity | D365 entity |
|---|---|
| HZ_PARTIES / HZ_CUST_ACCOUNTS — Customer | CustTable |
| AP_SUPPLIERS — Supplier master | VendTable |
| GL_JE_LINES / GL_BALANCES — GL | GeneralJournalAccountEntry |
| FA_ASSETS / FA_BOOKS — Fixed assets | AssetTable / AssetBook |
| MTL_SYSTEM_ITEMS — Inventory items | InventTable |
// Pitfalls
Where Oracle migrations go wrong.
- The accounting flexfield often has more chart-of-account segments than D365 supports natively — map segments to financial dimensions early.
- TCA's party/account/site model needs flattening — a single Oracle customer can span multiple sites that need consolidating or splitting for D365.
- Multiple operating units in one Oracle instance often use inconsistent item numbering that needs rationalising before it loads into a single D365 legal entity.
- Depreciation books (corporate, tax, other) in FA_BOOKS need an explicit mapping decision to D365's book value, made before build starts.
// Domains
Domains we most commonly migrate from Oracle.
// Methodology
The same six phases, every time.
01
DISCOVER
Profiling, volumes, quality scoring across every source system in scope.
02
DESIGN
Source-to-target mapping and the cleansing plan, agreed before build starts.
03
BUILD
DMF templates, KingswaySoft packages, SQL staging tables.
04
TEST
Two mock migrations, full reconciliation, and UAT sign-off.
05
CUTOVER
Final load, balance reconciliation, go-live clearance.
06
STABILISE
Corrections, closure report, retainer option for what follows.
// FAQ
Questions about migrating from Oracle.
Our primary experience is with E-Business Suite. Fusion Cloud migrations are scoped case by case given its different data architecture and API surface.
Planning a Oracle to D365 migration?
Start with a Health Check to see exactly what needs cleansing before it moves.