Our business runs on an old Access database. How do I replace it safely?

By Ranjit Bhinge, founder of Blur Studio · Updated · 6 min read

Short answer: Replace an Access database in stages: list what it does, clean and move the data, rebuild the screens and reports people actually use, then run the old and new side by side for a week or more before switching off Access. Microsoft Access is a desktop database program that many small firms use for customer lists, jobs and orders. Your data moves easily. The forms, reports and hidden rules take the time.

Ranjit Bhinge

You have an Access database the business depends on, and you want to move off it without losing data or stopping work.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Access databases tend to be built by one person over many years. It works, nobody else understands it, and the person who built it may have left. Replacing it is a sensible move, but the risk is not the data. The risk is the things Access does that nobody wrote down. This guide gives you a safe order of steps.

Why people replace Access, and when not to

Microsoft's own specifications say an Access database file can be up to 2 gigabytes and supports up to 255 concurrent users. Those are the hard ceilings. In practice, trouble starts well before them: slow screens on a shared network, files that corrupt, and no way to use it from a phone or from home.

Real reasons to replace it:

  • Staff need access away from the office.
  • The file is slow or sometimes corrupts when several people use it.
  • The person who understands it is leaving or has gone.
  • Customers or partners should see part of it.
  • You want to connect it to email, accounting or your website.

Reasons to wait: it works, three people use it in one office, and nothing is changing. An old tool that works is not an emergency. Plan the move, but do not rush it.

What moves and what must be rebuilt

An Access file bundles four different things. They move in different ways.

PartWhat it isHow it moves
TablesThe stored data: customers, jobs, ordersMoves well. Export or use a migration tool. Needs cleaning.
QueriesSaved questions: "all unpaid orders over 30 days"Rewrite as saved views or reports. Easy to list, medium to rebuild.
FormsThe screens people type intoRebuild. Design them around how people work now, not a copy of the old screens.
Reports and macros or VBA codePrintouts and automatic steps, often hiding business rulesRebuild, and find them first. This is where surprises live.

VBA (Visual Basic for Applications) is the code language built into Access. If someone wrote VBA, it holds rules like "when an order is marked shipped, email the customer." Those rules will not come across by themselves.

The safe order of steps

  1. Take a copy and stop making changes. Make a read-only backup of the .accdb file today. Freeze design changes to the old file while you plan.
  2. List everything it does. Open every table, query, form, report and macro. Write one line for each: what it is, who uses it, how often. Ask each user to show you their weekly routine. This is the inventory, and the most valuable part of the project.
  3. Mark what you will keep, drop or change. Most databases are full of forms nobody opens. Drop them. A smaller scope is a faster, cheaper move.
  4. Clean the data. Duplicates, blank fields, inconsistent spellings, dates stored as text. Fix these before you move, not after.
  5. Choose the target. See the next section.
  6. Move a copy of the data and check it. Compare row counts and spot-check 20 records by hand. Check totals, such as sales for one month, match in both systems.
  7. Rebuild screens and reports for the keep list. Start with the one workflow people use daily.
  8. Run both in parallel. See below.
  9. Switch over, make Access read-only, and keep it. Keep the file for at least a few months as a reference. Do not delete it.

What can replace Access

There are three common routes. The right one depends on how many screens and rules you have.

Route 1: Keep Access screens, move the data to a server database

