Spreadsheet to App: Replacing the Excel File Skip to content
CentriWeb
Not sure where to start?

Tell us how the business runs. We'll tell you what we'd build first.

Book a call
For builders and tradesPreBuildMore homeowner enquiries, more trust, more jobs won. For sole tradersOwner CFOA financial operating system for owners who do the books.
Need something of your own?

We build custom software too.

Talk to us

Spreadsheet to app: replacing the Excel file the business runs on

Moving from a spreadsheet to an app makes sense when the file has become the business's system. Here are the signs, the steps, and how to switch without stopping work.

Moving from a spreadsheet to an app makes sense when the file has stopped being a tool and become the system the business runs on: several people edit it, mistakes cost money, and nobody is sure what happens if the one person who understands it is away. You switch safely by mapping what the sheet does, building the app alongside it, running both for a short time, then retiring the sheet.

Signs it is time to move from spreadsheet to app

One sign alone is not enough. A few together are.

  • Only one person understands it. They are the formulas, the colour codes and the “don’t touch that column” rules.
  • Several people edit it, or copies exist. Files called “final”, “final v2” and “final v2 Sam” mean you no longer have one version of the truth.
  • Errors cost real money. A wrong price, a double booking or a missed renewal that came from a broken formula or an overwritten cell.
  • It is slow or crashes. The file takes minutes to open, or has grown to dozens of tabs.
  • People need different views. Staff should see their own jobs, customers should see their own status, and the owner should see margins. A sheet has no good way to do that.
  • Information is retyped. Someone copies rows from the sheet into accounting software, an email or a customer’s form every week.
  • You need a trail. Who changed what, and when, matters for disputes, audits or insurance, and the sheet cannot tell you.

Signs you should keep the spreadsheet

A spreadsheet is the right tool for one-off analysis, forecasts and quick calculations done by one person. It is also the right tool while you are still working out the process, because changing a sheet costs nothing. If the process shifts every month, building software around it too early locks in a guess. Wait until it has settled for a while.

What the spreadsheet is actually doing

Before any building, open the file and list what it does. Most business spreadsheets are doing several jobs at once.

Job in the sheet What it becomes in an app
Rows of customers, jobs or stock Records in a database
Formulas for prices, totals and dates Business rules in the code
Colours, notes and tab names that mean something Statuses, fields and categories, written down as real options
Pivot tables and summary tabs Reports and a dashboard
Someone copying data in or out Connections to other systems
Who is allowed to touch what, by habit Logins and permissions

The hidden items are the hard ones. Sit with each person who uses the file and watch them use it. Ask what they do when something does not fit a column. Those answers are the rules the app must follow.

Worked example: a bookkeeping practice and its job tracker

Suppose a small bookkeeping practice tracks every client engagement in one workbook. The details are invented for the example. It has a tab per service, a master list of clients, a column of colours showing who is waiting on whom, and a summary tab the owner updates by hand on Fridays.

Mapping it turns up the following:

  • Three types of user: staff who do the work, a manager who allocates it, and the owner who wants a summary.
  • Six statuses hidden in cell colours, one of which no one can explain.
  • A formula that works out a due date from the client’s financial year end, with an exception someone typed into a note cell.
  • A weekly task that copies completed jobs into the invoicing software by hand.

The first version of the app does only this: one list of jobs with the six statuses written down properly, the due date rule built in, a view for each user type, and the invoicing link. Client logins, document upload and time tracking go on the later list. That is the same discipline as writing a software requirements document: say what is in, and say what is not.

Moving from spreadsheet to app without stopping work

The safest sequence is gradual. There are six steps, and none of them needs the business to pause.

  1. Freeze the structure of the sheet. Agree that no new columns or tabs are added while the app is being planned. Data can keep changing; the design cannot.
  2. Map and decide. List users, tasks, rules and outputs. Decide what the app will do differently as well as what it will copy.
  3. Clean the data. Duplicates, spelling variants, blank cells and mixed formats cause more trouble at import than the software does. Fix them in the sheet while it is still familiar.
  4. Import a copy and test with real examples. Take last month’s work, run it through the app, and compare the results with what the sheet produced. Differences point to rules nobody wrote down.
  5. Run both for a short time. Pick one team, one service or one type of job. They use the app; everyone else stays on the sheet. Treat any difference between the two as a defect to explain.
  6. Cut over and keep the old file read-only. Move the rest across in stages. Keep the sheet as an archive so you can answer “what did it say back then” later.

Agree before the switch who decides when the old sheet is switched off, and tell everyone the date. Without a clear end, two systems quietly run for months and nobody trusts either one.

Expect the first weeks to produce a stream of small requests. That is healthy. It means people are using the app for real and finding the gaps the planning missed.

Options between a sheet and a custom app

You have more than two choices, and a custom build is not always the first step.

  • Tidy the sheet. Lock the formulas, split data from reports, and add a shared template. This is cheap and sometimes enough.
  • A low-code database tool. Good for list-shaped data with simple views. Our guide to Airtable alternatives covers where those tools stop fitting.
  • An off-the-shelf product for your industry. If one exists and fits most of your process, adapting to it is often cheaper than building. Check that you can export your data.
  • A custom app. Worth it when the process is part of how you compete, when the rules are specific to you, or when several systems must talk to each other. For a rough idea of how this is priced, see what custom software costs.

What to ask a developer about a spreadsheet project

  • How will you find the rules that are not written down? A good answer involves watching users as well as reading the file.
  • What will you import, and how will we check the imported data is complete and correct?
  • How will staff work during the changeover, and what happens if the app goes down in the first week?
  • Can I export all of my data at any time, in a format another system can read?
  • Who looks after it afterwards, and what does that cost? Our guide to software maintenance cost explains what is involved.

A developer who asks to see the spreadsheet and the people using it before quoting is doing the right thing. A quote given from a one-line description is a guess.

Things to protect during the move

  • The data. Take a dated copy of the spreadsheet before each import.
  • The person who knows the sheet. Involve them from the start. They are the best tester you have, and they need to feel the app helps them.
  • Your exit. Make sure you can export everything from the app in a common format, and that you own the code and the data.
  • Privacy. If the sheet holds personal details, check the privacy rules for the countries your customers live in before data moves anywhere new.

CentriWeb builds custom software including internal tools that replace spreadsheets, and the first step is a 30 minute call about the sheet you have. We also say so when a tidied sheet or an off-the-shelf tool will do the job. For professional practices, see our page on professional services.

Common questions.

Can an Excel spreadsheet be converted into a web app automatically?

Tools can import the data, but the formulas, the unwritten rules and the habits of the people using it do not convert on their own. Someone has to read the sheet, work out what it does and decide what the app should do instead. That analysis is most of the work.

Should I move to an app or a tool like Airtable first?

If the spreadsheet is a list with a few views, a low-code database tool may be enough. If it holds real business rules, customer logins or links to other systems, a custom app tends to fit better. Our comparison of Airtable alternatives goes through the trade-offs.

How do I move without stopping work?

Run the sheet and the app side by side for a short period with one team or one type of job, compare the results, then retire the sheet. Keep a read-only copy of the old file.

What should stay in a spreadsheet?

One-off analysis, forecasts that change shape every month, and anything only one person uses. A sheet is a good place to think. It is a poor place to run a process that several people depend on.

Related guides.

Custom software · 6 min read

Customer portal: examples and the features people use

Talk to CentriWeb about this

CentriWeb plans and builds portals, web apps and internal tools, and helps businesses decide when building beats buying.

CentriWeb is based in New Zealand and works online with businesses worldwide.

Want this working in your business? We'll map it with you on a call.

A 30 minute call. You'll leave knowing what we'd build first.

Book a call