By Mo Hussein

4 min read

If your spreadsheet holds customers, jobs and their history, and more than one person edits it, it's already a database. It's just one with no rules about who can change what, and no record of who did. Move it to a no-code database tool if a few people share it and the process is simple. Have custom database software built when several roles need different views, the data has to link to other systems, or a mistake in it costs real money.

How a spreadsheet turns into a database

Nobody sets out to run the business on a spreadsheet. It starts as a list. Then someone adds a column for status, a tab for invoices, a lookup to join the two, colour coding that only one person understands and a copy called "FINAL v3" because the main one got broken.

At that point the spreadsheet is doing a database's job: storing records, linking them together and holding the history. It does it without the things a database gives you, such as one version of the truth, rules that stop bad data going in and a log of every change.

Signs it's time to move it

  • There's more than one copy, and people argue about which is current.
  • One person understands the formulas, and things go wrong when they're off.
  • The same customer or job is typed into the spreadsheet and somewhere else, such as your accounts or CRM.
  • People need to see some rows but shouldn't see others, like pay rates or customer details.
  • Someone has overwritten or deleted data by accident, and you only found out later.
  • It's slow to open, or it breaks on a phone.

One or two of these and a tidy-up might be enough. Several, and the spreadsheet has become the riskiest thing in the office.

Option one: a no-code database

Tools like Airtable, Notion databases and Microsoft Lists sit between a spreadsheet and custom software. You get proper records, linked tables, forms and simpler permissions, and you set it up yourself.

They're a good next step when a few people share the data, the process is fairly simple and nobody outside the business needs access. The limits show up later: per-user pricing that grows as you hire, permissions that are either too broad or too fiddly, and automations that become their own tangle. They're still worth trying first. If you outgrow one, you'll know exactly what you need from the next system.

Option two: custom database software

Custom database software is a database built for your data, with screens on top built for your people. Underneath it's usually a standard database such as PostgreSQL. On top, each role gets the screens it needs and nothing else.

It's the right move when:

  • Different roles need different views and permissions, such as office staff, people out on jobs, managers and sometimes customers.
  • The data needs to link to other systems, such as Xero, your calendar or your website's enquiry form.
  • You need an audit trail of who changed what, and when.
  • The rules matter. A job can't be marked done without a signature, for example, or a quote can't go out below a minimum price.

A CRM is the most common example, and our guide to custom CRM or off-the-shelf covers that case. Job tracking, stock, compliance records and rotas all follow the same pattern.

Moving the data across

The part people worry about is losing what's in the spreadsheet. Done properly, you don't. The spreadsheet gets cleaned up first, with duplicates merged and blanks filled, and then imported. Someone who knows the data checks it before anyone switches over. Expect the clean-up to turn up records nobody knew were wrong. That's normal, and it's better found now than after launch.

Keep the old spreadsheet read-only for a while afterwards. People trust the new system faster when they can check it against the old one.

Before you decide

List every tab and column in the spreadsheet and write next to each one who uses it and why. Columns nobody can explain can usually go. The rest is the outline of whatever you build or buy next.

Common questions

What is custom database software?

It's software built around one business's data, with a database underneath and screens on top designed for the people who use it. It replaces spreadsheets and generic tools when they no longer fit the way the business works.

Is Microsoft Access still a good option?

Access still works for a single office on Windows, but it's awkward on phones, for remote staff and for sharing with customers. Most new projects use a web-based database instead.

Can we keep using spreadsheets for reports?

Yes. A custom system can export to a spreadsheet whenever you want one, so people can still do their own analysis without editing the live data.

Will we own the data?

Yes. Your data stays yours to export at any time, whichever way you choose to run the system after launch.

See what we build under custom internal tools and databases, get a price range with the project estimate, or book a free discovery call to talk it through.