Kodakod Team
If you get two different answers to the same question, the problem is not Excel — it is that your company has outgrown it. The signs, the hidden cost, and how to migrate incrementally.
In short: Whether it is time to move from Excel to software depends on how many of five thresholds you have crossed: more than three people touching the same data at the same time, a process that depends on one person’s knowledge, reporting that takes a full day or longer, errors that cannot be traced back, and personal data circulating as email attachments. At zero or one, stay in Excel; at two or three, plan a pilot with a single process; at four or five, every delay costs you. Always start the move with the single process that hurts most, never with everything at once.
The decision to move processes into software is usually made in a moment of crisis: a quote goes out with the wrong figure, the same stock gets sold to two customers, or a file corrupts. Yet this is not a decision to leave to a crisis. There are specific thresholds, and once you cross them, spreadsheets begin quietly costing you money.
Below are those thresholds in order. Mark which band your own company falls into.
Threshold 1 — How many people touch the same data?
One person: Excel is entirely sufficient. Recommending software at this stage is unnecessary expense.
Two or three, in sequence: Still manageable, though if file names have started collecting suffixes like "final", "current" and "v2", a warning light is on.
More than three, simultaneously: The threshold is crossed. Beyond this point, preserving a single source of truth is not something Excel can do. Cloud co-authoring makes it easier to write to the same file together, but it does not reliably restrict who can change which record or which business rule must never be broken. Getting two different answers to the same question is no longer a possibility but a matter of time.
Threshold 2 — Whose head is the knowledge in?
Run this test: if the person who built the file took two weeks off, would the process falter?
If the answer is yes, those formulas are one person’s knowledge, not your company’s. It looks like a backup problem but it is not — a process that cannot be handed over has to be rebuilt from scratch the day that person leaves. This is the least discussed benefit of moving to software: making the process independent of the individual.
Threshold 3 — How long does reporting take?
Minutes: No problem.
A few hours, once a month: On the edge of tolerable.
A full day or more: This is a cost, and you pay it again every month. One day a month is twelve working days a year. Multiply that by the daily cost of the person preparing the report and put it next to a quote for a software module; making the comparison with your own figures is more convincing than any rule of thumb. And that calculation excludes the cost of errors made during manual merging.
Threshold 4 — Can you trace an error backwards?
When you notice a figure is wrong, can you see who changed it and when? If you cannot, your error-finding process is really a guessing process.
This threshold matters most for financial data, inventory and price lists. Auditability is software’s clearest advantage over Excel.
Threshold 5 — Is data leaving your control?
If files containing customer or staff information circulate as email attachments, you have a compliance problem on top of a technical one. A setup where you cannot control who accesses which data is hard to defend under KVKK, Turkey’s personal data protection law.
The reason is written in the law itself. Article 12 of the Personal Data Protection Law No. 6698 requires the data controller to take all necessary technical and organizational measures to provide an appropriate level of security in order to prevent unlawful processing of and unlawful access to personal data and to ensure its protection. Showing those measures is hard for a file whose copies live separately in every inbox and where no one knows who has opened it.
This threshold differs from the others: it is about risk rather than efficiency, and on its own it can justify the move.
Excel’s limit is not capacity, it is control
Excel’s technical capacity exceeds what most companies need; as Microsoft documents, a worksheet holds 1,048,576 rows and 16,384 columns. The problem is that when a spreadsheet is used as the backbone of a business process, errors stay silent.
A well-known example comes from England. According to a BBC report from October 2020, nearly 16,000 coronavirus cases went unreported because Public Health England combined test results from laboratories in templates using the old XLS format. That format was limited to about 65,000 rows, and because each test result took up several rows, a template could in practice hold only about 1,400 cases; once the limit was reached, the rest never made it into the template. The lesson applies to companies too: the spreadsheet raised no error and no warning, it simply came up short. A software system in the same situation would reject the record, log the error and make sure someone knew.
How many did you cross?
Zero or one: Do not migrate now. Stay in Excel and tidy up your file structure.
Two or three: Start planning the move, but do not rush. This is the right time to pick one process and pilot it.
Four or five: Every delay is costing you. At this point the question is not "should we move?" but "which process do we start with?"
| Need | Shared Excel file | Business software |
|---|---|---|
| Single source of truth | Breaks down as copies multiply | One database; everyone sees the same record |
| Permissions | Usually file-level: you see everything or nothing | Role- and record-level |
| Change history | Limited and easily lost | A record of who changed what, and when |
| Rules and validation | Can be bypassed by pasting or a formula error | Enforced at the moment of entry |
| Reporting | Manual merging | Automatic, from the same data |
| Flexible, one-off analysis | Very strong | Limited; this is where data is exported to Excel |
The right order for migrating
Even if you have crossed the thresholds, do not move everything at once. This is the most common and most expensive mistake: the project stretches across months, the team resists, and people go back to their old files.
The right order is this: start with the single most painful process — usually order tracking, quote management or inventory. Let the team do its real work with it for a few weeks and let the rough edges get fixed. Only then move to the second. The real advantage of this method is human rather than technical: once the first module proves its worth, you do not have to convince anyone about the second.
The steps for the first module are clear too:
- Take an inventory. Which files exist, who feeds which, and which pulls data from which? Writing this list down is the fastest way to see how complex the process really is.
- Get the rules out of the file and into writing. The business rules hidden in formulas and colour codes are the software’s requirements list.
- Clean the data. Duplicate customers, product names spelled different ways and empty fields should be fixed before migration; dirty data goes into the new system dirty.
- Run in parallel for a short time. Let the new system and the old file run side by side for a few weeks and compare the results.
- Make the old file read-only. If people keep writing to the old file after the cut-over date, you end up with two sources of truth and the problem starts again.
Whether you solve this module with an off-the-shelf tool or with software built for you is a separate decision; we lay out the framework in our article off-the-shelf or custom software.
Common mistakes
- Copying Excel one-to-one. Moving the existing spreadsheet onto a screen just carries old problems into a new interface. Simplify the process first.
- Leaving out the person who built the file. They know most of the rules; they should be involved from the very start.
- Forgetting the reports. If the team cannot get its monthly report from the new system, it quietly goes back to Excel.
- Treating the move as a technology project. What really changes is how people work every day; a training and support plan is part of the scope.
Excel’s new role
Migrating does not mean removing Excel from the company. It remains one of the most practical tools for flexible analysis and one-off calculations. The only thing that changes is its role: it stops being the company’s memory and becomes an analysis tool that draws data from that memory.
If you are unsure which thresholds you have crossed, let us map your current workflow together. Most of those conversations end not with a vast system to build, but with a single well-chosen module. You can see how we build these modules on our custom software and SaaS development page. If your spreadsheets hold customer data, our data protection checklist is a good place to start as well.
Frequently asked questions
Check five thresholds: more than three people touching the same data at the same time, the process stalling when the one person who knows it goes on leave, reporting taking a full day or longer, being unable to trace who changed what and when, and customer or employee data circulating as email attachments. How many of these you have crossed shows how urgent the move is.
If you have crossed zero or one, stay in Excel for now and improve how your files are organized. At two or three, start planning the move and run a pilot with a single process. At four or five, every delay costs you; the question is no longer whether to move but which process to start with.
No, that is the most common and most expensive mistake: the project drags on, the team resists and people go back to their old files. Start with the single process that hurts most, usually order tracking, quote management or inventory. Move on to the second process only after the team has done its real work with the first for a few weeks and the rough edges are fixed.
Yes, if the files circulate as email attachments and you cannot control who accesses which data. KVKK is Turkey's personal data protection law, and such a setup is hard to defend under it. Because this threshold is about risk rather than efficiency, it can be a reason to move on its own.
No. Excel is still one of the most practical tools for flexible analysis and one-off calculations. Only its role changes: it stops being the company's memory and becomes an analysis tool that pulls data from the software that now holds that memory.
