Your Access database still opens, but its version may no longer get security fixes. Access 2016 and Access 2019 reached end of support on October 14, 2025, and Access 2021 followed in October 2026 (Microsoft).
The safe fix is an inventory first, then one of four routes: move the tables to SQL Server and keep Access as the front end, rebuild on Power Apps, convert the Access database to a web app, or move operations into an ERP such as Odoo. Devvista is a software development and growth agency that replaces Access databases with web applications and Odoo ERP. This guide compares each Microsoft Access alternative and gives a migration plan, the risks and scoping estimates.
01 Which Access Versions Are Still Supported, and What End of Support Means
Microsoft is clear about what end of support means: no new security updates, no non-security fixes and no assisted support (Microsoft Lifecycle, products ending support in 2025). The database keeps working. What changes is that a newly found flaw in the Access or Office code on that PC will stay open.
| Access version | Support status (Microsoft Lifecycle) |
|---|---|
| Access 2016 | Ended October 14, 2025 |
| Access 2019 | Ended October 14, 2025 |
| Access 2021 | Retired in October 2026 |
| Access LTSC 2024 | Mainstream support to October 2029 |
| Access in a Microsoft 365 subscription | Supported under the Modern Lifecycle Policy while licensed and kept current |
Sources: Microsoft Lifecycle, products ending support in 2025, Microsoft Lifecycle: Access 2021, Microsoft Lifecycle: Access LTSC 2024. If the version is the only problem, upgrading is the cheapest fix. Most companies searching for an MS Access replacement have a second problem: the database now runs the business, and it was never built for that.
02 Why Access Databases Turn Into a Business Risk
Access suits one department and a handful of users. Trouble starts when it becomes the order system or the inventory book. Find your cause:
- It slows down or corrupts when several people work at once. Access allows 255 concurrent users on paper (Access specifications), but a shared-drive file opened over a busy network is where corruption starts.
- It is close to the size ceiling. An .accdb file is capped at 2 GB including system objects (Access specifications).
- Remote staff cannot use it. Access is a Windows desktop program, so remote staff depend on VPNs or remote desktop.
- Only one person understands it. The logic lives in VBA and macros written by someone who has moved on.
- It feeds on spreadsheets. Linked Excel files, hardcoded file paths and manual imports hold critical steps together.
Items one and two point to the data layer; three and four mean the application itself needs replacing.
03 Four Microsoft Access Alternatives Compared
| Route | What changes | Fits when | Watch out for |
|---|---|---|---|
| Access front end + SQL Server back end | Tables move to SQL Server or Azure SQL; forms, reports and VBA stay in Access | Users are in one office, the app works, data size or corruption is the pain | Still Windows-only; still depends on whoever maintains the VBA |
| Power Apps + Dataverse | Data moves to Dataverse; screens rebuilt in Power Apps | You already pay for Microsoft 365 and the app is mostly forms and lists | Every user needs a Power Apps plan; complex VBA has no direct equivalent |
| Custom web application | New browser-based app on a server database, logic rewritten and tested | Remote users, customer or supplier logins, integrations, long life ahead | Highest build effort; needs a written spec of today’s rules |
| ERP such as Odoo | Orders, stock, purchasing and invoicing move into standard ERP modules | The database is really running operations next to separate accounting software | Business process changes; not suited to niche one-off workflows |
These are not exclusive. Moving the tables to SQL Server first stops corruption and size problems quickly, and the front end can then be replaced on a calmer timeline.
04 How Each Route Works in Practice
Keep Access, move the data to SQL Server
Microsoft’s SQL Server Migration Assistant for Access (SSMA) assesses the database, converts the schema, migrates the data and produces a report of errors and warnings to fix (Microsoft’s Access to SQL Server migration guide). Access then links to the new tables over ODBC. SQL Server 2022 Express, Microsoft’s entry-level edition with no license fee, caps a database at 10 GB (SQL Server 2022 editions).
Rebuild in Power Apps
Access can export tables to Dataverse and keep its existing forms and reports working against them while you rebuild screens. Microsoft notes that only supported data types are exported and that Dataverse requires a Power Apps plan (Microsoft: migrate Access data to Dataverse).
Convert the Access database to a web app
No reliable tool converts forms and VBA automatically; wrapper tools only stream the desktop app into a browser. A real conversion is a new application with its own database, user roles and audit trail, which is what our custom software development team builds.
Move operations into Odoo
If the database tracks orders, stock or jobs and someone retypes totals into QuickBooks, you are maintaining a homemade ERP. Odoo covers those flows as standard modules, with custom modules for what is unique to you. See our Odoo implementation service for how that rollout runs.
05 A Step-by-Step Access Database Migration Plan
- Back up and freeze design changes. Copy both files and stop design changes until the inventory is done.
- Inventory every object. Count tables, queries, forms, reports, macros and VBA modules, plus every linked table, Excel file and mapped drive.
- Map users to tasks. Spend 30 minutes with each regular user on their weekly tasks. Unused objects are common and do not need rebuilding.
- Choose a route per function, not per database. Order entry might move to Odoo while a niche calculation becomes a small web app.
- Move and clean the data first. Add missing primary keys, fix dates stored as text, merge duplicates, then compare row counts and totals per table.
- Rebuild logic with test cases. For each VBA routine, record real inputs and outputs from the old system and require the new one to produce the same results.
- Run both systems in parallel for one full business cycle, usually a month-end.
- Cut over and archive. Keep a read-only copy of the old file for lookups and audits.
Want a second pair of eyes on your inventory? Book a call and we will go through your Access file with you and tell you which route fits.
06 The Risks Most Access Migrations Underestimate
VBA hidden in form events. Rules such as "orders over a credit limit need approval" often sit in a button’s click event, not in a module anyone documented. Search every form’s code before you estimate.
Linked Excel and hardcoded paths. A macro that imports S:\Prices\current.xlsx every Monday is part of the system. List each one and decide whether it becomes an import screen, an API feed or goes away.
Reports. Access reports with grouping, subreports and printed layouts (invoices, packing slips, labels) take longer to rebuild than the screens. Collect a printed sample of each one users still need.
Access-only query functions. Queries using Nz() or DLookup() need rewriting on SQL Server. The SSMA report lists what it could not convert, which makes it a useful sizing tool.
07 Our Access Developer Retired: What to Do This Week
- Secure the files and admin rights. Make sure the company, not one person, holds the current front end, the back end, any workgroup or database passwords and the server or share it lives on.
- Check for source code. If users only have an .accde file, the editable VBA has been compiled out. Look for the matching .accdb on the developer’s old machine or backups before anything else.
- Stabilize. Split front end and back end if they are one file, schedule compact and repair, and set up nightly backups.
- Document while it still works. Record screen videos of each user’s weekly tasks. They become the spec for whatever replaces it.
08 What It Costs to Scope and Replace an Access Database
Scoping cost depends on the object count and how much logic hides in VBA, not on the number of users. These are our estimates for the inventory and fit-gap work alone, before any build:
| Database size (estimate) | Typical contents | Scoping effort (estimate) |
|---|---|---|
| Small | Under 20 forms, a few reports, little VBA | A few days |
| Medium | 20 to 60 forms, macros, linked Excel files | One to two weeks |
| Large | 60+ forms, heavy VBA, several linked systems | Two to four weeks |
For the build itself, internal business tools commonly land between $15,000 and $50,000, as covered in our custom software development cost guide. If the work moves into an ERP instead, the Odoo pricing guide breaks down license and implementation ranges. A scoped inventory turns these ranges into a real number.
09 How to Know the Migration Worked
- Data reconciles: row counts and money totals match the old system for the same cut-off date.
- Reports match: last month’s key reports produce the same figures in both systems.
- Workarounds disappear: count the spreadsheets and manual retyping steps before and after.
- Remote access works: staff outside the office can do their tasks without remote desktop.
- Nobody waits on locks: record lockups, "database is corrupt" messages and repair runs per month; the target is zero.
Common mistakes: rebuilding unused objects, migrating dirty data to clean later, skipping the parallel run, and copying Access screen for screen instead of fixing the process.
10 Where Devvista Fits, and When We Are Not the Right Choice
Devvista is a good fit if your Access database runs orders, jobs, stock or customer records for a growing team, if staff need it outside the office, or if the person who built it is gone. We inventory the file, recommend a route per function, then build a custom web application or an Odoo rollout and test it against the old outputs.
We are not the right choice if a single user needs a small personal database; upgrading to a supported Access version is cheaper. Companies whose database is really a homemade ERP should also read our QuickBooks Desktop end-of-life guide and our Dynamics GP replacement guide, since the accounting decision usually comes next.
Book a call about your Access database and leave with a clear route and a scoping plan.
? Frequently Asked Questions
→ Related Resources
More on replacing software your business has outgrown: