It rarely looks catastrophic on day one.

It looks like this. Claims go in and some come back rejected. Finance teams spend weeks trying to reconcile. Client statements are generated but do not match what carers actually recorded. A participant calls to question their balance and nobody can easily explain it, because the full history sits in a system that has been decommissioned. Then the Aged Care Quality and Safety Commission runs a prudential review, and the data they ask for is hard to produce cleanly.

This is not a hypothetical. The Commission is currently undertaking prudential reviews of Support at Home providers, focusing on financial management, reporting compliance and pricing practices. While the initial approach is education-led, enforcement action may follow if providers fail to address non-compliance.

It is happening now, to providers who treated the transition from Home Care Packages as a compliance task. It was a data migration. They did not treat it as one.

What actually has to move

When a provider transitions to Support at Home, the operational data that underpins day-to-day work has to carry over into a fundamentally different model. Client records. Care plans. Unspent fund balances. Budget histories. Provider relationships and subcontracting arrangements. Service delivery logs that will need to support itemised claims submitted to Services Australia.

Under the old HCP model, providers submitted a single monthly claim. The data behind it was relatively forgiving — if service records were slightly inconsistent, you could often reconcile manually and still get paid.

Under Support at Home, every service delivered must be mapped to a claimable funding category. Errors in service data cause claim rejections and payment delays. That is a completely different standard of data quality, and it is a standard that many legacy systems were never designed to meet.

The migration problem nobody talks about

When systems change, data does not automatically make sense in the new context.

An unspent HCP fund balance is a dollar figure. In Support at Home, it needs to map to a participant budget, a classification tier, and a care management account — three distinct things the old system may have stored as one. If the mapping is wrong, the opening balance in the new system is wrong. Clients are affected. Claims are affected.

Producing accurate monthly statements requires pulling data from multiple systems: rostering, timesheets, billing, and finance. Manual processes often require staff to compile reports across several platforms. For providers who built their operations around a single client management system under HCP, that coordination burden is new territory.

We have helped community health organisations migrate off legacy platforms — including TurnPoint and TrakCare — and what we find, consistently, is this: the migration completes without errors. The problems surface afterward. Not because the transfer failed, but because the data that transferred was already inconsistent — gaps, empty fields, records that nobody needed to fill in because the old model never asked for them. The migration does not create those problems. It just makes them visible, usually at the worst possible time.

CHSP providers: your window is now

The Commonwealth Home Support Programme will transition to Support at Home no earlier than 1 July 2027. That sounds like a comfortable runway.

The CHSP data landscape is typically more fragmented than HCP. More service types, more subcontractors, more variation in how data has been captured across different tools and teams across many years. Providers who think the 2027 date gives them time to wait are misreading which part of this work takes time. The audit takes time. The remediation takes time. The clean transition at the end is fast — if the work before it has been done.

What good looks like

The instinct is to trust the software vendor. They built the migration, ran the tests, confirmed the data moved. What they handled is technical transfer and field mapping. What they did not handle — and cannot — is whether the data in those fields was accurate or complete before it moved. That is a different job, and it belongs to the organisation.

An audit of the data before migration is where this starts. Not an audit of the system — of the actual records. What is populated, what is empty, what was never filled in because the old model never asked for it. A field that was irrelevant under HCP may be mandatory in an itemised SAH claim. Empty fields do not show up as errors during migration. They show up as rejected claims three months later, when someone is already stretched.

"Decommissioned" is also worth reading carefully. It means the system is turned off. It does not mean the data is gone — or that the need for it disappears. Client histories, fund transaction records, care plan notes: all of it may be required for audits, complaints, and continuity of care long after the transition. Where that data lives after the system is switched off, and whether it is actually retrievable when someone asks for it, is worth confirming before the question becomes urgent.

The underlying issue

The Support at Home reform is a bet by government that better data leads to better outcomes for older Australians. The itemised claiming model, the monthly participant statements, the quarterly financial reports — all of it is designed to create transparency that did not exist under HCP. That is a good bet. But providers can only benefit from it if their own data is good enough to support it.

SAH price caps land on 1 July 2026. From that date, every claim needs to be accurate, itemised, and traceable to a service record. For HCP providers already in the new model, the window to get on top of this is now. For CHSP providers watching from the sideline, the 2027 transition is closer than it looks — and the data work required is heavier. Start with an audit. Find out what you actually have before someone else asks you to prove it.

Written By: Bernard Herrok, proofed by AI.