How to Switch NDIS Systems: A Step-by-Step Guide for Providers

Most NDIS providers who stay on software that doesn’t fit aren’t short on reasons to leave. They’re short on time, and the switch feels bigger than the problem.

It doesn’t have to be. Switching NDIS systems is a project with a clear set of steps, and most of the risk comes from a handful of predictable mistakes. Get the order right, plan payroll carefully and keep your data clean, and the move is far more manageable than it looks.

This guide walks through how to switch NDIS systems well, whichever platform you’re moving to. It’s built from what we’ve learned moving providers onto Appoyo, but every step applies to any move.

Free download

The Appoyo Migration Plan

Every task in a system switch, broken into six phases, with who does what and when. Use it as your checklist, whichever system you choose.

Before you start: be clear on why you’re switching

A switch goes better when everyone knows what it’s meant to fix. Before you talk to vendors, write down the problems your current system causes: rostering that takes hours, billing that needs double handling, payroll errors, compliance evidence scattered across folders.

Then record an admin-hours baseline. Estimate how much time your team spends each week on rostering, billing, payroll, onboarding and compliance. It takes an hour to put together, and it’s the only way to prove the switch paid off once you’re live.

Decide how much of the move you want to do yourself

Before you plan anything, decide who does the work. Most software vendors offer some version of three approaches:

Be honest about your team’s capacity. Choosing the cheapest option and then running out of time mid-migration costs more than paying for help up front. Ask every vendor exactly which tasks each option includes, because “implementation” means very different things to different providers.

The six phases of switching NDIS systems

A well-run switch typically takes around eight weeks from kick-off to settled. Smaller, single-site providers can move faster. Larger or more complex providers take a little longer. The phases overlap on purpose, so training starts while data is still loading and no step holds up the next.

Phase 1: Scope and plan

Nothing should move until you’ve mapped what you have and agreed where it’s going.

• Map your current setup. List every function your current system handles, every integration it connects to (accounting, messaging, clock-in tools) and every workaround your team uses outside it.
• Name an owner on both sides. One person inside your organisation and one named contact at the vendor. Migrations without a clear internal owner are the ones that drift.
• Lock your go-live date around payroll. Set go-live to the first pay cycle of a month. It gives payroll a clean cut-off and avoids splitting a pay period across two systems. More on this in Phase 5.
• Check your current contract. Find your notice period and data export terms now, not in week seven. Missing a notice window can mean paying for both systems for months.
• Plan your communications. Staff, participants, plan managers and support coordinators all need to know what’s changing and when. Prepare the messages early.

Phase 2: Configure the new system before loading data

Configure first, migrate second. Data loaded into a system that isn’t set up properly lands in the wrong places and has to be fixed twice.

• Structure and access. Employee groups, access levels and business unit or site segregation.
• Payroll. SCHADS award interpretation, pay levels, penalty rates, allowances and leave rules, so pays are right from the first run.
• Billing. Your price book, NDIS support line items and invoice templates.
• Claiming continuity. Claims to the NDIA and plan managers must carry on without a gap. Confirm this is set up and tested before go-live.
• Finance. Cost centres, tracking categories and your accounting integration mapped to your chart of accounts.
• Documents. Forms, service agreements, policies and letter templates rebuilt in the new system.
• Integrations. Messaging, email and time capture tools connected and tested.

Phase 3: Export, migrate and reconcile your data

This is the phase providers worry about most. The rule is simple: export once, load clean, reconcile before you go live.

Getting your data out. Your service agreement with your current vendor should set out how you get your data back. Most platforms export to CSV or Excel. Only you can request your data from your current vendor, so start this early. Ask your new vendor for the exact list and format they need, so you only have to ask once.

Your export checklist:

• Participant details, contacts and key relationships
• Plan manager and support coordinator details
• Participant budgets and funding periods
• Rosters, ideally from your NDIS Roster of Care (ROC) spreadsheet
• Care plans, goals and risk assessments
• Participant documents, forms and compliance records
• Employee profiles, credentials and compliance documents, including expiry dates
• Incident history
• Price book and billing setup
• Payroll year-to-date figures, leave balances and super details

Clean before you move. Archive inactive participants and former staff, fix duplicates and update expired credentials before the export. Migration is the cheapest time you’ll ever have to clean your data.

Use your Roster of Care. Your ROC spreadsheet already holds most of what you need to build participant profiles and rostered shifts. A good system will import it directly and save hours of re-entry.

Reconcile and sign off. Compare participant counts, budgets and employee records against the old system before anyone relies on them. Don’t go live until someone has signed the data off.

Agree a rule for open items. Decide in advance what happens to anything open on go-live day: shifts in progress, unclaimed invoices, open incidents. This is where things most often fall through the gap.

Keep your incident history. Export historical incidents and store them in the new system or a secure archive, then record all new incidents in the new system from go-live.

Free download

Get the full task list

The Appoyo Migration Plan lists every configuration and data task in this guide, phase by phase. Download it and use it to run your move.

Phase 4: Train your team while data loads

