Replacing old business software without losing what works

Most businesses don’t choose to run on old software. It happens gradually. A system is built or bought, it works, and years go by. Then one day someone realises the company depends on a program nobody can update, on a PC nobody dares switch off.

You don’t need to know what your system is written in to recognise the signs.

Signs it’s time to act

• One person holds the knowledge. If they left or were ill for a month, would the business cope?
• It only runs on one computer. Or one old server, or only with a particular version of Windows.
• The supplier has gone. Or they still answer the phone but can’t make changes anymore.
• Data gets re-keyed. Orders, invoices or customer details are typed into the old system and then again into something else.
• Month end involves exporting to Excel and fixing things by hand.
• Nobody can work from home or on the road without awkward workarounds.
• An insurer, auditor or customer has asked questions about security, backups or access controls that you couldn’t comfortably answer.

One or two of these is normal. Four or five means the risk is quietly building.

Your choices

There are really only four:

Keep it, but make it safe. Document it, back it up properly, make sure it can be rebuilt on a new PC, and line up support. Cheap, sensible, and often the right first step.

Replace it with a packaged system. If what it does is fairly standard, such as accounts, stock, orders or CRM, a modern platform like Odoo can usually cover most of it, with your history migrated across and the gaps built as add-ons.

Rebuild it. If your system does something genuinely specific to how your business works, a modern web application built around that process may be the best answer. Done a module at a time, it doesn’t need to be a big-bang risk.

Connect it. Sometimes the old system can stay a little longer if it’s linked properly to your other software, so data stops being typed twice.

How to replace it without disruption

The businesses that get this right tend to do the same things:

1. Understand the old system first. Not just the screens, but the rules, the calculations and the workarounds nobody wrote down. This is where most replacements go wrong.
2. Rescue the data early. Get a clean, complete copy of your data out before anything else, so you’re never dependent on the old system to see your own history.
3. Move in stages. Replace one area at a time, and run old and new side by side until people trust the new one.
4. Fix the price before starting. Once the old system has been properly understood, a fixed price is possible, which protects you from the surprises old systems are full of.

Where to start

If you’re not sure what you’ve got or what it would take to move on, a Health Check is the quickest way to find out. If your system is built in FoxPro, our guide to Visual FoxPro end of life covers the options in more detail.