Your Practice Management Software Is Older Than Your Newest Associate
William “BJ” Pote
CEO, eTop Technology
A lot of the software running law firms today was designed before the smartphone existed. Some of it before broadband was common.
That is not automatically a problem. Old software that does the job correctly is often better than new software that does it approximately. But it does mean that general IT advice, most of which assumes modern cloud applications, is frequently wrong when applied to your firm.
What “legacy” actually means here
It is not about the year on the box. It is about architecture. Legal practice management, billing and accounting systems commonly share a set of traits:
They expect a file server. The application on the desktop and the data on a server, talking constantly. That relationship is sensitive to latency, which is why these applications feel instant in the office and unusable over a VPN.
They have their own database engine. Not a modern managed database. Something specific to the product, sometimes an engine most IT people have never touched.
They are licensed per workstation, with matching versions. Update the server, and every workstation has to move too. Miss one and that user gets errors nobody else sees.
They assume Windows, permanently. Which constrains what you can do with tablets, Macs, and anything web-based.
Their upgrade paths are narrow. You often cannot jump from an old version to the newest one directly. You have to step through intermediate versions in order, and skipping steps is how firms lose data.
Most firms are already running both, and that is the real situation
The tidy version of this discussion pretends a firm is either on old on-premise software or modern cloud software. In practice almost every firm we support is running both at once, and often has been for years.
A cloud case management system for matters and documents. A traditional on-premise package for billing and trust accounting, because that is where the history lives and nobody wants to migrate ten years of financial records. Sometimes a third, older system still running because one practice area depends on it.
That is a perfectly reasonable position to be in. What matters is recognizing that the two halves fail in completely different ways, and need different attention.
The cloud half fails at the edges. The service itself is rarely down. What breaks is the connection between it and the desktop: document handoff to Word, email linking in Outlook, add-ins after an Office update. Managing that means managing workstations.
The on-premise half fails in the middle. Server problems, version mismatches between machines, database limits, update failures. Managing that means managing servers and being extremely careful about updates.
A provider who only understands one of those will do a poor job on the other. It is worth asking directly which one they are better at.
Why “just move it to the cloud” is usually wrong
It is the advice every firm gets and it means at least three different things.
Move to a cloud-native product. Replace your system with a browser-based one. This is genuinely good if a product exists that fits your practice. It is also a full data migration, retraining, and a period where nobody can find anything. Real option, big project, and not something to start in your busy season.
Host the same software on a server in a data center. Your existing application, running on a machine you do not own. This is what most firms actually mean, and it works well. Performance is protected because the application and database stay together, and remote access becomes the normal way of working rather than a compromise.
Put the files in cloud storage and keep the app local. This is the one that sounds cheapest and causes the most damage. Practice management databases generally must not live in a consumer file-sync folder. Sync tools are designed for documents, not for a database being written to by six people at once, and the result is corruption that is slow to appear and painful to unwind.
If somebody proposes moving your case management data into a file-sync folder, that is the moment to get a second opinion.
The honest framework
If the software still fits how you practice, keep it and modernize around it. Put it on a properly specified server, publish it so people can work remotely without a VPN, back it up in a way you have tested, and update it carefully and rarely. This is the cheapest good answer and it is the right one for most small firms.
If the software is genuinely holding you back, replace it deliberately. Not during a busy period, not without a data migration plan, and not without knowing what happens to your history.
Never let the decision get made accidentally. The worst outcomes come from firms that never chose. The vendor stopped supporting the version, an update went wrong, or a server died, and now they are migrating under emergency conditions with no plan.
The three questions worth answering this year
What version are we on, and is it still supported? A surprising number of firms cannot answer this. If your version is out of support, you have a deadline whether you have acknowledged it or not.
What does our upgrade path look like? Not whether you can upgrade. What the specific sequence of steps is, and whether any of them cross a database engine, because those are the risky ones.
If the server holding this died tonight, what is the plan? Answering that will tell you more about your firm’s risk than any security assessment.
Old software is a manageable condition. Old software nobody has thought about is a countdown.
Related reading
William “BJ” Pote
CEO, eTop Technology
eTop Technology has spent over 15 years in IT and over 12 years serving the Inland Empire as a trusted managed IT provider. We host the Business Tech Playbook podcast and are passionate about helping business leaders make smarter technology decisions.