Modernizing

How to replace Excel or Access with a web application

When several people enter the same data and that data has to follow rules, a web application does the job better than a file. Here are the signs it’s time to change, the options, and five steps to move to a new tool without losing your history or stopping work.

The short answer

A web application is a good replacement for Excel or Access when several people enter the same data and that data has to follow rules. The data sits in one database, every entry goes through a form that checks it, each person has their own account, and reports come out on demand. Excel keeps its place for analyzing numbers.

The move takes five steps, and your team keeps its current tool until the last one. This guide covers the signs that it’s time to change, the options, then each step, with the example of a community organization. Taking over your Excel files is part of J3B Web’s custom web application projects.

1 Inventory 2 Data 3 Screens 4 Migration 5 Switch Excel or Access stays in use Test imports on a copy Web application
The old tool stays in use until the switch.

Signs that a file is no longer enough

Excel and Access are good tools to start with. Trouble begins when the file becomes the whole team’s system. Here are the signs to watch for.

  • Several copies of the same file. The same data is entered in several places, and no one knows which version is current.
  • Only one person understands it. They alone know its formulas, macros or queries. When they’re away, everything waits.
  • Training a new hire takes weeks. They have to learn which tabs not to touch, which columns to fill in and in what order.
  • The file slows down. It takes a while to open, or it locks up when several people use it at once.
  • Work only happens at the office. The file sits on one computer or a local server, and people on the road can’t reach it.
  • Everyone sees everything. A shared file does a poor job of limiting who sees what. With personal information, that’s a risk.

Both programs also have written limits. According to the Access specifications, a database can’t exceed 2 GB, minus the space needed for system objects, or have more than 255 concurrent users. According to the Excel specifications and limits, a worksheet stops at 1,048,576 rows. A file can stay far from these limits and still become hard for several people to use.

On the other hand, Excel remains the right tool for a one-off calculation, an analysis or a budget kept by one person. There’s no rush to replace a file that does its job well.

Three options

When the file is no longer enough, you have three paths. Each one suits a situation.

OptionSuits you whenWhat to check
Keep Excel or Access, better organizedOne or two people use it and the rules are simple.The copies, the backups, who can change what.
A no-code platform, such as Power AppsThe process fits the platform’s building blocks, and the team already works in it, for example in Microsoft 365.The cost per user, the platform’s limits, how to get your data back if you leave it.
A custom web applicationThe rules are specific to your organization, the history is long, or several roles share the tool.The contract, who owns the code, the upkeep after launch.

With custom software, the code can be yours, provided the contract says so. The guide Who owns the source code of custom software? explains what to ask for.

The rest of this guide describes the move to a web application. The first three steps also apply to a no-code platform.

Step 1. Take inventory

Before talking about screens, list what your files actually do. Open each file with the people who use it, and write down the following.

  • The files, tabs and tables, and who fills in each one.
  • The formulas, macros and queries, and the rule each one applies.
  • The forms and reports, and who uses them.
  • The rules no one wrote down, such as a cell colour that means “call back” or a column only filled in on Fridays.

Formulas, Excel macros and Access VBA code don’t convert automatically. Each one is read to understand the rule it applies, and that rule is then written into the new software. The table shows what each piece becomes.

In Excel or AccessIn the web application
Tabs and tablesThe tables of a single database, linked to each other.
Formulas and macros (VBA)The software’s rules, checked by automated tests.
Access formsWeb screens that check every entry.
Queries and reportsSearches, statistics, and PDF or Excel reports.
Shared fileAn account for each person, with rights based on their role.
Backup copiesAutomatic backups of the database.

Step 2. Choose the data to move

Not all the old data has to come along, or go through an import. There are four choices, and they can differ from one table to the next.

  1. Import everything. The full history stays searchable in the new tool. It’s the choice that takes the most work, because every old record has to meet the new software’s rules.
  2. Import the recent years and keep the rest in an archived file, read-only.
  3. Re-enter the records in the new application. The team reviews each record as it enters it, and the forms check every entry. It takes time to type in, but the team validates its data one record at a time.
  4. Start fresh from a chosen date. New records go into the application, and the old file stays open for reference.

Whatever you choose, plan a cleanup. An old file often holds duplicates, categories typed ten different ways, dates stored as text or merged cells. With an import, each case is fixed once, in the import tool, rather than by hand. With re-entry, it’s fixed when the record is entered.

Step 3. Rethink the screens

