Data migration
Housing association data migration to Oracle Fusion
Data is where housing finance teams want the most certainty. Every load is reconciled to your control totals and approved by your finance team.
Housing finance teams ask three questions first. Will our balances be right? Will the asset register come across with its components? How much history do we have to bring? We settle the answers early and in the open, and rehearse the migration before the day it counts.
Migration and reconciliation are included in the implementation.
Short answer
How is housing association finance data migrated to Oracle Fusion?
Balances, open items, suppliers and the asset register with its components are profiled with housing-aware rules, rehearsed in mock loads and reconciled to your control totals every time, with your finance team approving each load. How much history to bring is settled early and in the open.
Last updated
What comes across
Open items
Open purchase orders, supplier invoices and debtors, loaded over the cutover days and reconciled to legacy.
Opening balances
Loaded once the legacy March close is done, reconciled to your control totals and signed off with the auditors.
The asset register
Every asset and component, with cost, accumulated depreciation and life, mapped to its scheme, block and property during the load.
Suppliers and customers
Mapped once from the old finance system and any separate purchasing tool, de-duplicated and validated.
Master data
Mappings, customers and the reference data the new design needs, loaded and validated in every mock migration.
History
You choose how much comes across. Older detail can stay in legacy, read-only for audit, or in an archive your auditors can still search.
From profiling to the final load
Legacy data never goes straight into production. Migration runs in cycles, and each cycle is a full rehearsal of the real thing.
Steps, in order:
- Profile: Housing-aware rules, in the first weeks
- Exceptions checklist: Every issue listed, with an owner
- Fix at source: By the team that owns the data
- Mock loads: Each one reconciled before the next
- Final load: At cutover, after legacy stops
- Signed off: Opening balances approved by finance
Every cycle produces record counts, control totals and an exceptions report. Balances, open items, purchase orders and fixed assets are reconciled to agreed legacy reports. Large populations such as asset components are checked with automated validation plus sampled business checks.
Who does what
Who extracts what, in which format, and who cleanses which records is agreed jointly after the data has been profiled, so decisions rest on what is actually in the old systems.
PCL One
- Profiles the data with housing-aware rules and lists every exception
- Builds the extract, transformation and load, using Oracle migration tools
- Runs the mock loads and the final load, with a reconciliation pack for each
- Maps old codes to the new chart of accounts through the Finance One accelerator
Your team
- Agrees who runs which extract, and in which format, once the data is profiled
- Works through the exceptions checklist and fixes issues at source
- Names a data owner who signs off each reconciled load
- Decides how much history comes across, with audit and reporting needs in mind
The asset register, components and all
A housing association holds tens of thousands of properties, each split into components with their own cost, life and depreciation. Agreeing the component structure first reduces what has to move.
Steps, in order:
- Agree component structure
- Profile with housing rules
- Exceptions checklist
- Fix at source (assets team)
- Mock load
- Reconciled?
- Final load after legacy year end
- From “Reconciled?” to “Profile with housing rules” (No: issues found, next mock load)
- From “Reconciled?” to “Final load after legacy year end” (Yes)
Opening balances at the year boundary
With go-live on 1 April, legacy closes the old year and the new system opens the new one. Balances move once the legacy March figures are ready.
- The legacy system makes its final payment run, then activity is frozen
- Open purchase orders, invoices and debtors move with delta loads over the cutover, each with a signed reconciliation
- Rollback decision points are agreed before cutover starts
- Opening balances load once the legacy March close is done, reconciled to your control totals
- Your finance team approves the opening balances, and they are signed off with the auditors
Go live on 1 April: changing finance systems at the year boundaryFinance One integration acceleratorSee how the new chart is designed: chart of accounts transformation
Data migration: questions housing associations ask
Who extracts and cleanses the data for a new finance system?
Who runs which extract, in which format, how much history comes across and who cleanses which records is agreed jointly after the data has been profiled. PCL One profiles the data with housing-aware rules and lists every exception; your team fixes exceptions at source, owned by the team that owns the data. Migration and reconciliation are included in the implementation.
How much history should we migrate into a new finance system?
Bringing every year of history into a new ledger is rarely worth the cost. Most housing providers bring opening balances, open items, the full asset register and one or two years of summarised history, and keep older detail in an archive their auditors can still search. The answer is agreed with your data owners in discovery and written into the migration scope.
Can a housing asset register with components be migrated?
Yes. Each property is split into components such as roofs, kitchens, bathrooms and heating, each with its own cost, life and depreciation, and each mapped to its scheme, block and property during the load, not afterwards. Migration runs as two mock loads and a final load at cutover, every one reconciled to your control totals and approved by your finance team.
When are opening balances loaded after a 1 April go-live?
The legacy system makes its final payment run and closes the old year as normal. Open purchase orders, invoices and debtors move over the cutover with a controlled freeze and delta loads. Opening balances are loaded once the legacy March close is done, reconciled to your control totals and approved by your finance team, and signed off with the auditors.
Do our housing systems have to change to the new chart of accounts?
No. The housing management system and other source systems keep posting with the codes they already use. The Finance One accelerator maps those codes to the new chart of accounts in the integration layer, so the new ledger structure does not depend on changing every system that feeds it.
Know where your data stands
Tell us which systems hold your ledger, suppliers and asset register today. We will show you how the profiling, mock loads and reconciliations would run for your data.
PCL One (PayrollCloud Limited)
International House, 12 Constance Street
London E16 2DQ
United Kingdom