Instead of Lumary
Tired of needing a Salesforce person to change Lumary? Own the system your supports run on.
We build your version around your SIL houses, your support coordination caseloads and the way your rostering team actually works, move your Lumary participant, worker and shift history across, and keep it running. One setup fee, then a monthly retainer.
Lumary publishes no price. Its website offers a demo or a conversation with its team, and the cost is quoted to each provider privately.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What a Lumary contract carries
A care platform built on a CRM platform, priced after a demo
Strip the layers away and a provider keeps a short list of records: who it supports, what each plan funds, who worked which shift, what was written up, what went wrong and what was claimed. Lumary builds those on Salesforce and adds its own modules for client care, workforce, finance and compliance, then prices the bundle one provider at a time.
A price you only hear in a sales call
The Lumary website lists demos, consultations and a contact form, and no figures. Comparing it with anything else starts with booking time with its team.
Two platforms in one system
Lumary describes itself as built natively on Salesforce. Your care records live inside a general sales and service platform, with Lumary's care modules on top of it.
Changes that wait for a specialist
One reviewer on Capterra said it can be hard to get the most from it without a Salesforce developer on site. A new field or a changed workflow can become a job for someone who knows the platform.
Four module areas to scope
Client and care management, workforce and rostering, financial control and revenue, and security and compliance are each presented as their own part of the platform.
An assistant that lives inside the vendor
Lumary now shows an assistant called Chrono. Whatever it does, it works inside Lumary's system and contract, not over records your organisation holds on its own terms.
Leaving means working through Salesforce exports
Getting years of participants, shifts and claims out runs through report exports or a bulk data export your administrator sets up, then a rebuild somewhere else.
What you keep instead
One provider record, in your hands, with the NDIS checks written in
Participants
Each person, their plan and how fast it is being spent
Plan details that tend to scatter across a CRM, a portal and a spreadsheet sit in one record you can question directly.
- check Service agreements followed from signing to end date, with spend compared to where it should sit today
- check Agency, plan and self managed participants kept apart, with plan managed claims routed to the plan manager
- check Plans running under pace named before the plan review
- check Supporting more participants never adds a licence line
Rostering
Shifts checked before anyone is sent out
The questions a rostering coordinator asks themselves are asked by the system for every shift.
- check A worker whose NDIS Worker Screening clearance has lapsed by the shift date cannot be rostered
- check No shift outside a signed, current agreement, and no worker in two places at the same time
- check A shift cannot be closed off until its progress note is written
- check Late cancellations record how much notice was given and follow the short notice claiming rule
Claims and incidents
Delivered supports turned into money, incidents closed the right way
Ask for the list in plain words and it comes back, with no report builder in between.
- check Every completed, noted shift with no payment request yet, oldest at the top
- check Bulk payment request files prepared at the agreed rate, ready to upload
- check A reportable incident stays open until the Commission notification is on file
- check Rejected claims hold their reason and stay on the list until resubmitted
Ownership
Change it by describing the change
No platform administrator in the middle: a field, a rule or a report is added by asking for it.
- check New support items, fields or compliance checks added in a sentence
- check Worker files, incident reports and participant statements printed under your own logo
- check Nothing is deleted: participants exit and claims stay for the seven years the rules require
- check Payroll and accounting tools can be connected to your own database where agreed
Make it yours
Design your own Lumary replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Lumary. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Lumary data across and run it for you.
Switching
How to switch from Lumary
The move involves exporting the records your account allows, mapping Lumary's columns to the import format, then checking the imported records against Lumary before you switch.
- 1
Export your records
Lumary runs on Salesforce, so records can come out through Salesforce report exports or a bulk data export your administrator can schedule. Export the participants, workers and shifts you want to bring across. Check with Lumary or your Salesforce administrator which export path and file format your account allows, often CSV or Excel.
- 2
Load a test import
Home Care for Claude Code imports records in a set format, so map Lumary's columns to that format before loading your data. Start with a test run if the import offers one, then review the result before loading the full set. Include the history you want to keep, rather than assuming every record or field will transfer automatically.
- 3
Review the import flags
Treat the import checks as a list to resolve, not as noise. The import can flag shifts without a covering service agreement and clients without a recorded funding type. Check each flagged record against Lumary, correct the field mapping or source data, and create any service agreements you need before relying on the imported shifts and records.
- 4
Run both systems briefly
Keep Lumary running while you check the new records against it. Compare participants, agreements, workers, shifts, notes, incidents and claims, and confirm that the records your team needs are present and make sense. Use this short side-by-side period to resolve mismatches before staff rely on Home Care for Claude Code as the main record.
- 5
Switch off Lumary
Once you have checked the records and your team is ready to work from the new database, make Home Care for Claude Code the system you use for ongoing work. Keep the exports and any Lumary access you still need for reference, then end Lumary only when you are satisfied the move is complete.
Where the real effort goes
The main work is mapping Lumary's fields to the import format and deciding how much history to bring across. Your service agreements and the quality of your source records also affect what the import flags. If Enterprise DNA handles the move, they do the mapping and the side-by-side check against Lumary.
Not ready for a call?
Get your Lumary switch plan by email
We will send you the step-by-step plan for moving your business off Lumary, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Lumary switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to switch
Take the free version, or let us build and run yours
Open source
Run it yourself
Free
- 1 Clone the repo from GitHub and run npm run demo
- 2 Open the folder in Claude Code and type /attention
- 3 Export your participant, worker and shift lists from Lumary as CSV reports, or ask your Salesforce administrator for a data export
- 4 Ask Claude Code to map the Lumary columns to the import, then load your own records
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a monthly retainer
- check We pull your records out of Lumary, map them across and compare them with Lumary before you switch it off
- check We shape it around your services: SIL and SDA houses, support coordination, community supports
- check We add a worker phone app or web screens where your team needs them
- check It runs inside Omni, our managed Command Centre, next to the rest of your business
Questions
Instead of Lumary, answered
Lumary is built for disability providers. Why would we leave it? expand_more
It is, and it is also a Salesforce system, which means two layers of platform, and changes that can need a Salesforce specialist. If your week is participants, agreements, shifts, notes, incidents and claims, that is exactly what this holds, in a database you own, and changes are made by describing them. If you depend on clinical or allied health records, we tell you on the call what stays outside the free version.
How hard is it to get our data out of Lumary? expand_more
Because Lumary runs on Salesforce, records come out as report exports or a bulk data export your administrator can schedule. The free version imports a set format, so Lumary's columns need mapping first. When Enterprise DNA handles the move, the mapping and the side-by-side check against Lumary are ours to do.
What about SCHADS award interpretation and payroll? expand_more
The free version keeps the shift record, not the pay calculation. Enterprise DNA connects your version to the payroll or award interpretation tool you already use, working from the same shift records your coordinators see.
Our support workers use a phone app today. What do they use instead? expand_more
The free version has no worker phone app yet. If your workers need to see their shifts and write notes from the road, Enterprise DNA builds that into your version, reading and writing the same database your office uses.
Does it meet the NDIS rules? expand_more
It keeps the record-keeping shape the NDIS rules describe: screening checked before rostering, a note before a claim, rates held at the agreement, Commission notification before an incident closes, and no deletions. Each rule names its source. Deciding whether an incident is reportable is still your call, and nothing here is legal advice.
See what your Lumary setup really costs you
Bring your Lumary contract and a list of what your coordinators and rostering team open every day. In 30 minutes with Sam we go through what you pay each year for Lumary, who you rely on to change it, and what your own system would look like with your houses, caseloads and funding in it. If it fits, we build it and run it. If it does not, the free version is yours to keep.
Home Care for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Lumary?
Get your version built