Replacing Excel with a web app: from spreadsheet debt to a production-ready application

That one Excel file has been running for years. It does what it needs to do, until a second user joins, a formula is accidentally overwritten, or the macro stops working after an Office update. We build web applications that take over your spreadsheet logic and turn it into a multi-user, auditable and scalable system.

Excel migration Multi-user web app Postgres + Next.js Audit trail RBAC
Discuss your Excel case More about web apps

The moment your Excel file needs to become a production app

Excel is a great tool. For modelling a calculation, analysing a dataset or setting up a one-off report, it's incredibly fast. Many business-critical processes started life as a spreadsheet: a quote calculator, a time tracker, a stock list, a commission calculation. It worked. Until the organisation grew.

The tipping point rarely arrives all at once. It is an accumulation of small frictions. Two people open the file at the same time and one person's changes overwrite the other's. A colleague drags a column down and breaks a formula. The macro that builds the monthly report suddenly stops working after an Office update. An external party emails their version as an attachment and nobody knows which file is the source of truth any more. In software engineering this is known as spreadsheet debt: technical debt that builds up in a tool that was never designed for this.

At that point it is time to turn the spreadsheet into a proper application. Not as a rejection of what Excel did well (your existing logic is years of business knowledge), but as a formalisation of it in an environment that can handle multiple users, audit requirements and growing data volumes. We build that transition for you: a web application that takes over the business logic from your worksheets, with an interface your team understands immediately, and a database that ensures no row ever quietly disappears again.

Six signs your Excel file has outgrown itself

Not every Excel file needs to become a web app. But if you recognise one or more of the situations below, you are by now paying a higher price to keep the worksheet alive than it would cost to replace it.

Multi-user conflicts and race conditions

Two colleagues edit the same file on the shared drive or via OneDrive co-authoring, and changes disappear or clash. With heavy use you get warnings about conflicting versions, or worse: silent overwrites that nobody notices until a total no longer adds up.

No data integrity

Excel doesn't know that a customer ID must be unique, that an amount cannot be negative or that a date must fall within the financial year. One wrong paste and referential integrity is gone. In a database with constraints and validations, such an error is simply impossible.

No audit trail

Who changed that price? When was that percentage modified? Excel keeps no change history, not even with track changes on. For processes where accountability matters (finance, HR, contracts, compliance) that is a fundamental problem.

Fragile macros and VBA legacy

Your file runs on VBA macros written by a colleague who no longer works here. Nobody dares to touch them. Office 365 updates regularly break functionality. Power Query is a great help for analysis, but for production processes it is unsustainable.

Performance as row counts grow

Beyond ten thousand rows, recalculation slows down, the file takes minutes to open and sorting crawls. Formula cascades with VLOOKUP, INDEX/MATCH and SUMIFS across thousands of cells bring even modern hardware to its knees. A database does the same work in milliseconds.

Limited mobile use

Your engineer in the field, your salesperson on location or your customer who has to submit data themselves: none of them wants to open an Excel sheet on a phone. A web app works anywhere, on any device, with an interface designed for the task rather than for cells.

Migration approach: extracting data and logic from your worksheets

An Excel file is more than a table of numbers. It contains business logic hidden in formulas, rules of thumb built into conditional formatting, and exceptions that live in comments or hidden columns. If you simply export the data and pump it into a new application, you lose that knowledge. Our migration approach is built around carefully uncovering it.

In the first phase, we carry out what we call business logic discovery: we go through every formula, every named range, every macro and every pivot table field. A SUMIFS with four criteria isn't a technical detail — it's a business rule. We document what that rule means in plain language, check with you whether it's still current, and then translate it into code in the new application. This exercise often surfaces rules that nobody knowingly remembered, or that are outdated and can be dropped.

We also take care of the data extraction. That is more work than a CSV export. We map the implicit schema of your worksheet: which columns logically belong together, which are calculated and which are source data, and where there are duplicates or inconsistencies. We then design a normalised Postgres schema in which every entity gets its own table, with foreign keys, constraints and indexes in the right places. If in doubt, we run the old Excel file and the new system in parallel for a while to validate that the results match.

For processes that must be idempotent, such as generating invoices, sending emails or firing API calls, we build in explicit safeguards. A single double click must never create two invoices. Excel cannot guarantee that; a well-designed web app can.

The web app stack we convert your Excel into

We choose technology that is mature, fast and maintainable. No exotic frameworks that nobody may still support in two years' time, but a stack that major companies run in production worldwide and that plenty of developers can work with.

Front end

Next.js or Astro with React, TypeScript and a component library such as shadcn/ui or Mantine. Server-side rendering for a fast first load, client-side interactivity where users expect it. Tables that can handle tens of thousands of rows through virtualisation.

Back end and database

Node.js or a Python back end on top of PostgreSQL. Postgres is the workhorse database for modern web apps: ACID guarantees, strong data types, JSON fields where needed, built-in full-text search, and battle-tested on production workloads of petabytes.

Authentication and RBAC

Login via a mature solution such as Auth0, Clerk or a custom NextAuth setup. Role-based access control ensures a salesperson sees something different from a board member. Single sign-on with Microsoft Entra or Google Workspace for those who already use it.

Audit log and versioning

Every change to an important entity gets a record in an audit table: who, when, old value, new value. For financially sensitive data we use event sourcing or soft deletes with restore. The full history can always be retrieved.

Hosting and deployment

