Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 9 · Migration strategy and reconciliation
The cutover sequence
Lesson 89 of 177 · 2 min
What loads before go-live, what loads during the freeze, and what loads after — that ordering decides how long the business is unable to transact. BEFORE. Everything static: chart of accounts values, suppliers, customers, items, employees, positions. These can be loaded weeks ahead and verified at leisure, and any that are still changing can be topped up with a delta at the end. The more you move into this window, the shorter the freeze. DURING THE FREEZE. Only what cannot be known until the legacy system stops: open balances, open items as at the cutover date, and the final deltas on master data. The freeze is when the business cannot transact, so every hour of it has a cost somebody feels, and the design goal is to make this list as short as possible rather than as complete as possible. AFTER. History, if any. Anything that can be reconciled later…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 9 · Migration strategy and reconciliation
- 1What to migrate, and what to leave behind
- 2Balances versus transactions
- 3The cutover sequence
- 4Reconciliation: proving a migration landedFree preview
- 5Data cleansing, and who owns it
- 6Mapping legacy values to Fusion
- 7Trial loads and the rehearsal nobody schedules
- 8Sub-ledger and general ledger agreement
- 9Signing off: what "done" means
- 10What breaks: the migration that reconciled and was wrong
- 11Lab briefing · Plan and reconcile a migration