OĞUZ EROLAI·ADS·APPS

Google Sheets as a Database: Limits and When to Switch

13 min readPublished: Updated:

Google Sheets can work as a small record store for form responses, team lists and simple applications. It supports collaboration and version history; multiple users alone do not justify migration. The decision depends on record relationships, conflicting transactions and individual access requirements. A relational database can enforce additional rules centrally, but its design, permissions and application behaviour still need to be implemented and tested.

In this article I explain the difference between a spreadsheet and a database, both tools’ limits in numbers, how to tell when a sheet has started acting as a database, and how the move is done. I also covered the topic in a short video: stop using Excel and Sheets as a database.

What is a database, and how is it different from a spreadsheet?

A database is a system that stores records under rules defined in advance. On the surface it’s tables too: rows and columns. Sheets also offers validation and protected ranges. A relational database can add central constraints, relationships and transaction rules. The following behaviours depend on those rules being configured:

  • Every column has a type. You can’t type “tomorrow” into a date column or “50 pcs” into a number column. A field marked required can’t be left empty.
  • Each fact is stored once. A customer lives once in the customers table; orders link to it by a number. When the customer’s payment terms change, they change in one place.
  • Links are protected. You can’t create an order for a customer number that doesn’t exist, and a customer with orders can’t be silently deleted.
  • Several steps are saved as one transaction. “Save the order and deduct the stock” happens either completely or not at all; nothing is left half written.
  • It enforces permissions itself. The rule for who can see which rows and columns lives in the database.
Top: an orders sheet where the same customer appears as Harbor Supply, Harbour Supply and Harbor Supply Ltd., with two different payment terms, 30 and 45 days. Bottom: in a database, customers and products are separate tables and orders link to both; terms change in one place and a customer or product code that doesn't exist can't be entered.
In a sheet, the customer is retyped on every order and drifts apart over time. In a database, it's stored once and orders link to it. The company names are made up.

Is your spreadsheet already acting as a database?

In many businesses a spreadsheet turns into a database without anyone calling it that. These signs help identify record-management requirements; reaching a particular number is not an automatic reason to migrate:

  • Tabs are linked with VLOOKUP or XLOOKUP. Names come from the “Customers” tab and prices from the “Products” tab. That’s a database relationship built by hand.
  • There’s a manually typed ID column. Someone increments the order number or customer code by looking at the previous row.
  • Rules live only in cells. Sheets can reject invalid input. Forms, scripts and other writing routes still need checks against the same business rules.
  • Status is only a colour. Yellow means “waiting” and green means “done”. An explicit status field makes reporting and reasons for changes easier to manage.
  • Record ownership is unclear. Sales, warehouse and accounting can collaborate, but someone needs responsibility for conflicting changes to the same order.
  • A form or script adds rows. Google Forms, Apps Script or an automation tool fills in rows; the sheet has become an app’s back end.

The limits, in numbers

ExcelGoogle Sheets
Size of a file1,048,576 rows × 16,384 columns per worksheet (Microsoft)20 million cells or 100 MB (Google)
Editing at the same timeCo-authoring in Microsoft 365; on the same cell, the last save winsUp to 100 people working together, with editing restrictions at higher access levels (Google)
Reading and writing from outside—Sheets API: 300 read requests per minute per project, 60 per minute per user; writes have their own, identical quota (Google)
Automation—Apps Script: 6 minutes per execution; total trigger runtime 90 minutes a day on a Gmail account, 6 hours on Workspace (Google)

The Google help page checked on 9 October 2026 lists 20 million cells or 100 MB. This maximum is not a promise of responsive performance at that size. Microsoft’s own page also says Excel is optimised for data analysis rather than serving as a database management system, and that because it doesn’t support relational data, it can’t support referential integrity either (Microsoft Support).

Most businesses never get near these limits. Problems can arise earlier: complex formulas may slow down, changed fields may affect reports, and conflicting edits may need review. Measure these issues in the current file rather than assuming that every shared spreadsheet has them.

