Moving a paralegal office off MS Access: the risks you are carrying

A great many Ontario paralegal offices still run on an MS Access database, often one that has been in service for fifteen years or more and has been shaped around exactly how that office works. There is nothing shameful about it. These systems were well matched to the problem when they were built, and a tool your staff know cold has real value.

The difficulty is that the risks accumulate quietly, and they are structural rather than fixable. This article is about naming them honestly, and about what moving actually involves.

Everything depends on one machine

In most offices running Access, one computer holds the real database file and everyone else connects to it across the office network. That machine is now the most important asset in the practice, and it is usually an ordinary desktop under somebody’s desk.

If it fails, gets replaced, or is simply switched off by someone tidying up, the office stops. Not slows down, stops. Nobody can open a file, check a court date or look up a client until it is back.

Corruption is a real failure mode

Access databases can and do corrupt, particularly when several people use them at once over a network, and particularly when a connection drops mid-write. Anyone who has run one for long enough has seen the compact-and-repair routine become a regular ritual.

The problem is not that repair usually works. It is that when it does not, the recovery position is whatever your last backup holds.

Remote work is a structural limitation

Access was designed for a local network. Working from home, from a courthouse, or from a second office means bolting something on: remote desktop into the office machine, a VPN, or a synchronisation arrangement. Each adds cost, latency and a new thing that breaks.

The same constraint is what makes a second office genuinely hard. You either duplicate the database, which creates two versions of the truth, or you pipe everyone through one location and accept the performance.

Who can still change it?

Access systems are usually maintained by one person, sometimes the original author, sometimes a consultant who has moved on. As the years pass, the number of people who understand the forms and queries shrinks, and at some point it reaches zero.

At that stage the system becomes fixed. You can use it, but you cannot adapt it, and every change in how you want to work has to be absorbed by your staff instead.

The good news: the data is portable

An Access .mdb file is a real relational database, and its tables can be read and exported with standard tooling. You do not need the application running, a licence, or cooperation from whoever built it.

This matters because it means your history is not hostage to the system holding it. The hard part of a migration is not getting the data out. It is working out what it means.

What the move actually involves

The sequence is the same regardless of who does it:

1. 1Take a copy of the database. Your office keeps working, untouched.
2. 2Export every table and examine what is genuinely there.
3. 3Map your conventions: what your fields mean, how file numbers encode offices, which staff are current.
4. 4Run a full dry run into a staging environment that is not live.
5. 5Review a verification report with per-entity record counts and an exception list.
6. 6Go live, with a delta import covering everything entered since the dry run.

Steps three and five are where your time goes, and they are the steps worth spending it on. Extraction is mechanical; interpretation is not.

What changes afterwards

The practical differences that offices notice first are rarely the headline features:

What to do if you are not ready to move yet

Moving is a decision with timing, and there are legitimate reasons to wait. If you are staying on Access for now, three things are worth doing regardless:

• Test a restore. Actually restore a backup to a separate machine and open it. Do this this month.
• Keep an off-site copy. A backup that lives in the same building as the original is protecting you against fewer scenarios than you think.
• Write down what your fields mean. The knowledge currently in one person’s head is an asset, and it is the thing that makes a future migration straightforward.

That third one pays off whether you move next year or in five years, and whoever eventually does the migration will thank you for it.