Signs it is time to replace your Microsoft Access database

Most Access databases were a good idea when they were built. Someone solved a real problem quickly, with a tool that was already on the PC, and the business ran on it happily for years. Nobody decided it should be the thing the company depends on. It just became that, one useful screen at a time.

The question is not whether Access is a bad product. It is not. The question is whether the particular database you have is still doing its job safely, or has quietly become the biggest single point of failure in the business.

If you want the story about Microsoft's support dates, we cover that separately in our guide to Microsoft Access end of life. This guide is about something more practical: how to recognise that it is time to move on.

1. The file keeps corrupting

Multi-user Access works by several people opening the same file across the network. When someone's PC sleeps, their wifi drops or the file is open while a backup runs, the file can be damaged. The usual fix is compact and repair, then a restore from last night's backup.

One incident in five years is bad luck. A pattern, where staff have learned to "get everyone out of the database" before doing anything important, is a sign that the architecture has reached its limit. You are losing real work each time, and you are relying on people remembering a ritual.

2. It is slow, and getting slower

Reports that took seconds now take minutes. Forms hang while they load. Staff open the database first thing and go and make a tea.

Access holds all its data in one file, and every user pulls what they need across the network to their own machine. As the data grows and more people use it, that stops scaling. You can sometimes buy time by tuning queries, but if the slowdown tracks the growth of the business, tuning only delays the conversation.

3. Nobody can safely change it

This is the sign we see most often, and it matters more than any technical one. The person who built it has left, or has moved into a different role, or is a contractor who no longer answers the phone. Everything still works, but the business has stopped asking for changes because nobody knows what else a change will break.

At that point you have an unsupported system, whatever version of Office it runs in. We wrote about this risk in more detail in what happens if your software developer disappears, and it applies to Access databases just as much as to anything bespoke.

4. People need it away from their desk

Engineers on a customer site, drivers, carers, a sales team at a trade show. If any of them need to look something up or record something, and the answer is "wait until I am back at the office" or "log in through a remote desktop", the database is costing you time every single day.

Often this is the real reason a business finally acts. The data is fine. The trouble is that the work has moved out of the building and the database has not.

5. You are working around it

Look for the signs of a system that has stopped fitting:

• Exports to Excel every week so that someone can do the part Access cannot.
• Information typed into Access and then typed again into the accounts package.
• A second spreadsheet next to the database that holds the things nobody could add to it.
• Staff who keep their own notes because they do not trust the records.

Each workaround is a small tax on the week. Together they are usually the largest cost of keeping the database, and the cost is invisible because it is spread across everybody's time rather than appearing as an invoice. If double keying is part of the picture, a system integration may solve a surprising amount of it on its own.

6. You cannot control who sees what

Access has very little in the way of real permissions. In practice most people who can open the file can see everything in it, including customer details, pricing and sometimes staff records. If the database holds personal data, that is a data protection question as well as a tidiness one.

The same applies to history. When a figure is disputed, can you see who changed it and when? In most Access databases the answer is no.

7. The business is about to change

New site, new service line, more staff, a new accounts package, a customer asking for online access to their own records. Any of these is a good moment to look hard at the database, because each one tends to push on exactly the places where Access is weakest. It is far cheaper to replace it before a growth spurt than in the middle of one.

Repair, upgrade or replace

Not every one of these signs means a full rebuild. Roughly:

• One or two signs, both about size or reliability. Moving the data into a proper database and keeping Access as the front end is often enough, and it is the cheapest real fix.
• Signs 3, 4 or 5. These are about the application, not the data. A better database underneath will not help, because the screens and the access problem are still there. This is where replacement earns its keep.
• No signs at all. Leave it. A small database used by two people, holding nothing sensitive, is not a project.

If you land in the middle category, the work is described on our legacy system replacement page. The encouraging part is that the old database is an asset rather than a burden. Years of real business rules are encoded in it, along with the data itself, and a rebuild that starts by reading what is already there is a far better specification than a blank page.

What a replacement involves

The sequence is usually the same. We look at the database as it actually runs, including the tables, the queries, the VBA and the reports that people really use. We talk to the people who use it, because the screens that matter are not always the ones you would guess. Then we agree what the new system must do on day one, what can wait, and how the data will move across.

It is normally built and tested alongside the old database, so staff can run both until they trust the new one. How long that takes depends on the size and condition of the data and how many processes hang off it, and our guide to how long bespoke software takes sets out realistic ranges so you can plan around them.

Before you decide anything

Do three small things first. Find out who actually uses the database and what they use it for. Take a backup that lives somewhere other than the server where the file sits, and check that you can restore it. Then write down, in a couple of sentences, what it would cost the business if it were unavailable for a week.

That last answer usually settles the question. If the honest reply is "we would cope", you have time. If it is "we would stop", treat it as a system and not a file.

Our free process audit covers exactly this. It is 60 minutes, usually on site, and you will get a straight answer at the end, including "leave it alone" where that is the right call. You can book one through the contact page.