An Access database that runs a department's core workflow goes down. It's a Monday. The person who built it retired two years ago. Nobody knows exactly what it does, only that without it, three people can't do their jobs.
This isn't a hypothetical. It's a pattern we see regularly. And the cost of that outage — the real, total cost — is almost never calculated honestly before it happens.
When a business-critical Access database fails after an upgrade or update, the costs accumulate from several sources simultaneously:
Someone has to respond to the incident. Diagnose it. Attempt fixes. Research the problem. Escalate if internal knowledge runs out. Find a consultant. Brief the consultant. Wait for a fix.
For a .mdb that fails because Access 2021 doesn't support the Jet format: diagnosis time is 2–6 hours. For a .mdb with VBA errors and ActiveX failures: 8–24 hours for an experienced VBA developer who wasn't already familiar with the codebase. For an IT generalist trying to figure out what VBA even is: potentially days.
Every hour the database is down, affected users either sit idle or spend time on manual workarounds. Manual workarounds for an automated process that took 15 minutes per day can easily take 2–4 hours to reproduce manually, with more errors.
If the workflow involves 5 users at an average fully-loaded cost of $35–$65/hour:
The Access database usually feeds something. Invoices don't go out. Inventory doesn't get updated. Reports can't be generated for a client meeting. Shipments get delayed because the pick list isn't generated.
These downstream impacts are harder to quantify but often larger than the direct IT and labor costs. A delayed invoice by three days doesn't just cost the invoice value — it affects cash flow, customer satisfaction, and potentially penalties on contracts with payment terms.
If internal IT can't resolve it and the business function is critical enough, a VBA specialist gets called in. Emergency rates are not normal rates. $150–$300/hour for an emergency Access/VBA consultant is not unusual. And because they're coming in cold with no familiarity with the codebase, they need time to understand what the database does before they can fix it.
If the database was left in a half-open state when it failed — a write that didn't complete, a form that was in the middle of editing a record — there may be data integrity issues to resolve after the technical fix. Records to check. Transactions to verify. Potentially data to recover from backup.
A 6-person accounting team uses an .mdb database to track client billing and generate monthly invoices. The database has been running since 2008. After an Office 365 migration, Access no longer opens the .mdb file.
That's for a single day. If resolution takes 2–3 days, the cost multiplies. And this doesn't account for the less tangible costs: the stress on the team, the client who asks why their invoice is late, the manager who has to explain what happened to leadership.
The same .mdb database, migrated proactively before the Office 365 upgrade:
Total proactive migration cost: roughly $1,500–$2,500.
Compare to $4,540 for a single day of reactive outage — and that's a modest estimate. For a more critical database or a longer outage, the reactive cost is easily 5–10x the proactive migration cost.
This is the business case for proactive migration, and it's worth making explicitly to the decision-makers who control migration budgets.
LegacyLeaps scans your Access database and tells you exactly what's inside — VBA code, forms, queries, linked tables, and ActiveX controls — before anything breaks. Free scan, no commitment.
Try the Free ScanThe reason legacy databases don't get migrated proactively isn't budget — it's that they appear to be working. The .mdb opens. The forms load. The reports print. Nobody is complaining.
What's invisible: the software environment has been shifting under the database for years. Windows updates quietly removed components the database depended on. Office security policies changed. The 32-bit Office installation that kept everything compatible was replaced by a 64-bit one. The database works today because of a chain of preconditions that are eroding without anyone tracking them.
The failure mode isn't gradual degradation. It's a specific event — an Office upgrade, a Windows update, a new machine — that removes the last precondition the old database was relying on. Then it stops working completely, all at once, on a day when you didn't plan for it.
If you're an IT manager or department head trying to get budget for a proactive migration:
While this applies to legacy Excel files too, .mdb databases deserve special attention because:
If you have .mdb databases in active use, the question isn't whether they'll break — it's when, and whether you'll be ready.
Our Done-For-You team handles .mdb to .accdb migrations for organizations that need it done right. Fixed-price quote, no surprises, and a 14-day money-back guarantee if we don't get it right.
Get a Free Consultation Try the Free Scan FirstRelated: The Hidden Cost of .mdb Files in Production · How to Convert .mdb to .accdb — Step-by-Step · Complete Guide to Access Database Migration
Practical fixes for legacy Excel and Access problems. No spam.