What to take away
Replace workflows, not every spreadsheet
Look for concurrency and control risk
Stabilise definitions before migration
Keep analysis flexible after operations become structured
The warning signs
A spreadsheet is becoming operational infrastructure when multiple people edit it, downstream work depends on its current state, changes need approval or the business cannot reconstruct who changed what.
- Conflicting copies and manual consolidation
- Broken formulas affect decisions
- Access is broader than responsibility
- One person understands the logic
- The same data is re-entered elsewhere
- Reporting requires repeated cleanup
What ERP should change
The goal is not to copy every column into a database. Define the events, decisions, roles and outputs the spreadsheet was informally coordinating.
A good system structures routine operations while preserving export and analysis options for questions that remain exploratory.
A safe migration path
Choose one painful workflow, clean its definitions, migrate the minimum dependable data and run the new process alongside the old one long enough to reconcile outcomes.
Retire the old operational file deliberately. Leaving both editable creates a new source-of-truth problem.
Common questions
Do we need ERP if spreadsheets still work?+
Not necessarily. Change becomes worthwhile when collaboration, control, scale or reporting risk creates more cost than the flexibility spreadsheets provide.
Can users still export data to Excel?+
Yes. Controlled exports can support analysis without turning spreadsheets back into the system of record.