Migration playbook
Switch from Lumary to CareOS
Migrate from Lumary to CareOS for transparent per-program pricing, native aged care and allied health, and faster time to value.
Typical timeline: 6 weeks · Built for Australian funding rules · No disruption to active claims
Why providers switch from Lumary
- Enterprise rollout has stalled or change-management cost is unsustainable
- You need aged care SIRS / Quality Standards or allied health practice tools natively
- Total cost of ownership has grown with modules and configuration
- You want a single person record across programs you actually run
Migration playbook
- Step 1
Program map and scope (weeks 1–2)
We document the disability workflows you actually use in Lumary, then map them to CareOS modules. Anything you do not use today is not migrated.
- Step 2
Person, plan, and enrollment migration (weeks 2–4)
Participants, plans, budgets, goals, and active service bookings are exported and imported with full traceability. PACE participants are validated against current claim status.
- Step 3
Rostering and SCHADS cutover (weeks 4–6)
Roster templates, SCHADS configuration, and shift patterns rebuild in CareOS with parallel validation on one pay cycle before live cutover.
- Step 4
Add aged care or allied health on the same record (weeks 6+)
Where a second program is in scope, HCP/CHSP enrollment or AlliedHealthEpisode attach to the same Person — no separate platform fee.
Common questions
- Will switching from Lumary disrupt active PACE claims?
- No. We migrate after a fortnightly claim batch completes and only redirect submissions once the next batch is queued in CareOS with pre-validation.
- Is CareOS suited to large multi-site organisations?
- Yes. CareOS supports multi-site organisations with site-aware rostering, scoped permissions, and centralised compliance — without an enterprise-class rollout.