Short answer: Replace Excel with custom software when the spreadsheet has become the place where work happens: several people edit it every day, other files copy from it, and a wrong cell costs real money. First check whether an off-the-shelf product or a no-code database covers the process. Custom development pays off when the workflow is specific to the business and has to connect to systems that already run it.
Key takeaways
- Size is rarely the trigger: an Excel worksheet holds 1,048,576 rows and Google Sheets allows up to 20 million cells, so most businesses outgrow the process long before the file.
- The real signs are people signs: conflicting copies, one employee who understands the formulas, and no record of who changed what.
- No-code has ceilings: Airtable caps a base at 1,000 records on Free, 50,000 on Team and 125,000 on Business.
- Migration is mostly cleanup: most of the effort goes into deciding which columns mean what, not into writing code.
Signs the spreadsheet has become the system
The spreadsheet usually starts as a quick list of orders, shipments, clients or inventory. Within a few years it holds status columns, colour codes that mean something only to the team, and lookup formulas pointing at other files. Typical signs: two versions of the file circulate by email, month-end takes a day of reconciling, a manager cannot see the current state without asking someone, and errors are found only after a customer complains.
In Israel there is a second reason to look closely. Amendment 13 to the Privacy Protection Law took effect on 14 August 2025 and widened the regulator's enforcement powers. A sheet of customer names, ID numbers and phone numbers attached to emails is hard to control. A system with logins, roles and an audit log is easier to defend.
Three options: off-the-shelf, no-code, custom
| Option | Fits when | Watch out for |
|---|---|---|
| Off-the-shelf (CRM, ERP, field service app) | The process is standard for the industry | Paying for modules nobody uses, bending the process to the product |
| No-code database (Airtable and similar) | A small team, simple relations, few integrations | Record caps, per-seat pricing as the team grows, logic spread across automations |
| Custom internal system | The workflow is specific and must talk to ERP, accounting or a website | Needs a clear scope and someone to maintain it after launch |
The decision framework in build vs. buy software applies here too. For the platform question, the comparison of no-code builders vs. custom development in Israel covers where each one stops scaling. When the spreadsheet is really a sales pipeline, a custom CRM is often the shape the replacement takes.
