Guide · Access and Excel replacement
Replace your Access database or spreadsheets with bespoke software
The warning signs, the honest options, and what a replacement project involves.
Most Access databases were never meant to run a business. They were built by someone clever in the office to solve one problem, and then they quietly grew until the business couldn't run without them.
That's not a criticism. Access and Excel are brilliant at getting something useful working quickly, which is exactly why so many firms end up depending on them. The trouble starts when the business keeps growing and the database doesn't.
This guide is for the operations manager, finance lead or owner who has a nagging feeling the system is held together with string. It covers how to tell when it's time, what your options really are (including the ones that don't involve us), and what a replacement looks like from start to finish.
Seven signs it's time to replace it
Any one of these on its own is a nuisance. Two or three together, and you're carrying a real business risk.
- It's getting slow. Screens that used to open instantly now take ten seconds. Reports get run overnight or "when nobody else is in". Access over a shared network drive slows down badly as the data grows and more people use it.
- It struggles with more than a few users. People get locked out of records, see "the database has been placed in a state by user Admin" messages, or have to take turns. We've written a whole guide on why Access struggles with multiple users.
- It corrupts. Someone has to run Compact and Repair every so often, and everybody knows to close it properly before going home. A dropped Wi-Fi connection mid-save shouldn't be able to damage your business data, but in Access it can.
- One person understands it. This is the big one. If the person who built it left, retired or was off sick for a month, could anyone else fix it, change it, or even explain what half the buttons do?
- You can't get at it from outside the office. Access is a Windows desktop program reading a file on a shared drive. Working from home means remote desktop or a VPN, and there's no version for a phone, a tablet or a Mac.
- Data gets typed in twice. Orders go in the database and then again into the accounts package. Jobs go in the spreadsheet and then onto a whiteboard. Every double entry is a chance for the two to disagree.
- It's started limiting what the business does. A customer wants a portal, a big client asks about your data security, or you want to take on more staff, and the answer is "the system can't do that".
If you're nodding along to the last one, you're probably already late. That's fine. Most people are.
Off-the-shelf, low-code or bespoke
There are three realistic routes, and a fourth (doing nothing) that's worth naming because it's the one most businesses take by default. We build bespoke software, so apply the usual pinch of salt, but bespoke is genuinely not always the right answer.
Off-the-shelf software
If your database does something lots of businesses do (CRM, job management, stock control, timesheets), there's very likely a subscription product that already does it well.
Fits when: your process is fairly standard and you're happy to change how you work a little to match the software.
Watch for: per-user fees that grow with you, and the one thing you do differently that the product can't handle.
Low-code platforms
Power Apps, Airtable, Zoho Creator and similar let you build forms and workflows on a hosted database without much coding.
Fits when: the system is fairly simple, someone in-house enjoys building things, and you're comfortable renting the platform.
Watch for: it's easy to recreate the key-person problem on a new platform. More on that in the case study below.
Bespoke software
A web application built around how your business actually works, on a standard database, that you own outright.
Fits when: the system is genuinely central to how you make money, your process is part of what makes you different, or nothing off the shelf fits without painful compromises.
Watch for: it costs more up front, and it needs a supplier you trust to look after it afterwards.
Leave it, but make it safer
Sometimes the honest answer is "not yet". Moving the data into SQL Server, documenting how it works and testing the backups can buy you a few years.
Fits when: it mostly works, only a few people use it, and the business isn't about to change shape.
Watch for: this treats the symptoms. Our guide on Access to SQL Server migration explains what it does and doesn't fix.
There's a longer side-by-side in Access database alternatives compared, and if it's a spreadsheet rather than a database that's run away with you, start with From Excel to web app. For the wider build-or-buy question, see bespoke or off-the-shelf.
What a replacement project involves
Whoever you use, a sensible replacement goes through the same five stages. If a supplier wants to skip straight to building, be wary.
- 1
Discovery
Someone reads the existing database properly: every table, query, form, report and bit of code. Then they sit with the people who use it, because the database never tells the whole story.
- 2
Specification
A plain-English description of what the new system must do, split into must-haves and nice-to-haves, agreed with you before any building starts.
- 3
Build in short rounds
Working software every couple of weeks that you can click through and comment on, rather than one big reveal at the end.
- 4
Data migration
Your history moved across, cleaned up, and checked against the old system with real numbers: record counts, totals, a sample of records compared line by line.
- 5
Parallel running and training
Old and new run side by side for a few weeks. Staff are trained on the new one, and the old one is switched off only when everyone's confident.
Discovery is the stage people want to rush, and it's the one that matters most. Access databases hide business rules in odd places: a query with a hard-coded date, a bit of code behind a button, a report that only works if you type the month a certain way. Miss those, and the new system does the wrong thing very efficiently. There's more detail on each stage in converting an Access database to a web application.
Cost and timescales
Bespoke software used to mean a big bill, and for a lot of small businesses that ruled it out. AI-assisted development has changed that. We use AI to read and document the old system, and to do the routine parts of the build, so a replacement takes far fewer developer days than it would have a few years ago. You pay for that time, so you get a bespoke system for a much more sensible price.
Every system is different, so we don't publish a price list. The free review below gets you a figure for yours. As a guide to timescales:
| Size of system | What it usually looks like | Typical timescale |
|---|---|---|
| Small | A handful of tables, a few forms and reports, one team using it. Often a spreadsheet or a simple Access database. | 4 to 8 weeks |
| Typical | The system a department runs on: customers, jobs or orders, scheduling, a few dozen reports, maybe an export to the accounts. | 2 to 4 months |
| Large | Runs most of the business: hundreds of forms and reports, finance, HR and scheduling in one place, links to other systems, a customer portal. | 4 to 9 months, usually in phases |
Hosting, support and further changes after launch are a separate monthly arrangement. See software support and maintenance.
Two things affect the cost more than anything else. The first is how many reports you genuinely use (people often find a third of them haven't been opened in years). The second is how clean the data is. Twenty years of free-text fields, duplicate customers and "do not use" records all take time to sort out, though it's time well spent.
How we do it
Spec first. We read the old system end to end and write down what it does in plain English, including the odd rules nobody remembers adding. You agree the specification before we build, and it becomes the checklist we test against.
Fortnightly timeboxes. We work in two-week rounds. Each one ends with working software you can try. The timebox stays fixed and the content flexes: if something new comes up, it goes on the list and gets prioritised at the next planning session rather than squeezed in. If the scope is growing, you hear about it early, with a clear picture of what more rounds would cost.
Bugs are ours. If something we delivered doesn't do what was agreed, fixing it comes out of our time, not your next round.
AI-assisted, developer-led. We use AI tools to read and document old systems quickly and to speed up the routine parts of the build. Experienced developers decide what gets built, review every line and own the result. It's quicker and much more cost-effective than doing it all by hand, without handing your business system to a chatbot. How we use AI goes into the detail.
You own it. Standard PHP and MySQL, on hosting you control, with the code and the documentation handed over. Any competent PHP developer can pick it up. We'd like you to stay with us because we're good, not because you're stuck.
A real one: a testing and compliance firm
This project is running as I write, so it's a live example rather than a polished success story. The client is a UK testing and compliance consultancy. We're not naming them, because the inside of a client's systems is theirs to talk about, not ours.
What they had
A split Access database that had run the business for many years: quotes, projects, engineer scheduling, report tracking, invoicing, HR and health and safety. The front end alone had 184 forms, 126 reports, 515 saved queries and 18 modules of code. The back end held 68 tables.
Part of the operation had already been moved onto a low-code platform sitting on a cloud SQL Server database. Then the developer who built that left. So they had two systems, one nobody could change and one that only a single member of staff fully understood. And that person was leaving within a few weeks.
What we found
Reading the database properly turned up exactly the kind of thing that sinks a rushed rebuild:
- Every PC had to find the back-end file at one fixed path on the C: drive, or nothing worked.
- Some screens were so slow over the network that the database copied results into local tables on each PC and read those instead.
- Staff holidays and sickness were recorded as bookings on a pretend internal job. Test equipment was set up as pretend employees, so it could be booked like a person.
- Nothing stopped an engineer being double-booked. The planner simply added up the days, and anyone who spotted a total above one knew to look.
- The financial year ran May to April, and some figures were cut off at two decimal places rather than rounded. Get either wrong and the new reports don't match the old ones.
- Around 20 reports no longer worked at all, and several queries had specific years typed into them.
None of that is unusual. It's what years of sensible quick fixes look like. But every one of those rules had to be found and written down before we could rebuild it properly, and the knowledge was about to walk out of the door.
What we're doing
We documented the whole Access system in a written reference, with every query rebuilt from the file itself, and agreed the new system in fortnightly rounds with the people who use it every day. The replacement is a standard PHP and MySQL web application they can hand to any PHP developer. Quoting went first because it's the commercial heart of the business. Jobs, scheduling and engineer allocation are being built now, with double-booking prevented by the system rather than spotted by eye.
The lesson worth taking away: the low-code rebuild didn't fail because low-code is bad. It failed because it swapped one person who understood the system for another. Whatever you replace Access with, make sure the knowledge ends up written down, not just moved.
Replacing Access: common questions
Microsoft still includes Access in its Windows desktop Office and Microsoft 365 business plans. What it has dropped is the web side: Access web apps in SharePoint were retired, and there's no Mac, browser or mobile version. Access isn't going to stop working tomorrow, but it isn't where Microsoft is putting its effort.
It depends on what the database does. For standard jobs like CRM or stock control, off-the-shelf software is usually best. For simple internal forms, a low-code tool like Power Apps can work. For a system that's central to how you make money, a bespoke web application usually fits best. See Access database alternatives compared.
It depends on how much the database does, how clean the data is and what it needs to connect to. Because we use AI-assisted development, it takes far fewer developer days than a traditional rebuild, so it costs much less than people expect. Our free review gives you a figure for your system.
Yes. All of it can be moved across, and it's usually the best chance you'll get to clean it up. A good migration is checked against the old system with record counts, totals and a sample of records compared line by line.
Yes, and you should. The old system keeps running until the new one is ready, then the two run side by side for a few weeks before Access is switched off.
It's more work but entirely doable. Everything the database does is in the file: tables, queries, forms, reports and code. We read it from there and then check our understanding with the people who use it day to day.
Free Access database or spreadsheet review
Tell us what you have and we'll tell you what we'd do.
What the system does, roughly how many people use it, and what's making you think about replacing it. A copy of the file or a few screenshots helps, but isn't needed to start.
What we will cover:
- Whether to replace it, patch it or leave it
- The options that would fit, including off-the-shelf
- A rough cost and timescale if replacing makes sense
Rather talk now? Book a call or ring 01474 639 089.
We reply within one working day.
