Spreadsheets are where many businesses begin. A workbook can track orders, stock, budgets or rotas with no software purchase and no training. Over time, though, the file grows, more people depend on it and the rules inside it become harder to see. Deciding to replace spreadsheets with ERP is rarely a dramatic moment. It usually follows a run of small problems that finally add up.
This article looks at the signs that a spreadsheet has quietly become a system, the risks that come with that, and how to decide what should move first. It also covers the people side of the change, which is where many moves succeed or stall. The mechanics of moving records are a subject of their own, so this piece stays with the decision and with adoption.
If a spreadsheet is starting to cause real problems in your business, the aim is to move in a controlled way, with as few surprises as possible for the team.
When a spreadsheet has become a system
A spreadsheet crosses a line when it stops being a personal tool and starts holding the live record for a process. The signs are usually practical rather than technical.
Recognising the warning signs
Look for everyday symptoms. The file name ends in words like final, final version or latest, and it still changes. Several people keep their own copies. Totals on one tab do not match another. Someone spends the first hour of each Monday checking whether they have the real version.
Each symptom is manageable on its own. Together they mean the business is running on an informal system without the controls of a proper one.
Why spreadsheets feel safe
Spreadsheets are easy to start, flexible and familiar. Excel can be adapted to many needs quickly, which is exactly why it spreads so easily through an organisation. The same flexibility makes it easy to break. Formulas get overwritten, rows are inserted in the wrong place and nobody is alerted when a rule stops working.
The risks of letting spreadsheets run the business
The risks are easy to dismiss because nothing has gone visibly wrong yet. They tend to surface only when something important breaks.
Key person risk
When one person understands how a workbook really works, the business depends on that person being available, accurate and willing to keep it going. Holidays, sickness or a departure can leave the team with numbers nobody can explain. Formulas built for a past process can stay in use long after the process has changed.
Version control and access
A spreadsheet does not record who changed what unless someone has set that up deliberately, and many workbooks are not set up that way. Two people can edit different copies on the same day, and whichever file is saved last quietly wins. Restricting access to particular rows or figures is awkward, so sensitive pricing or payroll details often sit where everyone can see them. The most common results include:
- Orders or stock levels that differ between two copies of the same file
- Price changes made on one tab but never carried through to the others
- Reports that cannot be reproduced because the inputs were overwritten
- Confidential figures visible to people who should not see them
Reporting that depends on rework
When management reports are built by copying data from several files each week, the business pays in time and in confidence. Each manual step is a chance for an error, and the people closest to the work spend hours assembling figures rather than acting on them.
What spreadsheets do well, and what they should not hold
The aim is not to abandon spreadsheets. They are excellent at certain jobs, and it is worth keeping those jobs in them.
Keep the analysis in spreadsheets
Forecasting, what-if modelling, one-off analysis and budget planning often suit a spreadsheet well. They let people test assumptions quickly and share a view with colleagues. None of those jobs needs to become a system of record.
Move the record into a system
The live record should be the place where orders, stock movements, customer details, purchases and approvals are held. An ERP is designed to keep those records consistent, linked to one another and visible to the people who need them, with an audit trail that a workbook cannot easily provide. A simple test helps decide which side of the line something sits on:
- If many people need to change it, it belongs in the system
- If it has to be right for a customer, a supplier or a tax return, it belongs in the system
- If it is an exploration or a draft, it can stay in a spreadsheet
- If only one person ever looks at it, it may not need to be a shared process at all
Replacing spreadsheets with ERP starts with the right first move
Trying to move everything at once is the quickest route to a stalled project. The first phase should target the records that cause the most rework or carry the most risk.
Start where the rework is
Look for the workbook that gets updated most often, is copied into other files or is used to make decisions with money attached. Stock levels, open customer orders and purchase approvals are common examples. A well-run first move on one of these brings visible relief and builds confidence for the next phase.
Leave history and rarely used files for later
Old workbooks, one-off analyses and archived lists can wait. They may still be needed for reference, so keep them accessible, but do not make them part of the first phase. A smaller first move is easier to finish, easier to test and easier for the team to understand.
Agree the order before the software arrives
Write down the order in which processes will move, the reason for each choice and the signal that the next phase can begin. The managers who own each process should agree that order, rather than the project team guessing it on their behalf. A written order gives the team something to hold the project to when requests start to arrive.
Change management starts before the software
Most of the difficulty in moving off spreadsheets is human. People have built routines around the workbook, and it makes sense to them even when it makes little sense to anyone else.
Explain the reason in terms people feel
Explain what problem the change solves for the people who live with it. A buyer may care about not chasing approvals, a warehouse lead about knowing what is on the shelf and a finance team about closing the month without weekend work. Broad talk about modernising the business does not help anyone.
Involve the people who use the sheets today
Ask the people who maintain each spreadsheet to walk the team through what it does, including the informal steps and the exceptions they handle by hand. Their knowledge is the real specification for the new process. People who helped shape the design are far more likely to use the result. Give them a visible role, such as super-user or process champion, with time set aside for it.
Train on real tasks, not on menus
Training works best when it follows the tasks people perform each day, such as raising a purchase order or recording a stock count, rather than walking through every screen. Give each role a short guide with the steps it will use, and provide a safe place to practise before go-live. Keep one named person available to answer questions during the first few weeks, so small confusions do not turn into workarounds.
Running the change without two sources of truth
The riskiest period in any move is when both the spreadsheet and the system seem to be valid. A few firm rules prevent that confusion.
Choose the cut-over date and hold to it
Pick a date after which new work is recorded only in the system. Tell everyone the date and make it part of the team's routine. Postponing the decision repeatedly keeps the old habit alive and doubles the effort for everyone. Announce the date early enough that people can prepare, and then keep to it unless there is a serious reason to change.
Limit any parallel running
Some businesses find it helpful to run old and new processes side by side for a short time, to build confidence. Keep that period brief and agree which system wins for each record. Parallel running that drags on creates duplicate entry and arguments about which number is correct. If you do run in parallel, make the new system the only place where corrections are made, even during the overlap.
Lock the old file and show people where it went
Once the cut-over date passes, lock the spreadsheet, rename it so it is clearly an archive and store a copy somewhere the team knows to look. That keeps the history available without inviting anyone to update it by mistake. A short note in the team's usual channel, stating where the archive lives and who to ask for it, prevents months of quiet confusion.
Measuring whether replacing spreadsheets with ERP has worked
A move is not finished when the software is switched on. It is finished when the team relies on the system and the old workarounds have stopped.
Look for signs of adoption
Watch for practical signals rather than enthusiasm in meetings. Are orders and approvals being raised in the system? Are managers pulling reports from it rather than asking for a spreadsheet? Are people still emailing copies of old files around? Each answer tells you how the change is landing.
Fix the process, not just the screens
If the team has rebuilt the spreadsheet inside the system, with the same workarounds and manual checks, the business has moved the problem rather than solving it. Review the process after the first few weeks and remove any step that exists only because the old tool needed it. The aim is a process that the new system can support, not a digital copy of the old workbook.
FAQ
Why do businesses move from spreadsheets to ERP?
Usually because the spreadsheets no longer match the pace or complexity of the business. Common triggers include growth, more people needing the same information and reports that take too long to produce. An ERP gives the business shared records, controlled access and an audit trail.
Is it a mistake to keep using Excel for business records?
Excel is a useful tool for analysis, forecasts and one-off models. It becomes a risk when it holds the live record for orders, stock or customers and only one or two people understand how it works. Keep the analysis in Excel and move the record into a system designed to hold it.
What should we move to ERP first?
Start with the records that cause the most rework or carry the most risk, such as stock levels, customer orders or purchase approvals. Leave long history and rarely used files until the new process is working. Keep the first phase small enough to finish well.
How do we get staff to stop using the spreadsheets?
Involve the people who use the sheets today, so they can explain what each one does and which exceptions it handles. Remove the sheet from the process rather than asking people to keep both, and give role-based training on the tasks they actually perform. Name one person to answer questions during the first few weeks.
What should happen to the old spreadsheets?
Lock them in read-only form after the cut-over date, rename them clearly as archives and store them where the team knows to look. Agree with finance and operations how long they are kept. Make sure nobody is still updating them, because two live versions soon cause confusion.
Can we run ERP and spreadsheets side by side?
Only for a short, defined period, and only with one agreed source of truth for each record. Running both for long periods leads to duplicate entry and arguments about which figure is correct. Decide which system wins for each record before the parallel period begins.
Final thought
Replacing spreadsheets with ERP is less about software and more about making the business's records reliable enough to trust. Spreadsheets have carried many businesses a long way, and they still have a useful role. The aim is to stop asking them to hold the live record, so people can spend their time on decisions rather than keeping files in step.
Start with the workbook that causes the most rework, agree the order of moves with the managers who own each process and prepare the team before the new system arrives. A calm, staged move is usually easier to live with than a single switch-over.
If spreadsheets have started to slow the business down, Mirex Agency can help you judge where the first phase should sit. The agency is based in London and works with UK small and mid-sized businesses through its ERP solutions service, which covers finance, stock, HR and operations in one clearer system. Reach the team at hello@mirexagency.com to talk it through.