Copying the file as-is into a browser would keep its flaws. The screens start from each person’s work, meaning what they enter, in what order, and what they need to see next.

  • Forms that check. A date is a date, a required field can’t stay empty, a category is picked from a list.
  • Roles. Each person sees their own files, the coordinator approves the timesheets and management looks at the statistics.
  • Exports. People who like Excel keep it for their analyses. The application produces an Excel file or a PDF from the same data, in one click.

Show the team a working version early and often. On its custom web application projects, J3B Web gives a demo every two weeks, on a staging site where the team tries each new feature with its own cases.

Step 4. Migrate and check the data

The migration is prepared during development. An import tool reads the old file or the Access database without changing it, then writes the data into the new database. It runs from the first weeks on a copy of your real data, so surprises show up early.

To know whether everything arrived, the tool compares the before and the after.

  • The number of records in each table.
  • The totals that matter to you, such as hours, amounts or the number of active members.
  • The anomalies. Every rejected record is written to a file, so a person can decide what to do with it.

A tool you can rerun as many times as needed makes the final import predictable. The Agence Distinction case study shows this method on an old system with more than 4,000 clients and 13,000 invoices, and the legacy software modernization page describes it step by step.

When the team re-enters its data instead of importing it, the forms do this work. They check each entry as it’s typed.

Step 5. Switch over

The switch is the moment the team stops using the old tool. It can happen in two ways.

  • All at once, on a set date. The day before, the old file becomes read-only, the final import runs and the counts are compared one last time.
  • One module at a time. A first part of the application replaces the Access database, then another replaces the Excel file a few months later. The team adjusts in stages.

A parallel period lets you compare the results of both tools, provided it has an end date. Without one, everything gets entered twice, and the two tools end up out of step. A switch rehearsed on a copy and backed by a rollback plan is simpler for the team. Keep the old file archived read-only, and plan a short training session on the day.

An example, Trait d’Union Montérégien

Trait d’Union Montérégien is a community organization. Its timesheets were filled in with Excel, and the rest of its data lived in an Access database that held more than 15 years of history. The data had grown too heavy for these tools.

J3B Web built a custom management tool that brings together the members’ files, volunteer matching, the timesheets and ten statistics reports, with PDF and Excel reports produced in one click. The move happened in two stages. The first version went online in October 2025. The Access data wasn’t imported, because the organization preferred to check it while entering it directly in the new application. The timesheet module followed in February 2026, after testing on a staging server, and the Excel timesheets ran alongside it for the first month.

Learning the Excel timesheets took days, sometimes weeks of training. In the application, entry is guided, and training takes a few minutes. To process the timesheets, the office staff export a report that already contains every calculation.

The monthly and yearly reports took weeks. The office staff compiled one Excel spreadsheet per employee to produce the statistics presented to the board of directors. Now they pick the report, confirm or change the pre-filled filters, and the application calculates all the statistics. When the organization needs a new report, it gives J3B Web the details, and the report is added within a few hours. It then stays in the application, and it can be updated.

Before you start, three questions are enough for a first call. Who uses the file, what it really does, and which old data your team still looks up. With those answers, a developer can propose a plan.

Sources

Pages read on November 8, 2026.

Frequently asked questions

Can you keep using Excel after moving to a web application?

Yes. The application can produce Excel files from its data, for your analyses and charts. The data itself is entered in one place.

Do Excel macros and Access VBA code convert?

Not automatically. Each formula, macro or query is read to understand the rule it applies, and that rule is then written into the new software. The ones no one uses anymore can be left out.

Do you have to move all the old data?

Not necessarily. You can import everything, import the recent years and archive the rest read-only, re-enter your records in the new application and check them as you go, or start fresh from a chosen date. The choice depends on the data your team still looks up.

Power Apps or custom software?

A no-code platform such as Power Apps suits a process that fits the building blocks it offers, for a team that already works in Microsoft 365. Custom software suits rules specific to your organization, data with a long history, or a need to own the code.

Do you have to stop working during the migration?

No. Your team keeps Excel or Access until the switch. The data import is prepared and checked on a copy, then one last import runs when you change tools.

Bobby Bougie, founder of J3B Web

The author

Bobby Bougie

Founder and programmer analyst · J3B Web

Bobby Bougie has been a programmer analyst since 1997 and founded J3B Web in 2003. Bobby loves finding new ways to solve problems and to make clients’ days simpler, often by thinking outside the box.

Let’s talk about your files

Show Bobby the Excel file or the Access database your team uses today. The first call lasts 30 minutes, with no commitment.