Hosting preferably in the EU, with us or with your own cloud provider. A CI/CD pipeline via GitHub Actions or GitLab. Automated tests, infrastructure as code and monitoring with Sentry and uptime checks. A crash on Friday doesn't mean your Monday is ruined.

Integrations

Integration with your accounting package, CRM, email, Mailchimp or supplier APIs. Excel got its data via copy and paste; a web app uses authenticated API endpoints with retries, error handling and webhooks for real-time updates.

Next.js Astro React TypeScript PostgreSQL Node.js Auth0 Clerk Tailwind shadcn/ui Sentry GitHub Actions

Common Excel files we replace

We see the use cases below week after week at SMEs and larger organisations. Recognise your own spreadsheet? Chances are the solution follows a familiar pattern.

📊

Quote and calculator tools

A quote spreadsheet with dropdowns, calculation formulas and discount scales — often created by a single commercial colleague — becomes an internal web app where every salesperson issues a quote, with an approval flow, history per client and automatic PDF export.

⏱️

Time tracking and project tracking

The weekly timesheet Excel with VBA totals is replaced by a time-tracking app that works on mobile, is linked to projects and clients, and automatically generates invoices in your accounting software at the end of the month.

📦

Inventory and asset management

An inventory spreadsheet with manual updates becomes a system with barcode scanning, real-time stock levels, minimum-level alerts and reorder suggestions. No more rows deleted by accident.

👥

Client portal and self-service

An Excel file you email to clients every month (invoices, reports, interim figures) becomes a secure client portal where each client sees their own data, downloads documents and fills in forms, without your team acting as the go-between.

💰

Commission and bonus calculation

Monthly commission spreadsheets with nested IF formulas and manual processing become an automated calculation based on CRM data, with visibility for the employee and an approval step for the manager.

📋

Workflow and intake forms

Excel forms that circulate by email, get filled in, sent back and processed manually are replaced by an online intake form with status tracking, automatic reminders and routing to the right team member.

Four steps from Excel to a working web app

Our approach is iterative and transparent. We deliver a concrete result in every phase, so you are not left waiting for months for something you had doubts about long ago.

Discovery

We go through your Excel file together with the people who use it every day. Which formulas are crucial, which macros are quietly running in the background, which exceptions are hidden in comments? Output: a functional design and a data model.

First working version

Within a few weeks we build a first version of the web app with the core flow. You can already log in, enter the most important data and run the main calculation. Not the full feature set, but a working product to build on.

Migration and expansion

Existing data from Excel is imported and validated. We add the supporting functionality: reports, integrations, advanced roles. In the meantime the old and new systems run in parallel so your team can get used to it and validate the results.

Go-live and further development

The application goes live and the Excel file moves to the archive. We actively support you for the first few months, monitor performance and add new functionality based on usage. A real web app grows with you.

Frequently asked questions about replacing Excel with a web app

When should I really move away from Excel?
When more than two people work in the file at the same time, when data errors lead to visible problems, when macros break regularly, or when mobile use and auditability become requirements. One signal is reason enough for a conversation; several make it urgent.
Will the business logic in my formulas be lost during migration?
Not if it is done carefully. We do business logic discovery: every formula, macro and pivot table is analysed, documented and validated before it ends up in code. This often improves the quality of the logic, because rules become explicit instead of hidden in cells.
Can I import my existing data from Excel?
Yes. A one-off import from Excel or CSV is a standard part of the project. We validate the data against the new schema, flag inconsistencies and give you the chance to clean them up before the web app goes live. This exercise often exposes long-neglected data hygiene issues.
Does the web app work offline or on poor connections?
A modern web app can be built with offline functionality using Progressive Web App techniques: entered data is stored locally and synchronised as soon as the connection returns. That is ideal for field engineers or international users with variable internet quality.
Is a web app more expensive than Excel with OneDrive co-authoring?
In licence costs, yes; in total cost, usually not. Work out how many hours a month your team spends on Excel maintenance, fixing errors, manual reporting and version conflicts. A well-built web app earns that time back, on top of clear benefits for data integrity, auditability and scalability.
What if we later want to analyse something in Excel again?
No problem. The web app gets an export function to Excel or CSV for ad-hoc analysis. Excel won't disappear from your organisation; it simply goes back to what it does well: analysis and modelling, not production workflows.
What about integration with our other systems?
We use APIs to connect web apps to your accounting software, CRM, email marketing tool or suppliers' APIs. Where Excel still relied on copy-paste or CSV hand-offs, data now flows in real time, authenticated and with error handling. See also our integrations page.
Can we start with one part and expand?
We even recommend it. Start with the most painful use case — for example the quote spreadsheet or the time tracker — and only migrate other processes later. That way you validate the approach with limited risk and expand based on proven results.

Why Appfront builds your Excel replacement

We start with your file

No generic template, no low-code platform you have to configure yourself. We analyse your actual Excel file, formula by formula, and build an application around that specific logic.

SME realism, no enterprise overhead

A web app that replaces your spreadsheet doesn't need a forty-page architecture diagram. We deliver something that works within weeks and grow with you as your needs grow.

Maintenance and further development

Excel needs maintenance from your people; a web app needs it from us. We stay involved after go-live, monitoring, retraining where needed and extending the app based on real-world use.

Ready to replace your Excel?

Send us your spreadsheet, anonymised or under NDA, and within a week we'll come back with an initial analysis: which logic needs to carry over, which data is usable, and what a web app would look like.

Discuss your Excel case

Edit content