Don’t leave training until go-live week. Run it alongside the data migration so your team is ready, not rushed.

• Train by role. Rostering, participant management, HR and recruitment, and payroll and billing teams each need different sessions.
• Keep it short for support workers. Most support workers only need the mobile app. A short video guide gets them confident quickly without pulling everyone into long sessions.
• Build a library you keep. Recorded videos and step-by-step guides pay off long after go-live, every time you onboard a new starter.

Phase 5: Go live and cut over payroll

Payroll is the riskiest part of any switch, so plan it most carefully.

Pick the first pay cycle of a month. Your old system stays the record up to that point, and the new system runs everything from that cycle onwards.

• One source of truth at a time. Avoid running live operations in two systems at once. That’s where records start to disagree.
• Carry over year-to-date balances. So Single Touch Payroll (STP) and super reporting continue without a break.
• Work through a go-live checklist. Confirm every area is configured, reconciled and tested before you switch.
• Run your first pay run with support. Have your vendor alongside you for the first pay.
• Consider a parallel pay check. For extra assurance, calculate your first pay in both systems and compare results before staff are paid.

Phase 6: Settle in and switch the old system off

• Expect a hypercare period. Priority support through the first full month and first pay cycle while your team finds its feet.
• Measure against your baseline. Compare admin hours now to the baseline you set before the switch. That’s your return, in numbers.
• Decommission the old system. Once data is validated and you’ve run cleanly, cancel the old subscription so you stop paying twice.
• Archive old records. Keep old system data archived and read-only so you meet your record-keeping and audit obligations.

Common mistakes to avoid when switching NDIS systems

1. Moving messy data. Duplicates and expired records carried across become problems in your new system.
2. Going live mid-pay-cycle. Splitting a pay period across two systems creates reconciliation work and payroll errors.
3. Training everyone in go-live week. Staff learn under pressure and make avoidable mistakes.
4. Forgetting the people outside your team. Plan managers and support coordinators need to know about new invoices and contact points.
5. Missing the notice period. Check your old contract early or pay for two systems longer than you need to.
6. No internal owner. Someone inside the organisation has to own decisions and deadlines.
7. No baseline. Without one, you can’t show the board or your team that the switch was worth it.

Questions to ask any vendor before you switch

• Who will be our named contact through the migration?
• Exactly which tasks do you do, which do we do, and which do we do together?
• What format do you need our data in, and will you load it for us?
• How do you make sure NDIA and plan manager claiming continues without a gap?
• How do you handle payroll cut-over, STP and year-to-date balances?
• Will you run our first pay run with us?
• What training is included, and do we keep the videos and guides?
• What support do we get in the first month after go-live?
• What is a realistic go-live date for an organisation our size?

How Appoyo does it

When providers first saw Appoyo, the feedback was consistent: they wanted the efficiencies, but moving from their old system felt too hard and they didn’t have the time or resources. So we built our setup, configuration, training and data migration into one plan, around the six phases in this guide.

• Three ways to move. Done By You, Done With You and Done For You. Choose how much you take on and how much we take off your hands.
• Done For You means exactly that. Send us your old data and we configure, load, build, test and hand you a live system.
• A named migration lead who owns your move from start to finish.
• Go-live on your pay cycle, with your first pay run completed with you on every package.
• Built for NDIS and aged care, with SCHADS award interpretation, NDIS line items, claiming and Xero set up for you.
• Around eight weeks for a standard move, with a written plan and go-live date you can hold us to.

We move providers from ShiftCare, Lumary, FlowLogic, other care management platforms and spreadsheets. For more on how we take the pressure off your team, read Switching NDIS Software Doesn’t Have to Be a Huge Project.

Free download

Download the Appoyo Migration Plan

See every task in an Appoyo move, who does it under each package, and how we de-risk the switch. Free to download.

Frequently asked questions

How long does it take to switch NDIS systems?

A standard switch takes around eight weeks from kick-off to settled, with go-live typically around week five. Smaller providers can move faster and larger multi-site providers may take a little longer.

Can we get our data out of our current NDIS software?

Your service agreement should set out how you get your data back, and most platforms export to CSV or Excel. Only you can request it from your current vendor, so start early and ask your new vendor exactly what they need.

When is the best time to switch?

Go live on the first pay cycle of a month so payroll has a clean cut-off. Avoid scheduling go-live during busy periods such as end of financial year payroll finalisation or an upcoming audit.

Should we run both systems at the same time?

Not for live operations. Keep your old system as the record up to your cut-over date and run everything in the new system after it. For extra assurance, you can run a parallel check of your first pay before staff are paid.

Do support workers need much training?

Usually not. Most support workers only use the mobile app, and a short video guide is enough for most to get started.

What happens to our incident history?

Export your historical incidents and store them in the new system or a secure archive, then record all new incidents in the new system from go-live.

Can Appoyo move us from ShiftCare, Lumary or FlowLogic?

Yes. We move providers from other care management platforms, spreadsheets and older systems using the same six-phase plan.