Help for owners
My business data lives in Google Sheets and it has outgrown it
Short answer
A sheet is a good notebook and a poor database: it has no enforced rules, no per-record permissions and a stated size limit of 20 million cells. When duplicates, overwrites, slowness or access problems are frequent, move one process at a time to a database with a simple screen, while the sheet stays as the backup.
Does this sound like your situation?
- The same customer appears three times with different spellings.
- Several sheets must be updated by hand to keep numbers in step.
- I cannot give staff access to only their own rows.
- Automations that read and write the sheet fail or hit limits.
- Reports take someone half a day to assemble.
Why does this happen?
A sheet does not enforce rules
Any cell accepts any value. Nothing stops a text in a date column, a duplicate order number or a blank required field. A database can refuse such entries.
There is a stated size ceiling
Google states a limit of up to 20 million cells or 100MB for spreadsheets created in or converted to Sheets. Real use becomes slow well before that.
Confirmed by support.google.com
Access is all or nothing per file or range
Google offers Viewer, Commenter and Editor roles and protected ranges, but its own help says protection is not a security measure. It is not a way to give each staff member only their own records.
Confirmed by support.google.com
Automation hits request limits
Scripts and tools that read and write the sheet are subject to API quotas, which causes 429 errors as volume grows.
Relationships are faked with lookups
Customers, orders and products are linked by copying text between tabs. When one name changes, the links silently break.
What can I do about it today?
- Back up the sheet todayMake a dated copy of the file, and keep it somewhere only you can open. Do this before any change.
- List what the data is used forWho types in it, who reads it, which reports and which other tools depend on it. This list becomes the plan.
- Stop adding new usesResist adding another tab for another process. Each one is another thing to migrate.
- Clean the worst duplicates by handWork on a copy, merge obvious duplicates in the key lists such as customers, and note rules you applied.
- Pick the one process that hurts mostOrders, stock or bookings: choose one, not all. That is where a move should start.
When should I bring someone in?
- The business cannot run if the sheet is lost or corrupted.
- Staff overwrite each other or see data they should not.
- Several systems need the same data and keep getting out of step.
How do I handle it?
- Understand the data as it isI read the tabs, find the real entities, such as customers and orders, and list the rules people follow without writing them down.
- Design a small databaseRecords are linked by identifiers, required fields and valid values are enforced, and roles control who sees what.
- Import with checksData is cleaned and loaded in a trial run, with counts and totals compared against the sheet before anyone relies on it.
- Give people a simple screenStaff get forms and lists that look familiar, so the move does not stop work.
- Run both for a short periodThe sheet stays as the reference until the numbers match, then it is made read-only and archived.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Do I have to leave Google Sheets completely?
No. Sheets can stay for ad-hoc analysis and exports, while the records that run the business live in a database.
Will I lose my data in the move?
The migration is done on a copy, counts and totals are reconciled, and the original is kept untouched.
Is there a related page for Excel?
Yes, the help page on a business that runs on one Excel sheet covers the same step for Excel files.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.