Should you replace it at all?
Access is still a capable tool for a small office on one network. If the database works, a few people use it from Windows computers in the same building, and somebody can maintain it, leaving it alone is a respectable decision.
These are the usual reasons to move:
- Remote work. Access files don’t behave well over the internet or a slow VPN, and a dropped connection can corrupt a shared file.
- Phones and Macs. Access is a Windows desktop program, so staff on phones, tablets or Macs can’t use it directly.
- Size. Microsoft sets a limit of 2 GB, minus system objects, for a single database file.
- The person who built it is leaving. A system only one person understands is a risk whatever it runs on.
- Access web apps are no longer an option. Microsoft no longer recommends building them in SharePoint and points people to Power Apps.
Take inventory first
An Access database is usually much more than its tables, and the forgotten parts are what make a replacement fail.
| Part | What to record | Why it matters |
|---|---|---|
| Tables | Row counts, relationships, linked tables | Linked tables may point to Excel files or servers nobody remembers. |
| Queries | Which ones are still used | Many hold business rules, such as how a discount is worked out. |
| Forms | Who uses each, and what they do | This is where your daily work happens, so it sets the shape of the new screens. |
| Reports | Which ones people actually print or send | Reports are often the hardest thing to reproduce exactly. |
| VBA and macros | What each one automates | This logic doesn’t move by itself. It has to be rewritten. |
| People | Who uses it, from where, and when | It decides how you can safely run the switch. |
Ask users what they do outside the database, too. A spreadsheet kept next to it often reveals a feature the database never had.
Your options, side by side
| Option | What changes | Good when | Watch out for |
|---|---|---|---|
| Keep the Access screens, move the data to SQL Server | Tables move; forms and reports stay in Access, linked to the server | Size or reliability is the only problem | Users still need Access on Windows |
| Microsoft Power Apps | Screens are rebuilt in Microsoft’s low-code tool | You already use Microsoft 365 and your forms are fairly simple | Per-user licensing, and complex reports need another tool |
| Another no-code builder | Data and screens are rebuilt on that platform | A small internal tool with simple rules | Limits on logic, and your app lives on their platform |
| A custom web app | Everything is rebuilt, around how you work now | Staff need it anywhere, and your rules are particular | The highest upfront cost; you depend on whoever builds it |
Moving the tables to SQL Server
Microsoft provides a free tool for this, SQL Server Migration Assistant for Access (SSMA). It assesses the database, converts the table definitions, moves the data, and can link the Access tables to the new server so existing forms keep working. It targets SQL Server and Azure SQL.
Run its assessment report before anything else, because it lists what won’t convert. Then test on a copy, and expect some queries to need attention: a query that runs fine locally can be slow when it has to pull a table across the network.
Plan the switch
- Back up the database and store a copy where nobody will touch it.
- Compact and repair it, then clean the data. Our guide on organizing scattered data helps if there are side files to bring in.
- Export your important reports as they look today, because they become the test for the new system.
- Rebuild in small parts, starting with whatever hurts most.
- Run old and new side by side for a period, and compare totals and report outputs.
- Choose a cutover date, freeze the old file as read-only, and keep it available.
Where Ciscom fits
Ciscom has real experience with Microsoft Access, and we build custom web apps from scratch that run on phone, tablet and computer. That is the right choice only when the options above fall short, so we are happy to tell you if moving the tables or trying Power Apps would do the job.