5 Access Databases We\'ve Seen That Were Overdue for Migration
After working with dozens of Access databases, certain patterns appear again and again. These are the five database profiles that tell us a migration is not just a good idea — it is overdue.
After working with Access databases across dozens of organizations, certain patterns appear again and again. Not every Access database needs to be migrated — some are perfectly suited to the tool and running fine. But some databases have clearly outgrown Access, and the people running them often know it but have not yet made the move.
Here are five profiles we see regularly. If your database matches one of them, the migration conversation is probably overdue.
1. The Database That Only One Person Understands
Every organization has one. It was built by someone who has since retired, moved on, or is the only person who knows how it works. The VBA is undocumented. The table names are cryptic. There are queries that nobody runs anymore but nobody will delete because they are afraid something will break.
This database is a business risk. When the person who understands it leaves — or gets hit by the proverbial bus — the organization is left with a critical system that nobody can maintain.
We see this most often in finance departments, operations teams, and HR — places where a technically inclined person built something years ago that became load-bearing infrastructure.
Why migration is overdue: The migration process forces documentation. To rebuild the application on a modern platform, you have to understand what it does. That understanding — captured in requirements documents, data models, and code comments — is itself valuable, independent of the new platform. Organizations that migrate these databases consistently report that the documentation alone was worth the investment.
What the migration looks like: Usually a full rebuild, because the existing code is too tangled to port cleanly. The data migration is straightforward. The front-end rebuild takes longer, but the result is an application that the whole team can understand and maintain.
2. The Database That Crashes Every Few Weeks
The symptoms are familiar: Access closes unexpectedly, a query that ran fine yesterday now throws an error, or the database opens in read-only mode because someone else has it locked. Users have learned to save frequently and restart Access when things get slow.
This database is usually approaching the 2 GB limit, has significant fragmentation, or is being accessed by more users than the architecture can support. Compact and Repair helps temporarily, but the problems keep coming back.
Why migration is overdue: Every crash is a productivity loss. Every corrupted record is a data integrity risk. The organization is spending real time on workarounds and recovery that could be spent on actual work.
What the migration looks like: Often a SQL Server back end with the Access front end relinked via ODBC — the fastest path to stability. Once the data is in SQL Server, the crashes stop. The front end can be rebuilt later if needed.
3. The Database That Nobody Can Access Remotely
The pandemic accelerated this one. Organizations that had always worked in the office suddenly needed remote access to their Access databases. VPN access to a file share is slow and unreliable for file-based database access. Some organizations set up Remote Desktop just to run Access, which works but is expensive and awkward.
These databases are often otherwise healthy — good data, reasonable performance, happy users — but they are physically tethered to the office network.
Why migration is overdue: Remote work is not going away. Every day the database requires physical office presence is a day of friction for remote workers and a constraint on hiring.
What the migration looks like: Power Apps with Dataverse is the most common destination for these databases. The result is a web application that works from anywhere, on any device, with no VPN required. The migration is often the catalyst for a broader Microsoft 365 adoption.
4. The Database That Has Become a Spreadsheet Graveyard
This one is subtle. The Access database exists, but over time users have started maintaining parallel spreadsheets because the database is too slow, too hard to use, or missing features they need. Now there are three versions of the customer list — one in Access, one in Excel on the shared drive, and one in someone's personal OneDrive.
The database has not failed. It has been quietly abandoned in favor of workarounds.
Why migration is overdue: Data fragmentation is a serious problem. Decisions are being made on incomplete or inconsistent data. The organization thinks it has a database, but it actually has a database plus a collection of shadow systems that nobody fully controls.
What the migration looks like: The migration is often the opportunity to consolidate. The new system — usually Power Apps with Dataverse, or a web application — replaces both the Access database and the spreadsheets. Users get a single source of truth that is easier to use than either predecessor.
5. The Database That Is Blocking a Larger Initiative
This is the most urgent profile. The organization wants to move to Microsoft 365, or adopt a new CRM, or implement a new ERP system — and the Access database is in the way. It stores data that the new system needs. It runs processes that the new system will replace. But nobody has figured out how to migrate it, so the larger initiative is stalled.
We see this frequently with Microsoft 365 rollouts. Organizations want to use Teams, SharePoint, and Power Platform, but they have an Access database that does not fit into that ecosystem. The Access database becomes the blocker.
Why migration is overdue: The cost of the Access database is now being measured not just in its own maintenance, but in the delayed value of the larger initiative it is blocking.
What the migration looks like: Usually a targeted migration to Power Apps and Dataverse, timed to align with the broader Microsoft 365 rollout. The Access database migration becomes part of a larger modernization project rather than a standalone effort.
The Common Thread
What these five profiles share is that the cost of staying on Access has become higher than the cost of migrating. The database is not just a technical liability — it is a business liability.
The migration conversation is never easy. There is always a reason to wait: the timing is not right, the budget is not there, the person who knows the database is too busy. But in each of these profiles, waiting makes the problem worse, not better.
The organizations that migrate these databases consistently report the same thing: they wish they had done it sooner.
Work With Access Evolved
If you found this article useful, Access Evolved specializes in exactly this kind of work — from hands-on Microsoft Access support to full database modernization projects.
Think your Access database might be overdue for migration? Schedule a free assessment and find out for sure.
Thinking about migrating?
Ready to move beyond Microsoft Access?
Access is a great starting point, but growing businesses often hit its limits. Anthony Passeri specializes in migrating Access databases to modern platforms — Power Platform, Power Apps, SQL Server, Azure, and more — so you keep your data and workflows without the headaches.
Written by
Anthony Passeri, MBA
Access Expert and Editor
Bridging the gap between Access and the Future
Explore Topics
Keep reading
More on Migration Cost & Timeline
The 5 Phases of an Access Database Migration
Every Access migration that goes wrong does so in one of the same predictable ways. Understanding the five phases — and where each one typically breaks down — is how you avoid them.
How Long Does an Access to SQL Server Migration Really Take?
The honest answer to the timeline question — with real numbers based on database size and complexity, not optimistic estimates.
How to Estimate Access Migration Cost by Database Size
Migration cost is the first question every Access developer asks. Here is a practical framework for estimating what your specific database will cost to migrate — based on size, complexity, and destination platform.