When should you replace Excel with a program? Moving from Excel to custom software
The time to move from Excel to custom software is when a spreadsheet stops being a calculation tool and becomes the system that runs the work: several people edit the same file, errors are hard to find, nobody knows who changed what, and the file is fed by hand from other systems. For a simple sheet used by one person, no move is needed. Excel is the right tool there.
People who search for "excel yerine program" or "excel yerine hangi program" (a program to replace Excel) are usually not looking for software. They are looking for a way out of a problem: versions get mixed up, a formula breaks silently, or an employee goes on leave and nobody understands the file. So first look at where Excel is enough, and then at where it is not.
Excel's technical limits are often further away than people think. According to Microsoft's Excel specifications and limits page, a worksheet can hold up to 1,048,576 rows and 16,384 columns. So the problem is rarely the row count. It is the arrangement around the file: permissions, audit trail, validation and integration. Excel stores numbers well, but it does not manage a process.
Excel also stores numbers as floating-point values following the IEEE 754 standard. Microsoft's floating-point documentation states plainly that this can cause rounding differences in some results. For stock or customer-account tracking that needs exact amounts, this is a sign that the sheet needs a control mechanism beside it.
Is Excel enough, or do you need custom software? A warning-sign table
Compare the table below with your own file. If three or more signs in the last column sound familiar, it is time to plan the move.
| Sign | Excel is enough if | Points to a move if |
|---|---|---|
| Users | One or two people | 3+ people at once, copies circulating |
| Versions | One current file exists | "final_final_v3.xlsx" files multiply |
| Errors | Formulas are simple and checkable | Errors surface months later |
| Permissions | Everyone may see everything | Visibility must differ by person |
| Audit trail | Who changed it does not matter | Who changed what, and when, gets asked |
| Integration | Data is typed in | Manual transfer to accounting, shop or CRM |
| Process | It only keeps records | Approvals, reminders and alerts are needed |
What happens when several people use the same Excel file?
Working together in Excel is possible. Microsoft describes it as co-authoring and says changes can appear within seconds. The same page lists conditions, such as being signed in to Microsoft 365 and using a version of Excel that supports co-authoring. If one colleague opens the file in an older version, the arrangement can break down.
Co-authoring solves simultaneous editing, but not permissions, validation or process. Anyone can change any cell, an invalid amount can be entered, and whether a row is approved is shown only by a colour. At this point the choice is not to strengthen Excel but to move the data into a system.
If you hold personal data, there is also a legal side. Article 12 of Law No. 6698 (KVKK) requires the data controller to take the necessary technical and administrative measures to prevent unlawful access to personal data. A customer list that travels by email, without a password and open to anyone, is an example that could be questioned when those measures are assessed. For your own situation, ask your data protection adviser or lawyer.
What comes after Excel: off-the-shelf software, low-code or custom software?
Custom software is not the only option, and often it should not be the first. You can separate the three routes like this.
- Off-the-shelf software (SaaS): Suited to standard processes such as accounting, stock and CRM. You start quickly, but you bend your process to the product.
- Low-code or no-code tools: Suited to simple forms, approval flows and internal reports. Limits appear as permissions get complex, user numbers grow and integrations multiply.
- Custom software: Consider it when your process sets you apart from competitors, must talk to several systems, and off-the-shelf products do not fit. It takes more effort, but it is shaped around you.
The decision rule is simple: if your process looks like everyone else's in your sector, buy a ready product. If your process makes you different and you keep patching around it in Excel, consider custom software. The logic in our buy or build article also applies to software decisions beyond AI.
How do you move from Excel to custom software? Step by step
- Take inventory of the file. Which sheets exist, which are really used, which cells are typed by hand and which are calculated? Do this through the eyes of several people, not one employee.
- Map the process. Who enters the data, who approves it, where does it go? The steps Excel solves silently (for example, someone phones to ask and corrects it) are often written down nowhere.
- Clean the data. If one customer is recorded in three spellings, dates are stored as text or blank cells carry meaning, fix these before the move. Bad data travels to the new system too.
- Start with one small part. Move the single process that causes the most trouble, not the whole file. The rest can stay in Excel.
- Run in parallel. Let the new system and Excel run side by side for a few weeks and compare results. If they differ, decide together which is right.
- Retire the old file. Make the Excel file read-only. Otherwise you end up with two "correct" records.
For the logic of phased migration in large, risky systems, see our application modernisation decision guide; the same principle applies to spreadsheets.
Example: a business that tracks orders in Excel
For example, imagine a 12-person wholesale business that keeps orders in a single Excel file and enters 80 orders a day. The sales team enters the order, the warehouse marks it "prepared", and accounting issues the invoice. On average three times a week, two people edit the same row at once and one overwrites the other's entry.
If only 4 errors a month occur and each takes half an hour to find, 2 hours a month go on hunting for errors alone. These figures are hypothetical; replace them with your own measurements. The real cost is the errors that are never found: a wrong shipment, a double invoice, a lost order.
A possible route for this business is a small web application that manages orders, their statuses and permissions. Sales only enters orders, the warehouse only changes status, accounting only sees what is ready to invoice. The old file is imported, run in parallel for a few weeks and then made read-only. Exporting to Excel can still be offered for management reports, but the data now lives in one place.
How do you know the move worked?
Before the move, define a few measures you can compare afterwards. Without them, all you get is "it feels better".
- Error count: Count wrong records, double invoices or wrong shipments per month for three months before the move, then track the same number in the new system.
- Search time: Measure how many minutes it takes on average to find a record or trace an error to its source.
- Manual transfer: How many times a week is data copied by hand from one file to another system? The aim is to bring this close to zero.
- User feedback: At the end of the first month, ask everyone who uses the system "which job is harder than before?" and feed the answers into the next release.
- Permission test: Sign in as one user from each role and confirm they cannot see data they should not.
Common mistakes when moving from Excel to software
- Asking for an exact copy of Excel: If the new system imitates the sheet, the same problems come along. Simplifying the process is the real gain.
- Moving data without cleaning it: Duplicate records and dates stored as text pollute the new system from day one.
- Moving everything at once: One big cut-over raises risk. Going process by process is safer.
- Leaving users out: The person who uses Excel every day is the first to notice what the system misses.
- Leaving permissions and backup to the end: Who sees what, and how data is backed up, should be designed from the start.
- Leaving the old file open: If both systems are updated, nobody knows which is right.
How Hatson Tech helps
Hatson Tech starts by understanding the process behind the spreadsheet: we review the file together and discuss which parts need custom software and which a ready product. The first meeting and discovery are free. Hatson does not publish fixed prices; a proposal is prepared once the scope is clear. For our development approach, see our custom software development page. We cover phased migration in the application modernisation decision guide and the choice between a ready product and building in the buy or build article.