On October 13, 2026, Microsoft ends support for Office LTSC 2021, and Access 2021 goes with it. Access 2016 and Access 2019 already reached the same point a year earlier, on October 14, 2025. If your business runs on an Access database that someone built years ago, and it is installed from a one-time-purchase copy of Office rather than a Microsoft 365 subscription, that date is the point where the software under it stops being maintained.
Nothing dramatic happens on the day itself. The database will still open on October 14. Forms will still work and reports will still print. That is exactly why this deadline tends to get ignored, and why it is worth understanding what has actually changed.
What "End of Support" Actually Means
End of support means Microsoft stops shipping security fixes, bug fixes, and technical help for that version. The software keeps running. What it no longer gets is protection against problems discovered after the cutoff date.
For a database that holds customer records, pricing, job history, or employee information, that matters in three practical ways:
- Security. Office files are a common route for malware. A vulnerability found next year in an unsupported version stays open on every machine running it.
- Compatibility. Windows and the rest of Office keep changing. Over time, an unsupported Access install becomes more likely to break after an unrelated update, and nobody at Microsoft is going to fix it.
- Insurance and compliance. Cyber insurance questionnaires and client security reviews increasingly ask whether you run unsupported software. "Yes" is an answer that can raise premiums or cost you a contract.
Access itself is not being discontinued. Access included with Microsoft 365 business plans that include the desktop apps is still supported and still updated. The deadline applies to the perpetual-license versions: 2016, 2019, and now LTSC 2021.
Which Version Are You On?
Open Access, go to File, then Account. Under Product Information you will see either "Microsoft 365" (subscription, still supported) or a named version such as "Office Professional Plus 2019" or "Office LTSC Professional Plus 2021." Check every computer that opens the database, not just your own. In a small office it is common to find three different versions on three desks.
Your Realistic Options
There are three sensible paths. None is right for everyone, and the best one depends far more on how the database is used than on the technology.
1. Move to Access in Microsoft 365
The quickest fix is to put everyone who uses the database on a Microsoft 365 plan that includes the Access desktop app. The database usually opens unchanged, and you are back on supported software within a day or two.
Treat this as a stopgap rather than a solution. It fixes the support problem but none of the problems Access databases tend to accumulate: a file that corrupts when too many people use it at once, no access from outside the office without a remote-desktop workaround, no audit trail of who changed what, and one person who understands how it all fits together.
2. Keep the Access Front End, Move the Data to SQL Server
Access can act as the forms-and-reports layer while the data itself lives in SQL Server, either on a server you already have or in Azure SQL. This is often called splitting the database. Your staff keep the screens they know, and the data gains proper multi-user handling, scheduled backups, and real permissions.
This fits a database that works well and that people like, but that has outgrown a single shared file. It still requires the Access desktop app on each machine, so it is usually paired with option 1.
3. Replace It With a Web Application
The longer-term option is to rebuild what the database does as a web application: the same records and workflows, reachable from a browser on any computer or phone, with user logins, permissions, and a history of changes. No desktop software to license or keep patched on each machine.
This is more work up front. It is usually the right call when the database has become central to how the business runs, when people need it outside the office, when more than a handful of people use it at once, or when the person who built it has left.
How to Tell Which One Fits
A few honest questions usually settle it:
- How many people use it at the same time? One or two, Access in Microsoft 365 is fine. More than five or six, the shared-file model is already a risk.
- Does anyone need it away from the office? If the answer involves remote desktop or emailing the file around, a web application solves a real problem.
- Who can change it? If nobody currently on staff can safely edit a form or query, the database is already a liability regardless of the support date.
- Is the business changing hands? A buyer will look hard at a critical system that only the seller understands. See our post on what to check about a business's software before you buy it.
What a Migration Actually Involves
Whether you split the database or replace it, the data is the easy part. The work is in everything around it.
Cleaning Up the Data
Long-lived Access databases collect duplicates, free-text fields used for three different purposes, dates typed as text, and tables nobody remembers creating. Moving to SQL Server or a web application forces those questions to be answered, because a proper database will not accept "sometime in March" in a date column.
Finding the Hidden Business Rules
This is the part most often underestimated. Access databases encode how the business works in queries, macros, and VBA code: how a discount is calculated, which jobs count as overdue, what happens when an order is marked complete. Those rules were rarely written down anywhere else. Every one has to be found, understood, and either carried over or deliberately dropped.
Protecting the Reports People Depend On
Somebody prints a report every Monday, and somebody else exports a spreadsheet for the accountant every month. Ask every user which reports and exports they rely on before anything changes, and check the new system reproduces them, numbers included.
Running Both Systems in Parallel
For anything that touches money or customers, run the old and new systems side by side for a short period and compare the results. It costs a little extra effort and catches the rule nobody mentioned before it causes a problem.
What to Do Now
- Check the Access version on every computer that opens the database.
- Make a full backup of the database file and store a copy off-site.
- If you are on 2016, 2019, or LTSC 2021, move those users to Microsoft 365 now.
- Write down who uses the database, what for, and which reports matter. That list is the starting point for any longer-term decision.
Getting onto supported software buys time. It is worth using that time to decide whether the database should still be at the centre of the business in three years.
Need a Second Opinion?
We help businesses across Los Angeles, the San Gabriel Valley, the Inland Empire, and Orange County review aging systems like Access databases and decide whether to keep, upgrade, or replace them. If you're buying, selling, or retiring from a business, or just want someone to look at what you are running on, see how we help with business transitions, email info@businesscodingpros.com, or call (562) 231-6488.