From Excel to a web app: a guide for owners who run on spreadsheets

When should you turn a spreadsheet into an app?

A spreadsheet is a great tool for one person doing analysis. It is a weak tool for a team running daily work. Look for these signs.

• Many editors: Three or more people change the same file each day.
• Costly mistakes: A typo in a price, date or address has cost you money or a customer.
• Copy and paste: Staff copy data from the sheet into emails, quotes or invoices.
• Phone use: People in the field need to update records from a phone.
• Outside access: Customers or contractors need to see their own data, and only their own.
• Slow files: The file takes a long time to open or crashes.
• One expert: Only one person knows how the formulas work.

If two or more of these sound familiar, an app will probably save you time. If none do, keep the spreadsheet. It is cheap and your team already knows it.

What are the hard limits?

Excel holds up to 1,048,576 rows and 16,384 columns per worksheet, says Microsoft. Google Sheets allows up to 20 million cells per file. Most small businesses never reach these limits. Problems with shared editing and access usually show up much sooner.

What is the difference between a spreadsheet and a database?

A spreadsheet lets anyone type anything in any cell. A database sets rules. A date field only takes dates. A customer can link to many jobs, and each job links back to one customer.

Moving from a spreadsheet to a database is the core of this change. The app sits on top. It gives each person a screen that shows only what they need, with buttons for the actions they take.

For example, a "CRM in Excel" might have one tab of customers and one tab of deals. In a database, each deal links to its customer. The app shows a salesperson only their own deals. It also sends a reminder when a follow-up is due.

What are the real warning signs a spreadsheet has become dangerous?

"Should I move off Excel" is usually asked too late, after something has already gone wrong: two people edited the same file at once and one version won by accident, or a formula broke three tabs away from where anyone was looking and nobody noticed for a month. A few concrete thresholds are worth checking yourself against, rather than waiting for the next incident.

• More than two or three people edit the same file regularly. Past this point, version conflicts and silent overwrites stop being rare and start being routine.
• Any single sheet has grown past a few thousand rows. Excel technically allows over a million rows, but it becomes slow and error-prone well before that, and formulas that reference whole columns get noticeably sluggish.
• The data needs to be trusted as a single source of truth. If two people could reasonably have different numbers in front of them right now and neither would know, the spreadsheet has already failed at its real job.
• It holds sensitive data with no real access control or audit trail. Anyone who can open the file can see and change everything in it, with no record of who changed what.
• Formulas are the business logic. If a single broken or copied-wrong formula could quietly produce wrong invoices, wrong payroll or a wrong inventory count, that is business logic that deserves the same care as code, not a cell that anyone can overtype.

None of these alone means you must move today. Two or three of them together, especially the version-conflict and source-of-truth problems, mean the cost of staying on a spreadsheet has already passed the cost of moving off one.

What are your options for turning a spreadsheet into an app?

These tools let a non-technical owner build a simple app. Prices come from each vendor's own page as of October 2026, in US dollars.

Tool	Best for	Listed price
Glide	Fast mobile-friendly apps built from a spreadsheet or a file	Free plan; Basic $25 a month, Plus $50, Pro $125
AppSheet	Teams already on Google Workspace	Starter $5 per user a month, Core $10, Enterprise Plus $20
Airtable	A shared database with views, forms and automations	Free plan; Team $20 per user a month billed yearly, Business $45
Softr	Portals and simple apps for clients or staff	Free to start, with paid plans for more features and your own domain
Custom app	Complex rules, sensitive data, deep links to other systems	Quoted per project

Glide

Glide builds an app from a spreadsheet, a prompt or a file. Its free plan lets you build but does not let you publish an app. Paid plans set the number of team members and published apps.

AppSheet

AppSheet is Google's no-code app builder. It connects to spreadsheets and cloud storage. Google says Core is included in most paid Google Workspace plans, so you may already have it. AppSheet's own database allows 2,500 rows per database on Starter and Core. Enterprise Plus raises that to 200,000.

Airtable

Airtable looks like a spreadsheet but works like a database. Airtable charges for each user who can edit. Read-only users, form submissions and share links are free. If you go over your plan's record limits, Airtable keeps your data, but you cannot add more until you upgrade. My page on Airtable alternatives compares it with similar tools.

Softr

Softr builds websites, portals and apps on top of your data, including Airtable. It is a good fit for a client portal where each customer logs in to see their own records.

A custom web app

A custom app is software built for your business. You own the code and the data. It costs more to start, but it has no per-user fees from the builder tool and no limits set by a platform.

How do you move data from Excel to an app safely?

Most data loss happens during the move. Follow these steps in order.

1. Make a backup: Save a dated copy of the file somewhere safe. Do not edit it.
2. List what each tab holds: Write down each tab, what one row means, and who uses it.
3. Split mixed data: If one tab holds customers and their orders, split them into two tables.
4. Give every row an ID: Add a unique number to each customer, job or product. The app uses it to link records.
5. Clean the data: Fix spelling, remove duplicates, and make dates and phone numbers use one format.
6. Remove merged cells and notes: Apps cannot read merged cells or color codes. Turn colors into a status column.
7. Test with a sample: Import 50 rows first. Check every field came across.
8. Import the rest: Count the rows before and after. The numbers should match.
9. Run both for two weeks: Keep the spreadsheet as a backup while the team uses the app.
10. Lock the old file: Make the spreadsheet read-only so nobody keeps editing it.

Protect personal data

Customer names, phone numbers and payment details need care. Set app permissions so each person sees only what their job needs. Turn on two-step login for every account. Never share a link to the whole database with an outside person.

What are the limits of no-code apps?

No-code tools are a good first step. Know their limits before you build your whole business on one.

• Per-user costs: Fees grow with each editor you add.
• Platform limits: Row, storage and automation limits can force an upgrade.
• Complex rules: Pricing rules, approvals and multi-step jobs get hard to manage.
• Lock-in: Moving off a platform later can mean rebuilding the app.
• Speed: Large data sets can make screens slow.

When should you bring in a builder?

You can build a simple app yourself in a weekend. Bring in help when one of these is true.

• The app runs your money: Quotes, invoices or payroll depend on it, so a bug costs real money.
• You have many tools: The app must sync with accounting, scheduling or job software.
• Customers log in: Outside users need secure logins and strict data rules.
• The no-code app got stuck: You hit a limit or the app has grown too slow to use.

A builder can also review a no-code app you made and tell you if it is safe to keep. My guide to internal tools shows what businesses build in place of spreadsheets.

How does Blur Studio approach a spreadsheet move?

I start with the spreadsheet itself. I read every tab and formula, because the formulas show the real business rules nobody wrote down anywhere else. Then I design the database and screens around the way your staff actually work today, not the way a generic template assumes they work.

Sometimes the right answer is a no-code tool, and I say so. When a custom app fits better, I build it so you own the code and the accounts. I move the data with checks at each step, so nothing silently goes missing in the move, and I take care of the app after launch. Many owners then add a KPI dashboard on top of the new, cleaner data once it exists.