Five rules a database can enforce centrally

  1. It rejects records that break the rules. In a database, rules like “this field can’t be empty”, “quantity must be above zero” and “this code can’t repeat” live in the column itself (PostgreSQL constraints). Excel and Sheets validation can reject invalid direct input, rather than only displaying a warning. For Excel, Microsoft’s own page says that when data is copied or filled, the validation messages don’t appear (Microsoft Support), so each writing route needs testing. That Excel behaviour should not be generalised to every Sheets input route.
  2. It protects links. An order is linked to a record in the customers table; you can’t place an order for a customer that doesn’t exist, or delete a customer who has orders.
  3. It saves all or nothing. Saving the order and deducting the stock are written as one transaction; even if the power goes out halfway, no half-written record is left (PostgreSQL transactions).
  4. It queues people writing at the same time. While hundreds of users enter records at once, each works on a consistent view of the data (concurrency control). The app can detect two people trying to change the same record and warn the second one.
  5. It can enforce permissions per row. A rule like “a sales rep sees only their own customers” can be defined inside the database (row security policies). Properly enabled policies and an appropriate application role can limit access on the server. Privileged accounts and policy configuration still need review.

Field names are a contract too. Change database fields and types through versioned migrations, updating applications and reports together. This requires development discipline; it is not an automatic guarantee supplied by a database.

Why do “free tool chains” break?

Using Google Sheets as the back end of a website or app is a commonly suggested route: a form adds a row, an automation tool reads it, a script sends an email. This arrangement can work at an appropriate scale. These risks need monitoring and a maintenance plan:

  • The per-minute quota runs out. The Google Sheets API allows 300 read requests per minute per project and 60 per user; anything above that is rejected with a “too many requests” error and has to be retried after a wait (Google). Reading on every visit increases request volume; batching and caching can reduce unnecessary calls. On the same page, Google says it plans to start charging for quota overages in 2026.
  • Scripts hit time limits. Apps Script can’t run longer than 6 minutes per execution, or more than 90 minutes of total trigger time a day on a Gmail account (Google). Measure runtime and consider dividing the work into batches with retry handling before a limit stops execution.
  • The chain hangs on one person’s account. Installable triggers always run under the account of the person who created them (Google). When that person leaves and their account is closed, the automation stops too.
  • When a column moves, the wrong data is read. If someone inserts a column or renames a header, an automation that reads columns by position quietly starts reading a different column; it doesn’t error, it produces wrong results.

The Sheets API applies an individual update request atomically: if part of the request is invalid, the update is not applied. That is not the same scope as a transaction spanning several systems or a complete policy for competing user edits. Account for API behaviour when designing the workflow; using a sheet as a back end is not wrong in every case.

When should you stay in a spreadsheet?

  • When collaborators can share the data, input rules are clear and measured workload remains manageable.
  • When the work is a calculation or an analysis: a budget, a scenario, a one-off comparison.
  • When data is pulled from another system to be reviewed for a report.

Businesses that move to a database don’t drop Excel either: records are kept in the database, and the list needed for analysis is downloaded to Excel. That’s the right arrangement.

What can a simpler Sheets solution look like?

Start with a stable identifier per record, an explicit status column and clear field definitions. A Sheets data entry form may be sufficient for new submissions. Cell protection can reduce accidental formula edits, while filter views support different working views. Keep the existing data where these features satisfy the workflow.

A custom app becomes more relevant when each user may see only assigned records, an order approval needs coordinated stock checks, or changes require review. In concurrent entry, the important question is the rule applied to a record rather than the number of collaborators alone. Moving Excel sources can be assessed separately through Excel to SQL migration.

Protect the headers when Sheets feeds an application

