The Software Migration Cycle Nobody Plans For
Every ABA practice starts small. Maybe it is a single BCBA with a vision, a handful of clients, and a kitchen table doubling as a home office. At this stage, the tools are simple: a spreadsheet for scheduling, a basic billing system, maybe a free data collection app. It works because the complexity is low and the volume is manageable.
But then something wonderful happens — the practice grows. And with growth comes a painful realization: the tools that got you here cannot get you where you are going. What follows is a cycle that plays out across the ABA industry with remarkable consistency. Practices migrate their software stack an average of two to three times over their first five to seven years, and each migration is more painful than the last.
Understanding this cycle — and planning to avoid it — is one of the most consequential strategic decisions a practice owner can make.
Phase 1: The Startup (1 to 3 Providers)
In the beginning, simplicity wins. A new practice needs to get clients, deliver services, and bill accurately. The software requirements are minimal: basic scheduling, session notes, and claim submission. Many founders start with consumer-grade tools — Google Sheets for scheduling, a standalone data collection app, a basic clearinghouse for billing.
This works for a reason. When you have three providers and 15 clients, the overhead of a full practice management system seems like overkill. You can keep track of authorizations in your head. You know every client by name. Your billing person (probably you) can manually check every claim before submission.
The cracks start showing when:
- You cannot easily see which authorizations are approaching expiration across your growing caseload
- Scheduling changes require updating multiple disconnected systems
- Your billing person spends more time on data entry than on actual billing work
- Reporting means exporting data from three different systems and combining it in a spreadsheet
- A new hire asks where to find information and the answer is "it depends on what you need"
For most practices, this breaking point arrives somewhere between three and five providers. The manual workarounds that were manageable at two providers become unsustainable at five.
Phase 2: The First Real Software (3 to 10 Providers)
At this stage, the practice invests in a dedicated ABA practice management platform. This is a significant decision — it involves evaluating vendors, migrating existing data, training staff, and changing workflows. The selection process typically focuses on the features the practice needs right now: session documentation, basic scheduling, insurance billing, and maybe a parent portal.
For a while, this works well. Having a centralized system is a dramatic improvement over the spreadsheet era. Staff can find information in one place. Billing is faster. Scheduling is less chaotic.
But between 8 and 15 providers, new problems emerge:
- Multi-location limitations: The practice opens a second location or serves a different region, and the software was not designed for multi-site operations. Reporting is site-specific. Staff cannot easily work across locations. Administrative overhead doubles.
- Reporting gaps: The built-in reports cover the basics, but practice leadership needs more sophisticated analytics — utilization by payer, revenue per provider, authorization burn rates, cancellation trends. Exporting data to Excel for custom analysis becomes a weekly ritual.
- Billing complexity: As the practice contracts with more payers, the billing requirements get more complex. Different payers have different rules for authorization formats, modifier requirements, and documentation standards. The software handles the common cases but struggles with exceptions.
- Credentialing at scale: With 15 providers, tracking certifications, licenses, supervision requirements, and insurance credentialing manually is no longer feasible. The current system either does not support credential management or handles it as an afterthought.
- Role-based access: The practice now has clinical directors, office managers, billing specialists, and administrative staff — each needing different levels of access. Basic permission systems that worked with a flat team structure are insufficient.
The practice owner faces an uncomfortable truth: the software they chose two years ago, the one they spent months evaluating and implementing, no longer fits. It is time to migrate again.
Phase 3: The Painful Middle Migration (10 to 20 Providers)
The second migration is significantly harder than the first. When you moved from spreadsheets to your first platform, you did not have much data to lose. Now you have years of clinical records, billing history, authorization documentation, and reporting data. Moving all of this to a new system is a massive undertaking.
The true costs of mid-stage migration include:
- Data migration: Moving client records, session data, billing history, and authorization information between systems is error-prone and time-consuming. Industry data suggests that data migration projects for mid-sized ABA practices take three to six months and frequently encounter data integrity issues.
- Staff retraining: Every staff member needs to learn new workflows, new interfaces, and new processes. During the transition period, productivity drops as people navigate the learning curve. Practices report a 15 to 25 percent dip in billable hours during the first month after a software migration.
- Lost historical data: Not everything migrates cleanly. Formatting differences, field mapping mismatches, and data structure incompatibilities mean that some historical data is lost or degraded during migration. Custom reports that relied on historical trends may need to be rebuilt from scratch.
- Dual system operation: During migration, you typically run both systems simultaneously — the old one for historical reference and the new one for active operations. This doubles your software cost for the transition period and creates confusion about which system is the source of truth.
- Consulting and implementation fees: Most mid-tier and enterprise platforms charge implementation fees ranging from $5,000 to $50,000, depending on the complexity of your setup. Add data migration consulting, custom configuration, and training, and the total transition cost can reach six figures.
- Opportunity cost: The months your leadership team spends managing a software migration are months they are not spending on clinical quality, growth strategy, staff development, or client acquisition. This is perhaps the most significant and least quantified cost of migration.
Phase 4: The Enterprise Question (20+ Providers)
Practices that reach 20 or more providers need enterprise-level capabilities: advanced analytics dashboards, API integrations with external systems, sophisticated permission hierarchies, multi-entity billing, custom workflow automation, and robust compliance tooling. If the Phase 3 platform does not offer these capabilities — or offers them as expensive add-on modules — the practice faces the prospect of yet another migration.
By this point, the cumulative cost of serial migrations is staggering. Three software transitions over five to seven years, each costing tens of thousands of dollars in direct expenses and months of lost productivity. The practice has paid the switching cost three times when it could have been avoided entirely.
The Alternative: Choose for Scale from Day One
The serial migration pattern is not inevitable. It happens because practices choose software based on what they need today rather than what they will need in two, three, or five years. The short-term savings of a simpler, cheaper platform are real — but they are dwarfed by the eventual cost of outgrowing it.
The alternative approach is to select a platform from day one that is designed to scale across the full growth trajectory of an ABA practice. This does not mean buying the most expensive or feature-heavy system available. It means evaluating software with a different set of criteria.
What to look for in a scalable platform:
- Features that unlock as you grow: The best platforms give you what you need now without overwhelming you, but have enterprise capabilities built in and ready when you need them. You should not have to migrate to access advanced features — they should be available on the same platform you started with.
- Multi-location architecture from the start: Even if you have one location today, choose a system built for multiple sites. The underlying data architecture matters — bolt-on multi-location support is never as clean as native support.
- Role-based permissions that scale: A system that supports five permission levels today should support 50 custom roles tomorrow. As your organizational structure becomes more complex, your software should accommodate that complexity without workarounds.
- Reporting and analytics depth: Basic reports are table stakes. Look for platforms that offer advanced analytics, custom report builders, and real-time dashboards that evolve as your data and questions become more sophisticated.
- Single database architecture: Systems built on a single unified database — where scheduling, billing, clinical data, credentialing, and HR all share one source of truth — are inherently more scalable than systems that bolt together separate modules. Data consistency, reporting accuracy, and operational efficiency all improve when there is one database rather than several.
- API access and integration capabilities: As practices grow, they inevitably need to connect their practice management system with accounting software, HR systems, analytics platforms, or custom tools. API access ensures you can extend the platform without replacing it.
The Growth Mindset Applied to Software
Practice owners invest enormous energy into growth strategy — marketing, hiring, clinical program development, payer contracting. But the operational infrastructure that supports growth often receives less strategic attention. Choosing practice management software is not an IT decision. It is a business strategy decision that compounds over years.
The practices that scale most smoothly are the ones that made their software decision with scale in mind from the beginning. They chose platforms built on unified architectures, with features that grow alongside the practice, and pricing models that do not penalize success.
Platforms like Wilma are specifically designed for this trajectory — giving startup practices the simplicity they need on day one while providing the enterprise capabilities they will need at 20 or more providers, all on a single platform with no migration required. The goal is simple: choose once, grow forever.
If you are in the early stages of your practice, invest the time now to evaluate for where you will be in five years, not just where you are today. The decision you make about software infrastructure will either accelerate your growth or become the bottleneck that slows it down. Choose accordingly.