Many firms are running a PCLaw version that was installed years ago and has worked well ever since. Then a notice arrives saying the version is no longer supported, and it is not clear whether that is a real problem or a sales message. Here is what it means.
How PCLaw versions work now
PCLaw is published by PCLaw | Time Matters, and it is now released as yearly versions, such as PCLaw 2024 and PCLaw 2025, in two editions:
- PCLaw, which uses the c-tree database, for smaller firms.
- PCLaw Enterprise, which uses Microsoft SQL Server, for larger ones.
Each release is supported for a limited period and then retired. At the time of writing, the vendor's published schedule showed support for the 2023 releases ending on December 31, 2025, and for PCLaw 2024 and PCLaw 2025 at the end of 2026. These dates change as new versions come out, so check the vendor's list of currently supported versions for the current position.
To see what you are running, open the Help menu in PCLaw and choose About.
What "end of support" actually means
It does not mean PCLaw stops working on that date. It means the vendor will no longer:
- Answer support calls for that version
- Fix bugs in it
- Update it for new releases of Windows, Windows Server or SQL Server
- Update built-in tax tables, forms and integrations
Your data stays yours, and the software keeps running for as long as its environment does not change.
The real risks of staying put
Windows moves on. A Windows update or a replacement computer can stop an old version from working, with no fix available. This is the most common way an unsupported version turns into an emergency.
Security. Old versions often depend on old components and old operating systems that no longer receive security updates. For a firm holding client funds and confidential files, that matters, and insurers are increasingly asking about it.
Integrations stop. Links to payroll services, payment processing and other software break when the other side changes its requirements.
The upgrade gets harder every year. Moving up one version is routine. Moving up many versions at once may have to be done in stages, on data that has not been checked in years.
Help is harder to find. Fewer people know the old versions well.
Your options
1. Upgrade to the current version. The straightforward route if the firm is happy with PCLaw. It needs an active plan with the vendor, a check of the system requirements, and usually a newer server if the current one is old.
2. Upgrade and move to SQL Server at the same time. Worth considering if you are also dealing with slowness or data errors. See our guide to moving from c-tree to SQL Server.
3. Stay on the current version for now, with protection. Sometimes right for a firm that is winding down or planning to change software within a year. If you do this:
- Keep the server and workstations exactly as they are, and off automatic feature upgrades.
- Make sure backups are tested and include the installer for your version.
- Have a specialist you can call. We support every PCLaw version, including those the vendor has retired.
If that is your firm, see our support for older PCLaw versions, with a page for each version from PCLaw 4 to PCLaw 14.
4. Move to different software. If the firm was already thinking about cloud software, the end of support is a natural point to decide. Read PCLaw vs. Clio for an honest comparison, and remember you will still need to keep the old PCLaw data readable for your record-keeping period.
Planning an upgrade
- Find out exactly where you are: version, edition, data size, server and Windows versions.
- Check the data first. Run Verify Data Integrity and reconcile all accounts. Upgrading damaged data is the main cause of failed upgrades.
- Take a full backup and test it.
- Run the upgrade on a copy before touching the live system.
- Check the results: trial balance, trust listing, receivables and work in progress must match the figures from before the upgrade.
- Upgrade the live system outside working hours, with a clear plan for going back if anything is wrong.
- Test every workstation, including printing bills and cheques.
If an upgrade has already gone wrong
An upgrade that stops partway can leave the data in a state that neither the old nor the new version will open. Do not run it a second time and do not restore over the top of it. Copy the data as it stands and call us. Recovering from failed upgrades is a regular part of our PCLaw data recovery work.
Help with the decision
We upgrade firms from every PCLaw version, including very old ones, as part of our PCLaw migration service, and we support firms that choose to stay where they are through our PCLaw support service. Contact us and we will tell you plainly which option makes sense for your firm.