Replacing a Microsoft Access Database: Your Options in 2026

A Microsoft Access database is often the most important piece of software a small business owns, and the one it thinks about least. Someone built it years ago to track jobs, stock, members, policies or orders. It grew a table at a time, a few people learned its quirks, and it has quietly run part of the business ever since.

Then something forces the question. A new laptop arrives without Access on it, a member of staff wants to work from home, the person who built it retires, or IT points out that the version you use is no longer supported. Suddenly the Access database that “just works” looks like a risk.

This guide sets out your realistic options in 2026, from simply upgrading Access to replacing it with a modern system, and how to move your data without losing anything along the way. It is the kind of decision we help with through our legacy system modernisation work, but the aim here is to help you think it through, whichever route you choose.

Why businesses are looking again at their Microsoft Access database

The trigger for many firms is Microsoft’s support calendar. When a product reaches the end of support, Microsoft stops providing security updates, bug fixes and technical help for it. The software keeps opening, but any flaw discovered afterwards stays unfixed. The dates that matter for Access are:

• Access 2016 and Access 2019: support ended on 14 October 2025, along with the rest of Office 2016 and 2019, as Microsoft’s list of products reaching end of support in 2025 confirms. Earlier versions were already out of support.
• Access 2021: the Access 2021 lifecycle page gives a retirement date of 13 October 2026, and the same date applies to Office LTSC 2021.
• Access 2024: supported until 9 October 2029.
• Access for Microsoft 365: the subscription version keeps receiving updates for as long as you pay for a plan that includes it.

So if your Access database runs on a copy bought outright in the last decade, there is a good chance it is now unsupported. That alone does not mean you must rebuild anything, but it does mean a decision is due.

Signs your Access database has reached its limits

Support dates are only part of the picture. Access was designed as a desktop database, and it shows its age in predictable ways as a business grows. Microsoft’s own Access specifications set a maximum size of 2 GB for a database file and a theoretical ceiling of 255 concurrent users. In practice, most small firms run into trouble long before either limit. Common warning signs include:

• Slowness and lock-ups when more than a handful of people have the Access database open at once.
• Corruption scares, where the file needs repairing after a crash or a dropped network connection.
• Remote working is painful. Opening an Access file over a VPN or a slow connection is unreliable, and there is no simple way to use it from a phone or tablet.
• Mac users are left out, because Access only runs on Windows.
• One person understands it. The forms, queries and VBA code were written by someone who has moved on, and nobody else dares change them.
• Data lives in several copies, with spreadsheets exported from Access, edited separately and never quite reconciled.

If that last point sounds familiar, it is the same pattern we describe in our guide to the signs your business has outgrown spreadsheets. Access is often the step a business took after spreadsheets, and it can be outgrown in exactly the same way.

Is an old Microsoft Access database a security risk?

It can be, for two separate reasons. The first is the unsupported software itself. The National Cyber Security Centre’s guidance on obsolete products says that once a product stops receiving security updates it should be treated as untrusted, that access to it should be limited as far as possible, and that you should plan to move away from it.

The second is the way Access databases tend to be stored and shared. The whole Access database is usually a single file on a shared drive, which anyone with access to that folder can copy, email or take home on a memory stick. A database password, if there is one, is usually shared by everyone rather than each person having their own login, and there is rarely a record of who changed what. If the Access database holds personal data about customers or staff, that matters under UK GDPR, whichever version of Access you run.

None of this means you should panic. It means the Access database deserves the same attention as any other system holding important business data, and the end of support is a sensible moment to give it that attention.

Start by mapping what the database actually does

Before comparing options, take stock. Many businesses underestimate how much an old Access database does, because its work is spread across forms, queries, reports and macros that people use without thinking. A short inventory saves a great deal of money later. Write down:

1. The tables and roughly how many records each holds. This shows the size of the data and where it is messiest.
2. The forms people use every day, and who uses each one.
3. The reports and exports, including any that feed spreadsheets, accounts or mail merges.
4. Any VBA code or macros, such as buttons that send emails, generate documents or update several tables at once.
5. Links to other files or systems, like linked spreadsheets, an accounts package or a shared folder of documents.
6. The pain points, in the words of the people who use it.

This list does two jobs. It shows whether the problem is the Access file, the business process around it, or both. And it becomes the checklist for testing whatever replaces it, so nothing quietly disappears in the move.

Your five options for replacing a Microsoft Access database

There is no single right answer. The best route depends on how many people use the Access database, where they work, how unusual your process is, and how much you want to spend now versus over time. Our article on whether to rebuild, refactor or replace legacy software covers the general thinking. For Access specifically, the options usually look like this.

1. Upgrade to a supported version of Access

The quickest fix is to move to Access for Microsoft 365, which is included in Microsoft 365 Business Standard, Business Premium and Apps for business, but not in Business Basic. Databases built in recent versions usually open with little or no change. This deals with the support problem but not the structural ones: it is still a Windows-only desktop file with the same limits on size, remote use and multiple users. It is a sensible stopgap if the Access database is small, used by a few people in one office, and working well.

2. Move the data to SQL Server and keep the Access front end

Here the tables move into a proper database server, such as SQL Server or Azure SQL Database, while staff keep using the familiar Access forms and reports, now linked to the new tables. Microsoft provides a free tool, SQL Server Migration Assistant for Access, to help with the move. This improves reliability, size limits, backups and security considerably, and it is often the cheapest serious upgrade. The downside is that you still depend on Access on every desktop, and remote or mobile use remains awkward.

3. Rebuild it as a low-code app

