Your legacy core should not determine your future.
Move customers, accounts and financial balances into OREBAN through a controlled migration and cutover process built around validation, reconciliation and auditability.
Legacy closing position in. Reconciled OREBAN opening position out.
- 1
Map
Legacy structures matched to their destinations
- 2
Validate
Exceptions surfaced before they reach the core
- 3
Migrate
Customers and accounts moved in batches
- 4
Reconcile
Subledgers agreed against the closing position
- 5
Cut Over
Opening position posted with an audit trail
- 6
Go Live
Operations resume on the new core
Six stages, in order, with a gate at each one.
Migration is run as an accounting exercise. Each stage has to be complete and accepted before the next one begins.
- 1
Map
Map legacy Chart of Accounts and source structures to their OREBAN destinations before financial balances are posted.
- Legacy Chart of Accounts mapped to the OREBAN Chart of Accounts
- Products, account types and branches mapped to their destinations
- Mapping reviewed and signed off before anything is posted
- 2
Validate
Identify unmapped records, invalid data and accounting exceptions before they reach the live core.
- Unmapped records reported rather than silently defaulted
- Invalid and incomplete source data surfaced for correction
- Validation re-run until the exception list is empty
- 3
Migrate
Move customer, account and other required operational data through controlled migration batches.
- Customers, accounts and product records migrated in batches
- Each batch traceable back to its source file and mapping
- Rehearsed in a non-production environment before the live run
- 4
Reconcile
Reconcile migrated subledgers and opening balances against the institution’s validated legacy closing position.
- Subledger totals reconciled against legacy closing balances
- Variances itemised down to the account that caused them
- Reconciliation resolved before the cutover is authorised
- 5
Cut Over
Post the validated opening position through a controlled cutover process with a complete audit trail.
- Opening position posted through a controlled, authorised process
- Full audit trail of what was posted, by whom and when
- Legacy system frozen for the agreed cutover window
- 6
Go Live
Begin operations with OREBAN’s opening position matching the institution’s legacy closing position to the cent.
- Trial Balance reviewed and accepted by your finance team
- Branch operations resume on the new core
- Post-go-live support through the first accounting period
The principles the process is built on.
A core migration is judged on whether the books still balance afterwards. Everything below exists to make that the expected outcome.
Mapping before movement
Nothing financial is posted until the source structures have a confirmed destination in your Chart of Accounts.
Exceptions surface early
Validation is designed to fail loudly in a controlled environment rather than quietly inside a live core.
Reconciliation is the gate
The cutover is not authorised until migrated subledgers agree with the validated legacy closing position.
Everything is auditable
Each batch, posting and authorisation is recorded, so the migration can be explained long after it is finished.
Migration questions.
The questions finance and operations teams raise before they commit to a cutover date.
A validated closing position and extracts of the customers, accounts, products and balances to be moved, together with the Chart of Accounts they post to. We work with your team to confirm the extract before mapping begins.
The cutover does not proceed. Reconciliation is a gate, not a report — variances are itemised down to the account that caused them and resolved before the opening position is posted.
The migration is rehearsed in a non-production environment first, so the live run is a repeat of a process your team has already seen. The legacy system is frozen for the agreed cutover window rather than run indefinitely alongside.
It depends on the size and condition of the source data and how much cleanup the mapping and validation stages surface. We scope it against your actual extract rather than quoting a standard timeline.
Bring us your legacy closing position.
Tell us what you are running today and we will walk you through how the mapping, validation and reconciliation would work for your books.