Software
Replace Microsoft Access: Four Options and What Each Costs
There are four ways to replace Microsoft Access, or not: rebuild it as a web app, move the data into a product you buy, keep Access and put the data on a proper server, or leave it alone for now. They cost very different amounts, and the right one depends on where your people work and what is actually breaking.
We don’t publish prices for Access work, because Access database migration cost depends on what the file does, and two files of the same size can be very different jobs. What we can say is how the four options compare with each other, and roughly how long each takes. Every one of them, apart from the last, starts with a free audit and a fixed quote in writing.
Option 1: Rebuild it as a web application
Every form and report is rebuilt to run in a browser, on a desk or a phone. The data comes across with checks at both ends, and the business rules hidden in the VBA get found, written down and rebuilt.
- Cost: the highest of the four up front, because nothing from the old screens carries over. The number of forms, reports and pieces of code sets it more than the size of the file.
- Time: a single-department database usually takes eight to twelve weeks from audit to cutover. A larger file with several departments takes about three months, and a multi-module system can run to a year.
- Best when: people need it away from one office, on a job site, in a truck or at home, or the code itself is the problem.
Our guide to Microsoft Access to a web app covers what moves cleanly and what gets rebuilt.
Option 2: Move the data into an off-the-shelf product
If what the database does is standard for your trade, somebody already sells it. The best alternative to an Access database is sometimes a subscription product you never have to maintain.
- Cost: usually the cheapest to start. The ongoing cost is per seat, so it grows with every person you add, and moving the old records into the product is extra work on top.
- Time: mostly set by the data. Cleaning and importing years of records takes longer than learning the product.
- The catch: your people learn the product’s way of working, and your old forms and reports go away. That is fine for most processes. It isn’t when the way you do the work is the reason customers choose you.
Our post on build vs buy has the test we use to decide.
Option 3: Keep Access and put it on a server
The tables move to SQL Server, and the Access forms and reports stay on each desk, linked to the new tables. Moving the data off a file on a shared drive and onto a real database server is the part that matters.
- Cost: the lowest of the three real moves, and the fastest.
- What it fixes: the file size limit, the backups, the permissions, and two people locking each other out.
- What it doesn’t: everyone still needs Access on a Windows PC, working remotely stays slow, and the code only one person understands is still there.
For one office on one network, with screens that work, this can be enough for years. It also works as a first stage, with the web app built later.
Option 4: Do nothing, and what that costs
Sometimes the honest answer is to leave it. A single-user database running a stable process, with no growth pressure, can stay as it is on a supported machine with a tested backup. That costs almost nothing.
What it costs you is risk, and it rises as the warning signs stack up: the file is nearing its size limit, people see corruption errors, it only runs on one old machine or one old version of Office, or the person who built it has left. Two or more of those, and the cost of doing nothing is the morning the file won’t open.
How long the shop keeps working during a move
The whole time, for any of the first three options. Staff keep using the Access file while the new system is built. Then both run side by side, with work going into both, until the numbers agree, and only after that does the old file go read-only. The month you switch is written into the quote and planned around a busy season or a month-end close, never across it.
Our post on retiring Microsoft Access without stopping the shop walks through those steps, and our Access migration page covers how we run them. Not sure which option fits? The scoping quiz asks seven questions and hands back a written brief, without asking for an email.