When one of Australia's largest superannuation administrators changed ownership in 2014, it triggered one of the most consequential data migration programmes the country's retirement savings sector had ever seen. Five of Australia's biggest industry superannuation funds — collectively holding more than $160 billion in retirement savings on behalf of nearly five million active members — needed to be migrated from a suite of interconnected legacy platforms onto a single modern administration system. Sequentially. Fund by fund. With zero tolerance for errors affecting member accounts.
Desda was engaged as ETL Project Manager across the full transition programme, leading the end-to-end data extraction, transformation, and load workstream. Desda also authored the governing data management strategy and data history policy that underpinned every fund migration — and held sign-off authority on the programme's overarching test strategy.
The Programme
Following the acquisition of the administrator, the incoming platform provider faced a formidable task: retire four interconnected legacy administration systems, migrate decades of member, employer, and transactional data for five of Australia's most significant industry funds, and do so in a sequenced programme spanning two years.
The five funds served workers across construction, hospitality, healthcare, transport, and a broad cross-section of industry — collectively making this one of the most member-critical migration programmes in the history of Australian superannuation. A failure at go-live would not just be a technology incident; it would directly impact the retirement savings of millions of working Australians.
- Four legacy source systems decommissioned across all five funds
- ~589,000 active employer records migrated
- ~397 million member transactions per year across the five funds
- 3.5 years of live transactional history migrated to active system per fund
- Full historical dataset migrated to a real-time enquiry archive
- Sequential fund-by-fund delivery, 2014–2016
The Scale in Numbers
To understand the magnitude of this programme, the data volumes alone tell a striking story. Across the five funds, the average annual transaction volume was approaching 400 million — meaning 3.5 years of live history represented well over one billion individual member transactions to be extracted, transformed, validated, reconciled, and loaded.
The programme's largest fund held more than two million active members, $81 billion in funds under management, and generated over 260 million transactions per year. For that fund alone, the ETL process at go-live required a continuous, uninterrupted processing window of 182 hours. The smallest fund in the programme — 265,000 members — still involved 22 million transactions over 3.5 years and its own 35-hour extraction and load window.
Beyond active members, the total record universe was significantly larger: more than 10 million inactive and exited member records also required migration, archiving, or disposition decisions as part of each fund's transition.
Desda's Role
Desda's principal was appointed ETL Project Manager for the Transition Programme — a role spanning not only the technical execution of data extraction and migration, but the programme governance, data strategy, cross-stream coordination, and risk management that determined whether each fund's go-live would succeed.
Desda authored two of the programme's most critical governing documents:
- The Data Management Strategy — the definitive document establishing the data quality framework for the entire programme. It defined what "migration-ready" data meant, how source-system validations would be replicated, how cleansing would be performed at source before extraction, and what reporting and governance mechanisms would track progress across all five fund migrations.
- The Data Transition and Configuration History Decision — the policy document that set out how many years of live transactional data would be carried forward into the active system versus archived, for each fund. This decision had direct compliance implications (No TFN tax refund obligations, MCS reporting, ATO lost member reporting), operational implications (backdated transactions, insurance premium recalculations), and contractual implications unique to each fund's trustee agreements.
Desda also held formal approver status on the Programme Test Strategy, ensuring quality assurance standards, defect governance, and testing phases aligned with the complexity and risk profile of a programme of this scale.
The Technical Approach
One of the defining features of this programme's data strategy was the decision to replicate the target platform's validation rules inside the source environment — enabling data quality issues to be identified and remediated before extraction, rather than discovered during or after loading. This approach significantly reduced migration failure rates and rework on the target system.
Validation and Reconciliation
More than 20 pre-, during-, and post-import validation types were applied per fund. These spanned member demographics (name, date of birth, gender, TFN, status), employment records (join dates, salary, leave), investment strategies (option validity, percentage integrity), beneficiary configurations (binding and non-binding), pension payment records, address integrity (Australian state/postcode combinations, mandatory fields), and employer data (ABN, registration, reference uniqueness).
Financial and non-financial reconciliation was executed source-to-target at go-live for each fund, with results crystallised before cutover was confirmed at each go/no-go governance gate. Go/no-go decisions took into account straggler volumes — records held in a post-migration holding status pending data cleansing — and these were tracked against operational capacity thresholds before each fund was declared live.
Data History and Archiving
One of the most consequential decisions in the programme was how much historical data to carry forward into the active administration system. Desda's Data Transition and Config History Decision document analysed fifteen distinct drivers — from No TFN tax obligations and MCS reporting requirements, to insurance premium recalculation volumes, rollback functionality constraints, and ATO lost member reporting obligations — and recommended a policy of three closed financial years plus the current open period as live transactional history.
All remaining historical data was migrated to a live archive system, providing operational staff with real-time enquiry access to member history beyond the active migration window. A further SQL-based archive repository preserved source data in its native form for developer-level query on request, ensuring complete historical integrity was maintained beyond what either the active platform or the front-end archive system could provide.
What This Programme Represented
In the history of Australian superannuation administration, programmes of this scale have been rare. The combination of member volume, transaction complexity, fund count, and legacy system diversity made this one of the most technically demanding data migration programmes the industry has produced. The stakes — retirement savings for nearly five million working Australians — demanded a standard of precision, governance, and data integrity that left no room for shortcuts.
Desda's involvement at the programme's centre — as ETL Project Manager, as the author of the data strategy and history policy, and as a governance approver on the test framework — reflects the depth of expertise and accountability Desda brings to the most complex assignments in the sector.
- ETL Project Manager across five sequential fund migrations, 2014–2016
- $160B+ in combined funds under management transitioned
- Over one billion member transactions extracted, transformed, and loaded
- Data quality strategy: cleanse at source, not mid-pipeline
- 3 trial loads + dry run + dress rehearsal per fund before go-live
- 20+ validation types applied pre-, during-, and post-import per fund
- Full archive migration preserving complete member history
- Author of the programme's governing data strategy and history policy
