They braced for months. The switch took a week.
An ABA practice that dreaded leaving its old software — clients, data, and open claims, all of it
This is the story of an ABA practice that stayed on software it had outgrown for far longer than it should have — for one reason that has nothing to do with the software itself: the fear of switching. We've kept them anonymous, but the dread will be familiar to anyone who has ever thought "we need to move off this" and then talked themselves out of it.
The real reason practices stay stuck: the move, not the tool
Ask an owner why they haven't left a system everyone complains about, and the answer is rarely "it's fine." It's "switching would be a nightmare." The whole client roster. Years of clinical history. Authorizations. Open claims with money still in them. Retraining a high-churn front-line staff. The imagined month of running two systems in parallel while something quietly breaks. The pain you know starts to feel safer than the move you don't.
So the practice waited — absorbing the daily friction because the one-time cost of moving felt enormous and unknowable. That's the trap: the fear of switching is almost never measured, so it grows.
What they braced for
Going in, they expected the worst version: months of overlap, a data migration they'd have to project-manage themselves, claims falling through the cracks during the handoff, and a team in limbo learning a new tool while still living in the old one. Every horror story they'd heard about software migrations, stacked on top of a practice that couldn't afford to stop running for a single day.
What actually happened: about a week
The move was not the months-long ordeal they'd braced for. Wilma ran the migration — and brought the things they were most afraid of losing across with them:
- Clients, history, and the graphs. The client roster, the clinical history, and the data-collection graphs all came across — so clinicians see what happened in the old system right inside Wilma, instead of keeping a window open on the platform they're trying to leave.
- Open claims. Claims still in flight came across too, so revenue already in motion didn't get stranded in the gap between two systems.
- Billing set up to actually go through. The move included getting the billing configuration right — payers, codes, the details that decide whether a claim pays — so claims went out clean from the start instead of bouncing while the team "learned the new system."
- Configured to your workflows, not the software's. The setup followed the way the practice already works, rather than forcing the team to reinvent their process to fit the tool. The software bent to the practice, not the other way around.
- Your templates, your standards. Note and documentation templates were customized to the standards the practice had already set — so the quality bar they'd worked hard to build carried over intact, on day one.
- Wilma did the lifting. All of it was a migration Wilma ran, not a project the practice was handed and left to figure out alone.
And all of it — the data, the billing setup, the workflow and template configuration — inside the same week. Not the quarter of disruption they'd talked themselves into.
"Honestly, we expected this to take months. We were fully moved over — clients, data, our graphs, open claims, all of it — in about a week, set up the way we already work. That was the part that genuinely surprised us." — Practice owner
You don't just land where you were — you land ahead
Here's the part that reframes the whole calculation: switching to Wilma isn't a lateral move that costs you a week to end up exactly where you started. You come out with capabilities the old setup never gave you — in that same week. This practice, for instance, gained a real company phone line with IVR — a proper business number with an auto-attendant, plus recording and transcription, ringing through to the phones staff already carry, without buying a separate phone system. The migration wasn't just "don't lose what we have." It was "and now we have more."
Why it's faster than almost anyone expects
The dread is real, and it's fair to be skeptical — most people have only ever heard migration horror stories. But the horror stories usually come from being handed an export file and left to reconcile it yourself. When the move is run for you — the roster, the history, the claims brought across as a managed migration rather than a DIY scramble — the timeline collapses to something most owners flatly don't believe until they've seen it.
An honest note on scope
"About a week" was this practice's experience, and it's a fair picture of how fast a switch can go — but it isn't a stopwatch promise for everyone. A larger practice, or one with messier or more unusual data, can take longer. The point isn't a guaranteed number; it's that the move is a managed migration Wilma runs with you, not a months-long project you're left to survive alone. The fear is almost always bigger than the reality.
The results
- Clients, clinical history, and data-collection graphs migrated — no keeping the old system open just to look things up
- Billing configured to go through clean, and the setup shaped to the practice's existing workflows and note standards — not reshaped to fit the software
- The whole switch completed in about a week, not the months they'd braced for — with no long parallel-running of two systems waiting for something to break
- New capability on day one, like a company phone line with IVR — the move was an upgrade, not a lateral shift
The names are hidden. The pattern isn't: a lot of practices stay on tools they've outgrown because the move feels unsurvivable — and never find out it isn't. The thing they were afraid of turned out to be smaller than the thing they were living with every day. It's the same lesson as leaving click-heavy clinical software: the daily pain you've normalized is usually the bigger cost.
Frequently asked questions
How long does it really take to switch to Wilma?
For the practice in this story, about a week — start to finish, including their clients, clinical history, and open claims. That isn't a universal guarantee: larger practices or messier data can take longer. The reason it's fast is that Wilma runs the migration with you rather than handing you an export file to reconcile yourself.
Will I lose my historical client data if I switch?
No — that's the fear, and it's the thing the migration is built to protect. Your client roster, the clinical history, and your data-collection graphs come across, so clinicians can see what happened in the old system right inside Wilma — no keeping the old platform open just to look things up.
Will switching force us to change how we work?
No — the setup is configured to the workflows your practice already runs, rather than making you reinvent your process to fit the software. Your note and documentation templates are customized to the standards you've already set, so the quality bar you built carries over intact. The software bends to the practice, not the other way around.
Do we just break even on a switch, or do we gain anything?
You come out ahead. Beyond keeping your data and history, the same migration week can add capability you didn't have — for example a company phone line with IVR (a real business number with an auto-attendant, recording and transcription, ringing through to the phones staff already carry, no separate phone system to buy). The move is an upgrade, not a lateral shift.
What happens to claims that are still in flight when I move?
Open claims come across in the migration, so revenue already in motion doesn't get stranded in the gap between two systems. Money in flight is one of the biggest switching fears, and it's exactly what the managed move is meant to carry over.
Do I have to run two systems in parallel for months?
No. The dread of a long, overlapping cutover is the horror-story version of switching. Because Wilma runs the migration, the move is measured in days-to-weeks for most practices, not a quarter of running everything twice.
Isn't it risky to switch while we're still operating every day?
It feels risky, which is why so many practices stay put. But the migration is something Wilma manages with you — the roster, the history, the claims — so you're not stopping operations or project-managing a data export alone. The fear is almost always bigger than the reality.