Replace a Microsoft Access database when it starts holding the business back: more people need it at once, people need it from outside the office, the file is creeping toward Access's 2 GB limit, or only one person understands how it works. The right replacement depends on what the database actually does. For most small businesses, the safest path is to move the data into a real database first, then replace the screens and reports a piece at a time.
Access has been a quiet workhorse in small businesses for more than thirty years. Across Iowa we still find it running quotes, inventory, case tracking, grant reporting and production schedules. It usually got there because someone smart built exactly what the business needed, and it worked. The question isn't whether Access was a mistake. It's whether it still fits.
What are the signs you've outgrown Access?
Most businesses don't decide to replace Access. They notice a pile of small frustrations that turn out to have the same cause.
- More people need it at the same time. Access is a file on a shared drive. It handles a few simultaneous users well. As that number grows, it gets slower and more fragile, and "everybody out of the database" becomes a weekly announcement.
- People need it away from the office. Remote staff, a second location, someone on a job site. Running a shared Access file over a VPN is painful, and there's no clean way to open it in a browser.
- The file is getting big. Microsoft's Access specifications cap a database at 2 GB, minus the space system objects need. Attachments and years of history get you there faster than you'd think.
- One person knows how it works. The person who built it has moved on, or is about to retire, or is the only one who can fix a broken report. That's a key-person risk dressed up as a software problem.
- Data leaves it to get work done. Someone exports to Excel, cleans it up, emails it around, and pastes the results back. Every round trip is a chance for an error.
If two or three of those sound familiar, you're past the point where "it still works" is the whole story.
Is it really Access, or is it a spreadsheet?
Often it isn't Access at all. It's a spreadsheet that became a system: the shared workbook with fifteen tabs, color codes only two people understand, and a macro that breaks when someone inserts a column.
Everything in this post applies to that spreadsheet too. Several people editing it, copies emailed around, numbers pasted into a monthly report: that's a database doing its job without a database's protections. Moving it into a proper database follows the same steps, and it is usually a smaller project than people expect.
What are the best alternatives to Microsoft Access?
There's no single answer, because "replace Access" can mean five very different things.
| Option | Best for | Watch out for |
|---|---|---|
| Keep Access, move the data to SQL Server or Azure SQL | Databases that work well but are hitting size, backup or multi-user limits | It's still a Windows desktop front end, and it still depends on whoever understands the forms and code |
| Power Apps with Dataverse | Businesses already on Microsoft 365 that need forms, approvals and mobile access | Dataverse requires a Power Apps Premium license per user, and complex reports and logic can be awkward to rebuild |
| A low-code internal-tools platform | Simple screens over a database, built quickly | Per-user costs grow with headcount, and your logic lives inside the vendor's platform |
| An off-the-shelf SaaS product | When the database does something common: CRM, inventory, job tracking, ticketing | Your process bends to the product. List what the old database did that the product can't |
| A custom web app | When the database encodes how your business works differently from everyone else | Someone has to maintain it. Insist that you own the code and that it's documented |
Microsoft offers a free tool, SQL Server Migration Assistant for Access, that moves the tables and links Access to them. It handles the mechanical part well. It doesn't tell you which queries matter or which reports people quietly depend on.
So what should replace an Access database?
What should replace an Access database depends on what it does that nothing else in your business does. If it tracks something common, such as customers, inventory or service tickets, an off-the-shelf product is usually the right answer, as long as you check what it can't do before you sign. If the database works well but is straining under more users, more data or remote access, move the tables to SQL Server or Azure SQL and keep the Access front end for now. That's the cheapest, lowest-risk step, and it buys time. If the database captures how your business works differently, the way you quote, schedule or price, then a custom web app or a Power Apps build is worth considering, because that logic is part of what makes you competitive. In every case, start by moving the data, not by picking the new screens. The data is the asset. The screens can be replaced one at a time.
How do you replace an Access database without breaking the business?
The projects that go badly try to replace everything on one weekend. The ones that go well move in three phases.
1. Inventory what it really does. Not what people think it does. Open every table, query, form, report and macro, and find out who uses each one and when. Pay special attention to the reports. The month-end report the controller runs, the list the shop floor prints every morning, the export that feeds a customer portal: those are what people rely on, and they're the first things lost in a rewrite. Talk to the people who use it, not just the person who built it.
2. Move the data first. Clean up the tables, put them in a real database, and link the existing Access front end to them. Nobody's day changes. But now you have proper backups, room to grow, security you can manage, and data your other systems can read. This step alone solves the size and reliability problems for a lot of businesses.
3. Replace the front end piece by piece. Start with the screen that causes the most pain, or the one remote staff need most. Build its replacement, put it in front of the people who use it, and retire the old form once they're happy. Then do the next one. Each piece goes live on its own, so there's never a risky cutover day, and you can stop at any point with something that works.
Before you rebuild a step, ask why it exists. Some of what the old database does is a workaround for a problem you can now solve directly.
Why is replacing Access cheaper than it used to be?
A few years ago, modernizing a legacy database meant a long, expensive project, and many small businesses reasonably decided to live with what they had.
That math has changed. AI-assisted engineering makes the slow parts of a modernization much faster: reading old queries and code to understand what they do, mapping old tables to new ones, writing and testing conversion scripts, and building replacement screens. The judgment still comes from people, including which reports matter, what the business rules really are, and when to leave something alone. But the hours it takes to act on that judgment have dropped a lot.
That's why Mosaic now takes on modernization and migration work that used to need a much larger team. We start by learning how the database is actually used, scope the work before it begins, and build inside the systems you already run, billed hourly for the time it takes. If your Access database sits next to an ERP on a plant floor, our post on AI in manufacturing covers why the data underneath matters before anything else.
Where should you start?
Start with the inventory. Even if you replace nothing this year, knowing what the database really does, who depends on it and what only one person understands is worth having on paper.
If you'd like help with that inventory or with the move itself, see how we approach custom software and modernization. We work with businesses in Cedar Rapids, Iowa City and across Iowa, and we'd rather help you keep what works than talk you into a rebuild you don't need.