Once a form, AppSheet app or script reads a sheet, its column headings may become application field names. Renaming “Tel” to “Phone number”, inserting a notes column or sorting records identified by row number can be a structural change for software even when the sheet still looks fine to a person.

  1. Separate raw data from views. Keep the application’s read/write tab stable. A human-facing view can use QUERY on another tab: =QUERY(Raw!A:F,"select * where E = 'Open' order by B desc",1). Typing a note beside a changing query result does not attach it to the source record; notes need a record identifier.
  2. Use permanent record IDs. A row number changes after sorting and is not an identity. Assign an immutable ID at creation and use it for lookups and updates.
  3. Protect headers and structure. Protect the raw tab’s headers and relevant ranges. Before changing a field, list every form, script and report that depends on it.
  4. Release new fields together. Test the consuming application’s compatibility, then add the agreed column. Version field-name changes. Appending a column may preserve some position-based code, but does not guarantee compatibility by itself.

What this does not solve: two people independently reading and updating one record can still conflict. Saying Sheets has no atomicity at all would also be wrong: Google’s Sheets API documentation states that changes within a request are applied atomically. That does not automatically provide transaction and conflict controls for an application’s entire workflow across multiple requests.

Checked on 24 October 2026, the same document lists 300 reads per minute per project and 60 per user per project, with separate equivalent write quotas. If quota failures, overwritten records or recurring field shifts occur, review business rules and a database migration rather than relying only on locked headers.

How do you move from a spreadsheet to a database?

  1. Tabs become tables. Customers, products, orders and movements become separate tables.
  2. Repeated information moves to its own table. The customer name and terms typed on every row move to the customers table; the order keeps only the customer number.
  3. Dropdowns become links. Fixed values such as a “status” list or a “warehouse” list live in their own table.
  4. Formulas become rules or calculated fields. “Total = quantity × price” becomes a calculation nobody can overwrite.
  5. Old data is cleaned on the way in. Duplicates like “Harbor Supply” and “Harbour Supply” are merged at this stage, and broken rows are listed separately.
  6. Compare results side by side. Use trial copies for reconciliation and identify the authoritative editing source and cutover time for live work.

There are three kinds of option: desktop databases such as Microsoft Access, no-code tools that connect to a sheet such as AppSheet, or a custom web app that runs on a server and that your team uses in a browser. I build the last kind: I read your spreadsheet and turn it into an app on PostgreSQL with user logins, permissions per person and a change log. The process and a sample screen: turn Excel or Google Sheets into a multi-user web app.

Frequently Asked Questions

Is Google Sheets a relational database?

Google Sheets is a spreadsheet with storage, collaboration and validation features. Relational foreign keys and individual row-access policies are different from a dropdown or protected range. Decide which rules need to be enforced centrally rather than treating the presence of multiple editors as the deciding factor.

How many rows can Excel hold?

An Excel worksheet holds up to 1,048,576 rows and 16,384 columns (Microsoft Support). In practice the file starts to slow down well before that, as formulas and links grow.

What is the Google Sheets row limit?

In Google Sheets the limit is on cells, not rows: a file can have up to 20 million cells or 100 MB (Google Support). In a sheet with 20 columns, that’s about 1 million rows. This is a theoretical calculation from cell count; other sheets and the file-size limit also matter.

Can I use Google Sheets as a database for a website or app?

Yes, at an appropriate scale and with properly designed access. Form responses and internal team lists are examples. Individual record privacy, complex relationships or coordinated transactions may justify an application and database. Sheets version history is useful, but it is not necessarily the same requirement as a separate record of every approval in a business process.

Access or Excel?

Access is a real database: typed columns, relationships and forms. But it’s a desktop application; it wasn’t designed for phone use or for many users working together over the internet. If your team works from different places and from phones, a web app that opens in a browser is the better fit.

If I move to a database, do I have to stop using Excel?

No. Records are kept in the database, any list you need is downloaded as an Excel file, and analysis carries on in Excel. The one thing that has to stop is typing the same information into both the sheet and the system by hand.

Back to top ↑