Migrating general-ledger balances is the heart of any Oracle Fusion Financials migration. This guide covers the GL FBDI template, mapping your source chart of accounts to the Fusion accounting flexfield, opening versus historical balances, the validation errors that trip teams up, and how to reconcile the trial balance to the cent.
GL migration is a mapping problem first and a loading problem second: get the chart-of-accounts crosswalk and ledger structure right, and the FBDI load and reconciliation become mechanical.
You decide how to represent history — most teams load opening balances as of cutover plus a number of prior periods as summarized journals for reporting continuity, rather than every historical transaction. Source balances and journals are mapped from the legacy COA to the Fusion accounting flexfield, then loaded through the GL FBDI (Journal Import) as balanced journals per period and ledger.
Oracle's import validation rejects unbalanced journals, invalid code combinations and bad periods — so expect iterative sandbox loads to burn down the error backlog. The migration isn't done until the Fusion trial balance equals the source trial balance for every period and entity.
What to get right.
Map every source account/segment to a valid Fusion code combination; this gates the load.
Load opening balances at cutover plus summarized prior periods for continuity.
FBDI Journal Import requires each journal to balance by ledger and currency.
Entered vs accounted amounts and rate types must be handled for FX ledgers.
Load per ledger and balancing-segment value so entities reconcile.
Expect multiple load cycles to clear validation errors.
The mechanical sequence.
Map source accounts/segments to the Fusion accounting flexfield; validate code combinations.
Pull trial balances and (summarized) journals per period from the source.
Populate the Journal Import template; ensure each journal balances per ledger/currency.
Run Load Interface File for Import, then Import Journals; review the execution report.
Fix unbalanced journals, invalid combinations and period issues; re-load iteratively.
Compare Fusion trial balance to source per period and entity until they match to the cent.
What trips teams up.
The top FBDI rejection — every journal must balance by ledger and currency.
Unmapped or disabled flexfield combinations fail import.
Target periods must be open for the load.
Entered/accounted amounts and rate types must be consistent on currency ledgers.
Loading isn't done until the trial balance ties out per period and entity.
Pre-built extraction, FBDI generation and reconciliation remove the manual grind.
Map your source chart of accounts to the Fusion accounting flexfield, extract trial balances and summarized journals per period, generate the GL FBDI (Journal Import) with balanced journals, load to a sandbox, clear validation errors iteratively, and reconcile the Fusion trial balance to the source per period and entity.
Most teams load opening balances at cutover plus a few prior periods as summarized journals for reporting continuity, and archive the full transaction history rather than loading every historical journal into Fusion. This keeps Fusion lean while preserving auditability.
The most common causes are unbalanced journals, invalid or disabled account code combinations, and closed/unopened target periods. Review the import execution report, fix the flagged rows and re-load — expect several iterations.
Compare the Fusion trial balance to the source trial balance for every period and per ledger/balancing-segment (entity). The migration is complete only when they match to the cent, evidenced for finance and audit sign-off.
Yes — Syntra ETL automates the extraction, COA crosswalk application, FBDI generation and trial-balance reconciliation, removing the manual template-building and error-chasing.
Tell us your source finance system and we'll handle the COA crosswalk, FBDI load and trial-balance reconciliation on a fixed-fee basis.