The Hidden Costs of Staying on Access
The cost of migrating from Access is visible and easy to estimate. The cost of not migrating is invisible and accumulates quietly. Here is what you are actually paying to stay put.
When organizations evaluate migrating from Access, the conversation almost always focuses on the cost of migration: developer time, licensing, training, disruption. These costs are real, visible, and easy to put a number on.
What rarely gets calculated is the cost of staying. That cost is invisible, distributed across dozens of people and processes, and accumulates quietly year after year. By the time it becomes undeniable, it has usually been accumulating for a long time.
Here is what you are actually paying to keep your Access database running.
The Productivity Tax
Every workaround your users have developed to compensate for Access limitations costs time. Most of them have become so routine that no one thinks of them as workarounds anymore — they are just "how we do things."
Common examples:
The export-to-Excel ritual. Access cannot produce the report someone needs, so they export to Excel and build it there. This takes 20 minutes. It happens every week. That is 17 hours per year for one report, for one person.
The "who has it open" problem. Someone needs to run a process but the database is locked because a colleague has it open. They wait, or they call, or they email. Five minutes here, ten minutes there. Multiply by the number of users and the frequency of conflicts.
The manual re-entry. Data exists in another system — a CRM, an accounting package, a vendor portal — but it does not connect to Access. Someone copies it manually. Every day, or every week.
The "I need to be at my desk" constraint. Access requires Windows. It requires the right machine. A manager who needs to approve something while traveling cannot do it. A decision waits until Monday.
Add these up across your team for a year. The number is usually surprising.
Maintenance Burden
Access databases do not maintain themselves. Someone — usually a developer, sometimes a power user who has learned just enough VBA to be dangerous — spends time keeping the database running.
Compact and Repair. Someone runs it regularly, or the database grows bloated and slow. If it is not automated, it requires manual intervention.
Relinking tables. When the network path to the backend changes, or when a user gets a new machine with a different drive mapping, linked tables break. Someone fixes them.
Debugging VBA errors. Access VBA is not robust. Error handling is inconsistent. When something breaks, someone investigates.
Managing the split database. Distributing frontend updates to every user's machine. Ensuring everyone has the right version. Dealing with the user who is still running the version from two years ago.
Handling corruption. Access databases corrupt. Not often, but it happens — especially on unreliable networks or after improper shutdowns. When it does, someone spends hours on recovery.
None of this is dramatic. Each incident is small. But the cumulative maintenance burden over a year is significant, and it falls on people whose time has other uses.
The Security Liability
Access security is, charitably, minimal. The old workgroup security model was deprecated. Most Access databases rely entirely on network share permissions — anyone who can reach the file can open it.
This creates real risk:
No row-level security. Every user sees every record. A salesperson can see every customer's data, not just their own accounts. An HR assistant can see every employee's compensation, not just the records they manage.
No audit trail by default. Without custom VBA audit logging, there is no record of who changed what. If data is altered — accidentally or intentionally — you may not be able to determine what happened.
No encryption at rest. Access databases can be password-protected, but the protection is weak. The data in the file is not encrypted in any meaningful sense.
Compliance exposure. If your database contains personal data (GDPR), health information (HIPAA), or financial data (SOX, PCI), the lack of proper access controls and audit trails is a compliance liability. The question is not whether this is a problem — it is whether it has been noticed yet.
Quantifying security risk is difficult. Quantifying the cost of a breach or a compliance finding is not.
The Opportunity Cost
This is the hardest cost to see and the most significant.
Every hour your team spends working around Access limitations is an hour not spent on something else. Every feature your business needs that Access cannot provide is a capability gap. Every decision that waits because the data is not accessible on mobile, or not integrated with your other systems, or not available in real time — each of these has a cost.
What could your team do with a system that:
- Gives managers real-time dashboards instead of weekly Excel exports?
- Lets field staff enter data on their phones instead of writing it down and entering it later?
- Automatically notifies the right people when a record changes instead of relying on email chains?
- Integrates with your CRM, accounting system, and email without manual re-entry?
The opportunity cost of staying on Access is not just the cost of the workarounds you have. It is the value of the capabilities you do not have.
The Escalating Risk of Dependency
Access databases accumulate dependencies over time. The database was built by someone who left three years ago. The VBA code has not been touched since 2019. The person who knows how it works is retiring next year.
As the knowledge base shrinks and the codebase ages, the risk of a catastrophic failure increases. Not because Access is getting worse — but because the safety net is getting thinner.
When the database breaks in a way that no one on staff can fix, the options are:
- Find an Access consultant (expensive, slow, and they are becoming harder to find)
- Migrate under pressure (the worst time to migrate — rushed, underfunded, high risk)
- Lose the data or the functionality entirely
The cost of a forced migration under crisis conditions is typically three to five times the cost of a planned migration. The disruption is greater. The risk is higher. The outcome is worse.
Calculating the Real Cost
A rough framework for estimating the annual cost of staying on Access:
Productivity losses:
- Hours per week spent on workarounds × number of users × hourly cost
- Hours per week spent on manual data re-entry × hourly cost
- Hours per month lost to database conflicts and wait times × hourly cost
Maintenance burden:
- Developer/admin hours per month on Access maintenance × hourly cost
- Estimated cost of one corruption event per year (recovery time + data loss)
Risk premium:
- Estimated probability of a compliance finding × estimated cost of finding
- Estimated probability of a forced migration in the next 3 years × cost premium of forced vs. planned migration
Opportunity cost:
- Value of one capability your business needs that Access cannot provide
- Cost of one integration that does not exist because Access cannot support it
For most organizations, this calculation produces a number that is larger than the cost of migration — often significantly larger. The migration pays for itself, usually within 18–24 months.
The Conversation to Have
The goal of this analysis is not to create anxiety about Access. It is to make the cost of staying visible so it can be weighed against the cost of migrating.
Migration has a price. Staying has a price. The question is which price you would rather pay — and whether you would rather pay it on your schedule or on the database's schedule.
Most organizations that have done this analysis honestly have found that the migration was worth it. Not because Access is terrible, but because the accumulated cost of staying had grown larger than anyone realized.
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.
Want to uncover the hidden costs in your specific migration project? Schedule a free assessment call before you commit to a budget.
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
Getting Team Buy-In for an Access Migration
The technical side of migrating from Access is solvable. The harder part is convincing stakeholders, managing user resistance, and keeping the project funded. Here is how.
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.
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.