Migration & Conversion

Is Microsoft Access Still Supported? Dates by Version

I get this question a few times a month, usually from an office manager who just saw a warning on a blog or got a memo from their IT contractor: "Our Access is out of support — is our database going to stop working?" It's a fair worry, and the answer is less scary than it sounds, but there are real things you need to know. Let me walk you through what "support" actually means, how to find the dates for your version, and when it genuinely matters.

What "supported" really means

When people ask "Is Microsoft Access still supported?" they're usually mixing up two different things. The first is whether the product keeps running. The second is whether Microsoft still issues security updates and will help you if something breaks. Those are not the same.

Access is part of Microsoft Office, and each version follows what Microsoft calls a lifecycle. A version moves through a few stages:

  • Mainstream support — bug fixes, security patches, and design changes.
  • Extended support — security patches only, no feature work.
  • End of support — no more patches of any kind. The software still opens and runs, but you're on your own if a flaw is found.

An important point that catches a lot of owners off guard: when a version reaches end of support, your database files don't expire and nothing locks you out. Your forms, reports, and data keep working exactly as they did the day before. What changes is the risk profile, not the functionality.

End of support does not mean your Access database stops working. It means Microsoft stops patching the program behind it. The file is fine; the software around it is what ages.

The two kinds of Access you might have

Before you can check any dates, you need to know which Access you're running, because the two kinds age very differently.

Microsoft 365 (subscription) Access is the version most businesses pay for monthly or yearly. As long as your subscription is active and you install updates, it stays current. There's no fixed "end of support" date to worry about — it keeps rolling forward. If you're on 365, the support question mostly answers itself.

Perpetual Office is the one you bought once as a boxed or one-time-purchase product: Access 2016, 2019, 2021, and so on. These each have a fixed support window, and that's where end-of-support dates actually bite.

How to find the support dates for your version

I'm not going to print specific end dates here, because Microsoft occasionally adjusts them and a wrong date in a blog post is worse than no date at all. Instead, here's the reliable way to get the right answer for your exact version:

  1. Open Access, go to File → Account (or File → Help in older versions), and read the product name and version number.
  2. Note whether it says "Microsoft 365" or a year like "2019" or "2021."
  3. Search Microsoft's official lifecycle page for that exact product. Check Microsoft's current lifecycle page for the retirement dates rather than trusting a date you read secondhand.

That three-minute check gives you a trustworthy answer instead of a guess. Here's roughly how the common versions line up today, in plain terms:

Your versionSupport situationWhat to do
Access 2010 / 2013Past end of supportPlan to move off; security risk is real
Access 2016 / 2019Older perpetual; nearing or at the endCheck the lifecycle page, then budget to upgrade
Access 2021 / 2024Current perpetual, still supportedNo urgent action; note the end date
Microsoft 365 AccessSupported while subscription is activeKeep updates turned on

Why an unsupported version is a problem in practice

If the file still opens, why care? A few concrete reasons come up with my clients:

  • Security. Once patches stop, any flaw discovered later stays unpatched forever. For a database holding customer records, that's a liability you don't want.
  • Compatibility drift. Older Access versions start to argue with newer Windows updates, newer printer drivers, and newer versions of SQL Server or SharePoint. The breakages are usually small and annoying, then one day they're not.
  • No lifeline. If something goes wrong, Microsoft won't help, and finding anyone who still remembers the quirks of a 2010-era setup gets harder every year.
  • New hires and new machines. Try buying a fresh laptop and installing Access 2013 on it cleanly. It's a bad afternoon.

I have an old version — do I need to rush?

Not usually. End of support is a signal to plan, not an emergency. Here's how I'd think about priority:

  1. If your database holds sensitive data and sits on a machine connected to the internet, move sooner. Security is the driver.
  2. If it's a standalone tool on one offline PC doing a narrow job, you have more breathing room — but still put an upgrade on the calendar.
  3. If multiple people share the database over a network, treat an upgrade as part of your normal IT refresh rather than a crisis.

One thing worth knowing: moving a database to a newer Access version is rarely as simple as opening it in the new program. Older VBA code, long-deprecated functions, and certain references can throw errors on the first open. It's usually a short job, but it's not always zero. If you want a hand with that, my team handles moving older databases onto a current, supported version and ironing out the code that breaks along the way.

A word on cost expectations

People assume an upgrade means rebuilding everything. Most don't. A typical move to a newer version is testing, fixing a handful of code or reference issues, and confirming reports still print right. We work at $40 per hour for existing databases, or give a fixed quote up front if you'd rather know the number before we start. A small, well-built database is often a couple of hours of work, not a project.

The short version

So, is Microsoft Access still supported? If you're on Microsoft 365, effectively yes, as long as your subscription is current. If you bought a specific year's version, it depends on that version — check Microsoft's lifecycle page for your exact build. Either way, an unsupported version keeps running; the thing you're really managing is security and compatibility risk over time.

If you're not sure which version you're on, or you've got an older database and want to know what moving it would actually involve, send me a note describing your setup. I'm happy to take a look and tell you plainly whether it's a quick job or something to plan for.

Related Services

Access to SQL Server Migration

Learn more →

Migrate to the Cloud

Learn more →

Convert Excel to Access

Learn more →

Related Articles

MS Access vs SQL Server: Which Is Right for Your Business?

MS Access vs SQL Server: which is right for your business? I break down the real differences, costs, and warning signs so you can pick the right database.

Read article →

How to Successfully Migrate Your MS Access Database to the Cloud

How to successfully migrate your MS Access database to the cloud — hosting options compared, the professional migration process, and common pitfalls.

Read article →

How to Convert Excel to Access Database: The Complete Guide

When should you convert Excel to Access, and how? A complete guide to the benefits, the professional conversion process, and why it's worth doing.

Read article →

Still stuck on this?

Send me the details and I'll take a direct look at your database and give you a straight answer.