Moving an Access Database to SQL Server: Costs, Timelines, and the Three Paths
What the migration actually involves, with the numbers nobody publishes.
Somewhere in your office, a Microsoft Access database is running a real part of your business. It was built years ago, maybe by someone who has since left, and it worked fine until it did not. If you are reading this, you have probably seen the warning signs: crashes when several people use it at once, a file approaching 2 gigabytes, or the words "the database is corrupted" on a Monday morning.
This guide explains what moving to SQL Server involves, what it costs, and which of the three migration paths fits your situation. We are SQL Server consultants in Chicago and this is work we do constantly, so the numbers are from real projects, not theory.
The warning signs it is time
- The .accdb or .mdb file is above 1 GB and creeping toward Access's 2 GB hard limit
- Multiple users cause locking errors, slowdowns, or crashes. Access theoretically allows 255 connections; in practice trouble starts around 5 to 15 simultaneous users
- You have had to run "Compact and Repair" as a ritual, or you have lost data to corruption at least once
- Remote and home-office staff cannot use it reliably, because Access over a VPN is painful by design
- The person who built it is gone, and everyone is afraid to touch it
- Auditors, insurers, or customers are asking about security and backups that a file on a share cannot honestly provide
Any two of these and you should be planning the move before it becomes an emergency migration, which is the same project with worse pricing and no sleep.
The three migration paths
| Path | What it means | Typical cost | Typical timeline |
|---|---|---|---|
| 1. Move the data, keep Access as the front end | Tables move to SQL Server; your familiar Access forms and reports stay, now linked to a real database engine | $8,000 to $18,000 | 3 to 6 weeks |
| 2. SQL Server back end plus a modernized front end | Data moves to SQL Server and the most-used screens are rebuilt properly, often as a web app, while the rest phases out over time | $15,000 to $40,000 | 6 to 12 weeks |
| 3. Full rebuild as a web application | SQL Server plus a complete purpose-built application; Access retires entirely | $25,000 to $75,000+ | 2 to 6 months |
Path 1 is the workhorse. It removes the corruption risk, the size limit, and most of the multi-user pain in a few weeks, while your team keeps the screens they know. Many businesses stop there happily. Paths 2 and 3 make sense when the forms themselves are the problem, when remote access matters, or when the business has outgrown what the original design assumed.
What the work actually consists of
Schema conversion
Access data types, indexes, and relationships get translated to their SQL Server equivalents. Microsoft's SQL Server Migration Assistant handles the mechanical part; the judgment calls it cannot make, such as fixing missing keys and inconsistent types that Access tolerated for years, are where experience earns its fee.
Query and logic conversion
Access queries that ran fine locally can crawl when pointed at a server, because Access may drag entire tables across the network before filtering. The fix is moving heavy lifting into SQL Server views and stored procedures. This step is the difference between "we migrated and it got slower" and "we migrated and it got dramatically faster," and it is the step DIY migrations skip.
Data cleanup
Years of Access use accumulate duplicates, orphaned records, and fields whose meaning changed in 2019. Migration is the one natural moment to fix that. Expect cleanup to be a visible line item on any honest quote; on messy databases it can be a third of the project.
Testing and cutover
A trial migration into a test environment, side-by-side validation of reports and totals against the old system, then a cutover on a quiet weekend with the old file kept as a read-only fallback.
Can we do it ourselves?
A technically confident team can run SSMA and get tables moved. Honestly, for a small, clean, single-user database, that may be all you need, and we would tell you so. The projects that come to us are the other kind: linked tables that crawl, queries that time out, corruption scars, and forms held together by two decades of patches. If your database runs something your business cannot live without for a week, the professional path costs less than the failed weekend attempt it replaces.
Find out which path your database needs
Send us a note with roughly what the database does, how many people use it, and the file size. We will tell you which path fits, what it would cost, and whether staying put a while longer is actually fine. That answer is free.
Get a free migration assessmentOr call (630) 548-5614. You can also try the cost calculator for a quick planning range.
Frequently asked questions
Will our reports and forms still work?
On Path 1, yes, that is the point: forms and reports keep working against linked SQL Server tables, with slow spots tuned during the project. Paths 2 and 3 replace screens deliberately, starting with the ones causing the most pain.
What does SQL Server itself cost?
Often nothing. SQL Server Express is free and its 10 GB per-database limit comfortably holds most former Access databases. Businesses that outgrow Express move to Standard licensing or a cloud-hosted database, and we will tell you if you are on that trajectory before you spend anything.
How much downtime should we expect?
Typically one weekend for cutover. Your team leaves Friday on the old system and starts Monday on the new one, with the old file preserved read-only as a safety net.
Our database is also our CRM. Should it become one?
Sometimes the right destination is not SQL-plus-Access but an actual CRM. If the database mostly tracks customers and follow-ups, look at our CRM migration services; if it tracks operations a CRM cannot model, SQL Server is home. We will give you a straight answer either way.