Microsoft’s Power Apps platform can host the data in Dataverse and replace Access forms with apps that work in a browser and on phones. This can suit businesses already committed to Microsoft 365. Be aware that users generally need Power Apps licences, which are a monthly per-user cost, and complex Access logic rarely moves across without being redesigned. Low-code still needs someone who understands data design.

4. Replace it with an off-the-shelf product

If your Access database does something many businesses do, such as basic CRM, stock control or job tracking, a ready-made product may now do it better than the Access database ever did. You gain mobile apps, support and regular updates. You lose some of the custom touches, and you will pay per-user subscriptions indefinitely. The data migration still needs care, and it pays to check how easily you could get your data back out again later.

5. Rebuild it as a custom web application

Your Access database becomes a secure web application that runs in any browser, on any device, from anywhere, with proper user accounts and permissions, an audit trail and room to grow. It can connect to your accounts, payments or customer portal. This is the most flexible option and usually the most expensive upfront, and it suits businesses whose process is genuinely their own. We cover what that kind of project involves in our guide to custom software development.

How to choose the right route

A few honest questions narrow the choice quickly:

• Who needs to use it, and where? If the answer includes people on the road, at home, on Macs or on phones, options 1 and 2 will keep frustrating you.
• Is the process standard or special? If competitors do the same thing the same way, look hard at off-the-shelf before building anything.
• How healthy is the database design? A well-structured Access database migrates cleanly. One with duplicated tables and years of workarounds may need redesigning whichever route you pick.
• What will it cost over five years? Compare upfront build costs with licences and subscriptions over the same period, not just the first invoice.
• How much risk can you tolerate during the change? Phased approaches, such as moving the data first and replacing the screens later, spread the risk and the cost.

Many businesses end up combining options: moving the tables to SQL Server now to get off an unsupported file, then replacing the Access screens with a web application in stages. That is a perfectly respectable plan, and often the most affordable one.

Moving the data safely

Whichever option you choose, the riskiest part is usually the data, not the new software. Years of records contain duplicates, blank fields, free-text dates and codes whose meaning only one person remembers. Our data migration checklist goes into detail, but the essentials for an Access database are:

1. Take a full backup of the Access database file and keep it somewhere safe and separate.
2. Clean before you move. Remove duplicates, fix obvious errors and agree what each field actually means.
3. Map old fields to new ones, including anything that needs splitting, combining or converting.
4. Do trial migrations and have the people who know the data check the results against the original.
5. Run old and new side by side for a short period if the process is critical, then switch over on an agreed date.
6. Keep the old Access database read-only for reference, rather than deleting it on day one.

Data migration is something we do regularly. On the JEENI.com entertainment platform, we worked alongside JEENI’s project manager, designers and back-end developers to turn their designs into a fast, responsive platform, and migrated their data from the old system into the new one. The setting was different, but the discipline is the same: know exactly what you are moving, and check it arrived intact.

What does replacing an Access database cost?

It depends heavily on the route and on the state of the existing database, so treat these as rough UK market ranges rather than quotes from us. Upgrading to a supported version of Access is mainly a licensing cost. Moving the tables to SQL Server and relinking the front end is often a matter of days of specialist work for a tidy database, which typically means low thousands of pounds, plus any hosting. Rebuilding as a low-code or custom web application commonly runs from several thousand pounds into the tens of thousands, depending on the number of screens, users, reports and integrations.

The costs people forget are data cleaning, staff time for testing and training, and ongoing support. Ask any supplier to break those out separately, so you can compare proposals fairly.

Common mistakes to avoid

• Copying every quirk. Rebuilding the old screens exactly, workarounds and all, wastes the chance to fix the process.
• Forgetting the hidden jobs. The report one person runs at month end, or the button that emails a supplier, only gets missed once.
• Leaving users out. The people who use the Access database every day know where it hurts. Involve them from the start.
• Waiting for a crisis. Migrating calmly is far cheaper than recovering a corrupted file with no recent backup.
• Losing access to your own data. Whatever you move to, make sure you can export your data in a usable format whenever you need to.

Microsoft Access database questions we hear often

Will my Access database stop working when support ends?

No. An unsupported version of Access keeps opening and running your Access database. What stops is Microsoft’s security updates and fixes, so the risk grows over time rather than arriving on a single day.

Is MS Access still part of Microsoft 365?

Yes, on Windows. Access is included in Microsoft 365 Personal and Family, and in the Business Standard, Business Premium and Apps for business plans. It is not included in Business Basic, and there is no Mac version.

Can we keep using Access and just fix the problems?

Sometimes. If the database is small, used in one office by a few people and well designed, upgrading Access and moving the tables to SQL Server may be all you need for years. If the problems are about remote access, mobile use or growth, patching Access usually delays the decision rather than solving it.

How long does replacing an Access database take?

A straightforward move of the tables to SQL Server can take days. A rebuild as a web application usually takes weeks for a focused system and a few months for a larger one, ideally delivered in phases so staff can use the most important parts early.

Do we need the person who built it?

It helps, but it is not essential. A competent developer can read the tables, queries and code in an Access file to work out what it does. The people who use the database every day are just as valuable, because they know which parts matter.

The bottom line

An ageing Microsoft Access database is not an emergency, but it is a decision you should make on your own timetable rather than after a crash or a security scare. Start by mapping what it does, decide whether you need a supported version, a stronger home for the data, or a proper replacement, and treat the data migration with the care it deserves.

If you would like a second opinion on your own Access database, tell us what it does and who uses it or call us on 01482 212499. We will tell you honestly whether it needs replacing, or just a sensible upgrade.