Microsoft publishes SQL Server Migration Assistant for Access, a tool that migrates Access databases to SQL Server (Microsoft's server database) or Azure SQL (its cloud version), with a documented step for linking existing Access applications to the new database. The aim is to keep your familiar screens while the data moves to a bigger, shared database. It does not give you a web app, because the screens are still Access screens. It is a stepping stone.

Route 2: Power Apps

Power Apps is Microsoft's tool for building business apps with little code. Canvas apps, its drag-and-drop style, can connect to Dataverse (Microsoft's cloud data store for business apps), SharePoint (Microsoft's shared sites and lists) and hundreds of other data sources, and work across browsers and mobile devices. Dataverse also supports one-time imports of Excel and CSV files. The per-user plan, Power Apps Premium, is listed at $20 per user per month billed yearly, as of November 2026. Check Microsoft's pricing page for the figure that applies to you, as it notes prices shown may differ at checkout.

It is a good fit if your company already uses Microsoft 365, has a few simple forms, and someone on staff will own it. It is a weaker fit when you have complex rules and many reports, or when outside people such as customers need to log in, since you would need to check Microsoft's licensing for them.

Route 3: A custom web app

A web app is software that runs in a browser, so anyone with a login can use it from anywhere. A custom one is built around your steps, with no per-user fee. This is the best fit when the Access file holds real business rules, when customers or outside staff need access, or when you want to own the result. See Excel to web app, which has the same logic for spreadsheets, and internal tools for what this kind of software looks like.

For a bigger system, one that replaces Access and the spreadsheets around it, the right answer may be a staged custom ERP. For a business with several loose spreadsheets feeding the database, start with replacing five spreadsheets with one customer database. To decide whether to buy or build, read build vs buy software.

The parallel run

This is the step that protects you. For at least a week, longer if you do month-end work, staff enter data in the new system and the old one is kept up to date from it or checked against it. Compare three numbers at the end of each day: new records created, total sales or hours entered, and open items. If they match for a full cycle (a week, or a month-end), you switch. If not, you have found a hidden rule before it cost you money.

Make switching a decision with a date, a named person, and a way back. Keep the old file untouched and read-only until the first month-end has closed in the new system.

Checklist for forms, reports and VBA

  • Every form has a named owner and a keep, drop or change mark.
  • Every report has been printed once and compared with the new version, line by line.
  • Every macro or VBA module is described in one plain sentence: "when X happens, do Y."
  • Every saved query is either a view in the new system or marked dropped.
  • Any link to Excel, Outlook or accounting software is listed.
  • Permissions: who may see or change what.

Common mistakes

  • Copying the old screens exactly. You pay to rebuild habits that existed only because of Access limits.
  • Skipping the inventory. The hidden rule surfaces in month three.
  • Switching on a Friday afternoon. Choose a quiet week.
  • Deleting the old file. Keep it.
  • No owner. Someone must decide what "done" means.

How I'd approach this

I would spend the first week only on the inventory and the keep list, and I would expect it to shrink the project. Then I would pick the lightest route that fixes your actual pain. If the problem is only file size and sharing, route 1 may be enough. If you need a browser, phone access or customer logins, I would build a small web app for the one workflow people use daily, run it in parallel, and move the rest over in stages.

I do this kind of fix, and you own the result. If you want help with the inventory or a quote scoped to your keep list, see what a build with me includes. If you would rather first see how far you can go without a developer, read building an internal tool without a developer.

Questions people ask

What is the best replacement for an Access database?

It depends on what the database does. For plain storage and sharing, a server database with your Access screens kept may be enough (Microsoft documents a way to link Access applications to SQL Server). For browser or phone access, Power Apps or a custom web app fits better. See build vs buy software.

Can I replace Access with Power Apps?

Often yes, for simple forms and Microsoft 365 users. Power Apps canvas apps connect to Dataverse, SharePoint and many other data sources. It costs $20 per user per month on the Premium plan billed yearly (as of November 2026), so check the total for your headcount against a one-time custom build.

Will my data transfer cleanly from Access?

Tables usually do. Clean them first: duplicates, blank fields and dates stored as text cause most problems. After moving, compare row counts and a month of totals in both systems.

What about the VBA code and macros in my database?

They do not move on their own. List each one in plain words ("when X, do Y") and rebuild it in the new system as a rule or automation. For ideas on what can be automated, see business process automation.

How long should I run the old and new systems together?

At least one full cycle of your work: a week for daily operations, through a month-end if you invoice monthly. Switch only when the daily numbers match.

Is it safe to keep using Access while I plan?

Yes, if you take a backup copy first. Access supports files up to 2 GB and 255 concurrent users per Microsoft's specifications, so check the file size before you plan, and freeze design changes while you work.

More in this topic: Problem solving: custom software (22 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…