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.
"How much will it cost?" is always the first question. And the honest answer — "it depends" — is frustrating but true. What it depends on, though, is knowable. This post gives you a framework for estimating migration cost based on the specific characteristics of your database.
Why Database Size Is Only Part of the Story
File size and record count matter, but they are not the primary cost drivers in an Access migration. A 500 MB database with simple tables and no VBA can migrate faster than a 50 MB database with 30 forms, complex macros, and business logic scattered across dozens of VBA modules.
The real cost drivers are:
- Number of tables and their complexity (relationships, data types, constraints)
- Number of forms and reports (each one needs to be rebuilt or replaced)
- Amount of VBA code (logic that needs to be ported or rewritten)
- Number of users and their workflows (training and change management)
- Integration points (does Access connect to Excel, Outlook, other systems?)
- Destination platform (SQL Server back end only vs. full application rebuild)
With that context, here is how to think about cost by database profile.
Small Database: Under 100 MB, Under 10 Tables
Typical migration cost: $3,000 – $8,000
A small Access database with a handful of tables, a few forms, and minimal VBA is the most straightforward migration. The data moves in hours using SQL Server Migration Assistant (SSMA). The front end — if you are rebuilding it as a Power App or web application — takes most of the time.
At this size, the bigger question is whether migration is worth it at all. If the database works, has one or two users, and is not growing, the ROI case is harder to make. Migration makes sense here when the database is being shared over a network (multi-user problems), when it needs to be accessed remotely, or when it is part of a broader Microsoft 365 rollout.
Medium Database: 100 MB – 500 MB, 10–30 Tables
Typical migration cost: $8,000 – $25,000
This is the most common profile we see. A medium-sized Access database usually has a decade or more of history, a mix of well-designed and ad hoc tables, several forms that users depend on daily, and VBA that nobody fully understands anymore.
The data migration itself is still largely automated. The cost is in the front-end rebuild and the VBA audit. Before migrating, you need to understand what the VBA actually does — some of it is business logic that needs to be preserved, some of it is workarounds for Access limitations that disappear in a modern platform, and some of it is dead code that can be discarded.
At this size, expect 4–12 weeks of development time depending on form complexity and VBA volume.
Large Database: 500 MB – 2 GB, 30+ Tables
Typical migration cost: $25,000 – $75,000+
A large Access database is usually a mission-critical application that has grown organically over many years. It has complex relationships, significant VBA, reports that finance or operations depends on, and users who have built their entire workflow around it.
At this size, the migration is a software development project, not a data transfer. You are rebuilding an application. The data migration is a small fraction of the total effort.
The cost range is wide because complexity varies enormously. A 1 GB database with clean table design and minimal VBA can migrate for less than a 300 MB database with 50 forms and 10,000 lines of VBA.
What drives cost up at this size:
- Complex multi-table reports that need to be rebuilt in Power BI or SSRS
- VBA that calls external COM objects or Windows APIs
- Integration with other Office applications (especially Excel automation)
- Custom ribbon or navigation form interfaces
- Multiple linked databases that need to be consolidated
Destination Platform Affects Cost Significantly
The destination platform is a major cost variable that is often underestimated.
SQL Server back end only (keep Access front end): This is the lowest-cost option. You migrate the tables to SQL Server and relink them in Access using ODBC. Forms, reports, and VBA stay largely intact. Cost is typically 30–50% of a full rebuild. The tradeoff: you still have Access, with all its limitations.
SQL Server back end + rebuilt Access front end: Slightly more expensive than the above, but you get a chance to clean up the front end. Still requires Access on every user machine.
Power Apps + Dataverse: A full rebuild of the front end as a modern web application. Higher upfront cost, but eliminates the Access dependency entirely. Best for teams already in Microsoft 365.
Custom web application: The most expensive option, but the most flexible. Right for databases with complex workflows that do not fit the Power Apps model.
A Simple Estimation Formula
If you want a rough number before engaging a consultant, use this:
- Count your tables. Multiply by $200–$400 per table for data migration and schema work.
- Count your forms. Multiply by $500–$1,500 per form for front-end rebuild (depending on complexity).
- Count your VBA modules. Multiply by $300–$800 per module for audit and porting.
- Add 20% for testing, training, and project management.
This will give you a rough order-of-magnitude estimate. A real assessment will refine it significantly.
What You Can Do to Reduce Cost
Clean up before you migrate. Delete unused tables, archive old data, and remove dead VBA code. Every hour of cleanup before migration saves two hours during it.
Document your business rules. The most expensive part of any migration is figuring out what the VBA is supposed to do. If you can document the business rules before the project starts, you save significant discovery time.
Prioritize ruthlessly. Not every form needs to be rebuilt on day one. Identify the 20% of features that 80% of users use daily and migrate those first. Everything else can follow.
Consider a phased approach. Migrating the back end to SQL Server first (while keeping the Access front end) is a lower-risk, lower-cost first step that delivers immediate stability benefits.
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 a real estimate for your specific database — not a range? Schedule a free assessment and get a concrete number.
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.
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.
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.