Program Operations · Case Management
When your case management system works against you.
Bonterra ETO is one of the most widely deployed case management systems in LA nonprofits. It is also, based on verified user reviews spanning 2024–2026, frequently broken in ways that directly harm service delivery. The system freezes mid-session during client interactions, silently deletes case notes without warning so staff must reconstruct them from memory, and assessment screens time out without saving — meaning staff redo work they've already completed.
The problem
Documented failures and their operational costs.
The dysfunction doesn't end with the software. Customer support charges per-report to address bugs rather than resolving them under a service agreement. Orgs running three or more programs find the native reporting so weak that they maintain parallel spreadsheets alongside the system — defeating the purpose of having a system at all. When a new staff member joins, onboarding one person to Bonterra takes 72 hours of training time according to one documented case.
The realistic solution isn't replacing ETO — switching costs are too high and the data migration complexity is prohibitive for most orgs. What's buildable is a reporting connector that exports ETO data via CSV and transforms it into whatever funder format is required, eliminating the parallel spreadsheet. For orgs that have hit a genuine breaking point, a lean standalone case manager scoped to one or two program types and under 500 clients is achievable — plan for 4–6 months of focused part-time work minimum, longer if your reporting requirements are complex or migration from ETO is in scope.
- System freezes mid-session during active client interactions
- Case notes deleted silently — staff reconstruct from memory after the fact
- Assessment screens time out without saving, forcing rework
- Native reporting so weak that parallel spreadsheets are standard practice
- 72 hours of training time documented for one new staff onboarding
- Per-report support charges instead of bug fixes under a service agreement
How we approach this
Work around what's broken or replace it entirely — depending on where you are.
ETO reporting connector
Exports ETO data via CSV on a configurable schedule and transforms it into your required funder formats. Eliminates the parallel spreadsheet. Your data stays in ETO — this layer just makes it useful.
Funder template library
Each funder's required output stored as a mapping configuration. When the funder updates their template, one mapping changes — not every manual process. Supports HUD, city contracts, foundation templates, and Measure A.
Data quality dashboard
Surfaces missing fields, duplicate records, and stale case notes before a reporting deadline — not after. Program directors see data quality issues in time to fix them.
Lean standalone case manager
For orgs that have hit a genuine breaking point with ETO: a purpose-built replacement scoped to one or two program types and under 500 active clients. 4–6 months of focused part-time work minimum — longer if reporting requirements are complex or ETO data migration is in scope. Not a universal platform — scoped to what you actually need.
ETO data migration
Structured export and import of historical ETO records into a new system. Field-mapping documented and validated before any data moves. Note: ETO's data model is complex and migration fidelity depends on how consistently data was entered. We assess this before scoping.
Staff onboarding documentation
Plain-language process guides for your specific ETO configuration. When the 72-hour institutional knowledge problem hits again — and it will — the next person has a reference.
Related issues
ETO making your staff's job harder instead of easier?
Book a free 30-minute call. Tell me which ETO problems cost your team the most time and we'll identify whether a reporting connector addresses the issue or whether you've hit the point where a replacement is worth exploring.
Book a free discovery call