Old software that still works is easy to keep. But risk builds quietly until a failure, a compliance deadline or a departing developer forces a rushed decision. Watch for these signs.
The warning signs
- Only one person or a defunct vendor can support it
- It runs on unsupported operating systems or databases
- It can't meet new compliance needs such as ZATCA e-invoicing
- It can't integrate with POS, e-commerce or banks
- Staff keep side spreadsheets to work around it
- Reports need manual exports and fixes
- Adding a branch or company is difficult
- Security patches are no longer available
- Performance slows as data grows
Three or more? Start planning
You don't need to replace everything at once. Start with an assessment: document what the system does, including hidden business rules, and how much data must move.
Your options
- Keep and wrap: add APIs or middleware around it
- Re-platform: move the same application to supported technology
- Replace: move to a packaged ERP or new application
- Retire: archive data and switch off parts no longer needed
Plan a safe cut-over
Run trial data migrations, test with real scenarios, and consider a short parallel run for critical processes. Keep read-only access to old data for reference.
Key takeaway
Decide before you're forced to. A planned replacement costs less and disrupts less than an emergency one.
