When to move from Excel to custom software: signs and steps

You should move from Excel to custom software when a spreadsheet stops being a calculation tool and becomes the shared system your team runs on. The signs are familiar: several versions of the same file in circulation, two people unable to work at once, nobody sure who changed what, reports assembled by hand every month. The move does not happen in one go. You map the process and the data first, take the part that carries the most weight into software, and run both side by side for a short while.

Excel is a strong tool, and it has a place in most businesses. This piece does not argue for abandoning it. It explains the point at which a spreadsheet stops carrying the load, how to plan the move and how to bring your data across without losing any of it.

Where is Excel enough, and where does it fall short?

Excel is enough for work that one person does, with simple rules and no need for history. It struggles once several people write to the same data, once it matters who can see what, and once it needs to connect to other systems.

Situation	Excel is usually enough	Consider custom software
Users	One or two people	Many people in different roles
Change history	Not important	You need to know who changed what, and when
Permissions	Everyone may see everything	Each person should see only their own work
Rules	A few formulas	Approval steps, statuses, reminders
Connections	Copying by hand is fine	Automatic transfer to accounts, shop or CRM
Reporting	Monthly, by hand	Live, and different for each role

The technical ceiling is rarely the deciding factor. According to Microsoft’s Excel specifications and limits, a worksheet holds 1,048,576 rows. Few businesses ever reach that limit. Where they struggle is in giving several people a safe, traceable way to work in the same file.

Eight signs your spreadsheet has outgrown its job

If three or more of these sound familiar, the spreadsheet is struggling to carry the load. We suggest taking the same list to a first conversation with any software team.

Version chaos. Files named “final”, “final_latest” and “final_latest_Sarah”, and only one person knows which is right.
Clashing edits. When two people edit at once, one overwrites the other, or someone waits for the file to be free.
Broken formulas. A deleted row or a shifted column quietly produces wrong totals, noticed weeks later.
No history. Nobody can say why a figure changed, or who changed it.
No permissions. The person who needs the price list can also see salaries or customer contact details.
Hand-built reports. Every month several files are merged and pivot tables rebuilt.
Hand-copied data. The same information is retyped into the accounts, the shop back office or the CRM.
One-person dependency. When the person who understands the file is on holiday, work slows down.

The fifth sign has a legal side too. Spreadsheets of personal data travelling by email and sitting in shared folders are a risk under data protection law — GDPR in the UK and EU, KVKK in Türkiye. Permissions and an access log are among the most tangible gains of moving to proper software.

Is custom software the only way out of Excel?

There are three ways out, and what the spreadsheet does decides which one is right. If it does a standard job — bookkeeping, stock, customer tracking — look first at an off-the-shelf product built for that job. If the work is specific to you, or you keep bending an off-the-shelf product to fit, custom software comes into the picture. Sometimes the spreadsheet stays and only the hand-copying is automated.

Route	When it fits	What to watch
Off-the-shelf software	The spreadsheet does a job that many businesses do the same way	You adapt to the product’s workflow
Custom software	The process is yours, with many roles and rules	It needs a build and ongoing maintenance
Spreadsheet plus automation	The spreadsheet works; the problem is copying by hand	The sheet must still be run as the single source of truth

We set out six questions for that decision in off-the-shelf or custom software?. If the spreadsheet is really a customer list, CRM: off-the-shelf or custom? is more directly useful. If the only trouble is copying by hand, the first steps in automation for small businesses may be all you need.

How do you plan the move?

The move starts with working out what the spreadsheet does today and ends with the old file going into the archive. There are eight steps in between:

File inventory. Which spreadsheets exist, who uses them, how often are they updated? What looks like one “master sheet” is often five linked files.
Process map. Where is a record born, whose hands does it pass through, where does it end? Who decides at each step?
Data dictionary. What does each column mean, which values can it take, is it required? Do “done”, “Completed” and “OK” in the status column mean the same thing?
Writing down the hidden rules. Rules buried in formulas, colour-coding and habits of the “Michael does this every month” kind are listed. This is the real knowledge that moves into the software.
Choosing the first module. The part that wastes the most time or causes the most errors goes into the first version. Trying to move everything at once is the most common reason migrations fail.
Cleaning the data. Duplicates are merged, spelling variants fixed, missing fields completed or flagged.
Parallel running. For a short period both systems run. The new system’s results are compared with the spreadsheet’s.
Archive. The spreadsheet is made read-only and archived. New records are created only in the new system.

Keeping the first module small cuts both time and risk. We describe the same thinking in product terms in building a SaaS product from an MVP, and what drives timelines in how long does a software project take?.

How is the data moved and checked?

Once cleaned, the data is moved with a migration script and checked three separate ways. The transfer itself is usually quick. The real work is making sure what arrived is complete and correct.

The three counts we recommend after a migration:

Record count. Does the number of rows in the spreadsheet match the number of records in the new system? If not, can every difference be explained — merged duplicates, old records deliberately left behind?
Totals. Do the sums of numerical columns — amounts, quantities, balances — match on both sides?
Sample check. Are randomly chosen records compared field by field by the person who knows the spreadsheet best?

A migration that fails any of these does not go live. Nor is the script thrown away after one run: records added to the spreadsheet during parallel running must be transferable with the same script.

How do you bring the team with you?

A team adopts a new system when they see it makes their own work easier, so the first module should fix the job people complain about most. A few practical points:

Involve the person who knows the spreadsheet best in the process map and the checks. The hidden rules they carry are the key to building the system correctly.
Set an end date for parallel running at the outset. Open-ended parallel running means doing everything twice.
Leave an export option in the new system. The team may want to keep doing their own analysis in a spreadsheet for a while; that is fine, as long as the new system is the single source of truth.
Gather feedback in the first weeks and make the small fixes quickly.

Frequently asked questions

Will we lose data when we move from Excel to custom software?

Not with a planned migration. Data is cleaned, moved and then checked by record count, numerical totals and sample records. The old spreadsheet is not deleted either; it stays in the archive as read-only.

Do we have to give up Excel completely?

No. Once the new system is the single source of truth, the team can keep using Excel for analysis and one-off calculations. That is why exporting from the system to a spreadsheet is usually planned in from the start.

How long does the move take?

It depends on the size of the process being moved, the number of roles and rules, the systems to connect and how clean the data is. Keeping the first module small is the safest way to see an early gain. A firm timeline comes with a written proposal once the scope is clear.

Our Excel files are linked and complicated — can they still be moved?

Yes. Linked files and nested formulas are where hidden rules hide most. Untangling those links is exactly the first step of the move, and it often gives everyone a clearer picture of the work itself.

If you would like to look together at which part of your spreadsheets should move first, see our custom software and SaaS page, or write to us with a short description of how you work today. If we think the spreadsheet is enough, we will say so.