Almost every established UAE business has one: a system built years ago by a developer who has moved on, running on a server nobody wants to touch. It holds the customer history, the pricing rules and the way the company actually works. It also cannot talk to the website, breaks when the browser updates, and takes a week to change a report. Replacing it feels risky; leaving it feels worse. This guide helps you choose between five approaches.
Signs that the system needs attention
- Only one person understands it, or nobody does.
- It runs on unsupported software, such as an old server operating system, an outdated PHP or database version, or a desktop-only tool.
- Security fixes are not applied, or you are afraid to apply them.
- Simple changes take weeks, and each change breaks something else.
- It cannot integrate with payment, WhatsApp, banking or e-commerce services.
- It does not handle current requirements: VAT details, Arabic documents, multi-branch, mobile access.
- Staff run key work in spreadsheets around it.
The five options
| Option | What it means | Best when | Main risk |
|---|---|---|---|
| 1. Keep and stabilise | Back it up, document it, patch the platform and fix known bugs | System is sound but neglected | Problems return; you stay dependent on old technology |
| 2. Wrap with an API | Leave the core alone and add a modern interface or integration layer around it | Core logic is good; you need web, mobile or integrations | The old core still limits you |
| 3. Refactor in stages | Replace the system part by part, keeping it running throughout | Large, valuable system with clear modules | Needs discipline and a long-term owner |
| 4. Replatform | Move the same system to a new server, database or framework version with limited change | Code is fine but the platform is end-of-life | Hidden dependencies surface during the move |
| 5. Rewrite or replace | Build or buy a new system and migrate the data | The old design cannot support the business | Cost, delay and loss of hidden business rules |
How to decide
- Value: how important is this system to revenue and operations? A rarely used internal tool does not justify a rewrite.
- Health: can the code be read, tested and changed safely? Ask a developer for a short technical review and a written summary.
- Fit: how closely does it match how you work today? A system you must work around is a candidate for replacement.
- Risk: what happens if it fails for a day? A week?
- Cost of waiting: add up the time lost to workarounds and the exposure from missing security fixes.
A common result: wrap the system for quick gains, then refactor the modules that hurt most, and replace the rest later.
Capture the business rules before anything changes
The most valuable thing in a legacy system is not the code; it is the rules in it: customer-specific pricing, discount limits, approval chains, special cases built over years. Before touching anything, document them with the people who use the system daily. Rewrites fail most often because rules nobody remembered are lost.
Plan the data
- Inventory every table and file, and decide what moves, what is archived and what is deleted.
- Clean duplicates and fix formats before migration. See ERP data migration.
- Keep the old data readable for audits for as long as the law and your policy require.
Avoid the big-bang switch
- Start with a small, visible module such as quotations or customer lookup.
- Run old and new in parallel for a defined period.
- Move users group by group, with a quick way back.
- Retire pieces of the old system as the new ones prove themselves.
UAE considerations
- Old billing modules may not meet current tax invoice requirements. Check them first. See tax invoice requirements.
- Arabic text support, multi-currency and multi-entity structures are often missing and are expensive to retrofit.
- Hosting and data location should be reviewed during the move. See cloud hosting and data residency.
We assess, wrap, refactor and rebuild business systems for UAE companies. Read about our software modernization service and the engagement models we offer, or send us a short description of your current system.