Most Access databases were never meant to run a business. Someone clever built one to solve one problem, and it quietly grew until the business couldn't manage without it. Access and Excel are brilliant for getting something working fast. The trouble starts when the business keeps growing and the database doesn't.
Access and Excel
Replace your Access database or spreadsheets with software that fits
If it's slow, breaks when several people use it, only works in the office or depends on one person, it's time to plan a replacement. A typical small business system takes two to four months, with the old one running until you're happy.
You'll be talking to one of us, not a salesperson.
This isn't a criticism
Seven signs it's time
One is a nuisance. Two or three together is a real business risk.
It's getting slow
Reports get run "when nobody else is in".
It struggles with users
Locked records, and people taking turns.
It corrupts
Someone runs Compact and Repair, and dropped Wi-Fi mid-save can damage your data.
One person understands it
The big one. If they left or were off sick for a month, could anyone fix it?
It only works in the office
No phone, tablet or Mac, and home working means remote desktop.
Data gets typed in twice
Into the database, then the accounts. Every time is a chance for the two to disagree.
It's limiting the business
A customer wants a portal and the answer is "the system can't do that".
Your realistic options
We build custom software, so take this with a pinch of salt. It isn't always the right answer.
Off the shelf
If your process is fairly standard, a subscription product probably does it well. Watch for per-user fees and the one thing you do differently.
Low-code
Power Apps, Airtable, Zoho Creator and the like. Fine when it's simple and someone in-house enjoys it. It's easy to recreate the one-person problem on a new platform.
Custom software
When it's central to how you make money, or nothing else fits. A web application on a standard database you own. It costs more up front, and you need a supplier you trust afterwards.
Leave it, but make it safer
Moving the data to SQL Server, documenting it and testing the backups can buy you a few years.
Write down what it does before you replace it.
The rules in an old database are the valuable part: the odd financial year, the rounding, the pretend job for holidays. We read the whole thing and write it up first. AI is a great help here, working through hundreds of queries in no time.
Then we rebuild it in fortnightly steps with the people who use it, move your data across and keep the old one running until you're happy.
Tell us what you've got
It goes straight to Rob and Jase. You'll hear back from one of us, usually the same day, and we'll tell you honestly whether we're the right people.