Replacing an Access Database or Excel Macro Tool With a Web Application

#replace access database with web app

Founder & Lead Developer

Expert in software development and legacy code optimization

LinkedIn

Almost every company with more than a few dozen employees has one. A department runs its daily work on an Access file or an Excel workbook full of VBA macros, built years ago by a colleague who knew the process well and liked to tinker. That colleague has since moved on, the file lives on a network drive, and nobody dares to touch the macros. If you are thinking about whether to replace an Access database with a web app, this guide is for you. It is written for the people who have to make the decision and sign the budget, not for the developers who will do the work.

We will cover the signs that it is time, the three realistic options, the part most projects underestimate (moving the data and the business rules hidden in the old tool), how to roll out without a risky cutover day, and what to expect on cost and timeline.

Signs it is time to replace an Access database with a web app

A homegrown tool is not a problem by itself. Plenty of Access databases run quietly for fifteen years and do their job. The trouble starts when the tool becomes critical and fragile at the same time. These are the signals we hear most often from operations and finance leads:

  • Only one person still understands how the file works, or that person has already left.
  • The file breaks or locks when two or three people open it at once, so the team has invented a "please close it, I need it" routine over chat.
  • Someone keeps a copy on their laptop "just in case", and now there are several versions of the truth.
  • A Windows or Office update stopped a macro from running, and it took days to find out why.
  • Colleagues working from home or another site need a VPN and remote desktop just to enter a few records.
  • Your IT department or auditor has started asking who can see the data, who changed what, and where the backups are.
  • The file has grown close to the 2 GB size limit of an Access database, or Excel takes minutes to recalculate.

Two or three of these together usually mean the tool has outgrown its form. The business process it supports is still valuable. The container is the weak point.

Your three realistic options

When people decide to move away from Access or Excel VBA, they end up choosing between three paths. Each one fits a different situation, and none is right every time.

Low-code platforms

Tools like Microsoft Power Apps or similar platforms let you build forms and simple workflows on top of a hosted database. They work well when the process is mostly data entry, lists and simple approvals, and when you already pay for the platform as part of a wider licence. The limits show up with complex calculations, unusual reports, or integrations with older systems. Licence costs also grow per user, which can surprise you after the second or third department adopts the tool.

Standard software

Sometimes the Access file is a homemade version of something that exists off the shelf: a small CRM, a ticket system, a stock or asset register, a time tracker. If your process is close to how the standard product works, buying is usually cheaper and faster than building. The honest test is whether you are willing to adapt your process to the software. If the answer is no because the process is part of what makes your company different, standard software will feel like a straitjacket. Our article on when to choose custom solutions over off-the-shelf goes deeper into that decision.

A custom web application

A custom build makes sense when the old tool encodes specific rules that give you an edge, when it needs to connect to other systems (your ERP, accounting, a supplier portal), or when the user group is large enough that per-seat licences add up. A web application runs in the browser, so remote staff and other sites need no VPN tricks. It has a real database underneath, proper user roles, an audit trail and backups that someone is responsible for. This is the path we usually work on through our custom software development and web application development services.

A short workshop with the people who use the tool every day usually makes the choice obvious. If it does not, that is a sign the requirements need more work before anyone writes code.

The hidden part: data and business rules

Most replacement projects that run over budget do so for one reason. Everyone treats the old tool as a set of screens and tables, when it is really a collection of business rules that nobody has written down.

In an Excel workbook, those rules live in formulas, conditional formatting, hidden sheets and VBA modules. In Access, they hide in queries, form events, macros and sometimes in the default values of a table column. A typical example is a discount that only applies to certain customer groups on orders above a threshold, implemented as a nested IF in cell K14 that someone added in 2016. It is in no specification, but the finance team relies on it every month.

Before any new system is designed, someone needs to inventory these rules. In practice that means three things:

  1. Read every query, macro and VBA module and write down, in plain language, what it does and why.
  2. Sit with two or three daily users and watch them work, because they often apply rules by hand that the tool does not enforce.
  3. Confirm each rule with the business owner, since some of them are workarounds for problems that no longer exist and can be dropped.

The data itself needs the same care. Old Access and Excel files almost always contain duplicates, free-text fields that should have been dropdowns, dates stored as text, and records that belong to customers who no longer exist. Cleaning this up belongs in the project plan from the first week. We write migration scripts that can be run again and again against a fresh copy of the old file, so the import can be tested many times before the real switch. Each run produces a report of records that could not be mapped, and the business decides what to do with them.

A phased rollout, with the old tool kept read-only

The riskiest way to replace an Access database with a web app is a single cutover weekend after which the old file is gone. If something is missing, people improvise, and the new system loses trust in its first week.

A safer plan looks like this. First, the new application goes live for one function or one team, with the migrated data, while everyone else keeps working in the old tool. That pilot surfaces the rules nobody remembered. Then the remaining functions move over in small steps, each with a fresh data import. Once everything runs in the new system, the old file is set to read-only and stays available for a few months. People can still look up a historical record or compare a calculation. After an agreed date, the file is archived.

This approach takes a little longer on paper, but it removes the pressure to get everything perfect on day one. It follows the same idea we describe in our plain-language guide to legacy software modernization: replace in slices, keep the business running, and avoid big-bang switches.

What it costs and how long it takes

Costs depend on how many rules the old tool hides and how many systems the new one has to talk to, much more than on the number of screens. As a rough orientation for a custom web application built by an experienced team in the EU:

  • A focused tool for one department, with a handful of forms, a few reports and no integrations, often lands somewhere between 25,000 and 60,000 EUR and takes two to four months.
  • A tool used by several departments, with user roles, approval steps and one or two integrations (for example an ERP export or a single sign-on connection), more commonly sits between 60,000 and 150,000 EUR over four to eight months.
  • Anything that replaces a web of linked Access files and touches several core systems should be scoped in a short discovery phase before anyone quotes a total.

Data migration and the rule inventory are usually 15 to 25 percent of the effort, and they are the parts most often left out of early estimates. Ongoing hosting, maintenance and small changes come on top, typically as a monthly retainer. For a fuller picture of how day rates, scope and integrations drive price, see our article on custom software development costs in 2026.

Compare those numbers with the real cost of the current setup. Count the hours people spend on workarounds, the risk of a corrupted file with no tested backup, and what happens if the one person who understands the macros is on holiday during year-end closing.

Questions to settle before you start

A few decisions make every later step easier:

  • Who owns the process in the business, and who can confirm which rules still apply?
  • Which reports and exports do other teams depend on, even occasionally?
  • Does the data need to stay in a particular country or on your own servers?
  • Which systems should the new tool read from or write to, now and in the next two years?
  • How long must historical records be kept, and in what form?

You do not need perfect answers. Writing down what you know and what is still open is enough to get a useful first estimate.

How Wolf-Tech can help

We help companies move business-critical Access databases and Excel macro tools into maintainable web applications. That covers the rule inventory, the data migration scripts, a phased rollout with the old tool kept as a read-only fallback, and running the new system afterwards if you want that. If the honest answer turns out to be standard software or a low-code tool, we will say so.

If you have a file like this somewhere on your network drive, send a short description of what it does and how many people use it to hello@wolf-tech.io, or take a look at wolf-tech.io. A first conversation is usually enough to tell which of the three paths fits.