Migration 1: Your Charity’s Oldest Database Might Be Its Biggest Risk
You Know the One
Every organisation has one. The database that has been there since before most of the current staff joined. The one that only runs on a specific laptop. The one where everyone knows not to click the wrong button. The one built by someone who retired years ago, leaving nobody quite sure how it works.
It holds your member records. Your client files. Your financial history. Your grant allocations. In some cases, it holds information about vulnerable people – children, patients, or service users – that your organisation has a legal and ethical duty to protect.
And in many cases, it is held together by hope.
What Is a Legacy Database?
A legacy database is any database system that is outdated, unsupported, or no longer maintained by its original developer. In the Irish and UK charity and voluntary sector, the most common ones we encounter are:
Microsoft Access: once the go-to choice for small organisations, now no longer suitable for most real-world needs
FoxPro and Visual FoxPro: Microsoft ended support in 2007 and 2015, respectively
dBase: one of the earliest database systems, still found in some older organisations
Sybase: acquired by SAP in 2010, with many older versions long since left behind
Bespoke systems: custom-built software from the 1990s or early 2000s, often running on Windows 98 or XP, with no documentation and no developer still available to support them
Excel: used as a database: common, fragile, and unsuitable once things become even slightly complex
If any of those sound familiar, you are in the right place.
Why Do Organisations Keep Using Them?
The honest answer is simple: because they still work. Mostly. The data is there. The reports run. Staff know how to use the system. And replacing it feels expensive, disruptive, and risky.
There is also a very human reason. The people who understand the system – which records matter, which reports are needed at year end, which quirks everyone works around – are usually the same people who would need to help replace it. And they are busy. The system works well enough. There is always something more urgent.
So the decision gets pushed back, year after year, until something forces the issue.
What Forces the Issue
In our experience, it is usually one of four things:
– The system crashes or becomes inaccessible, and the organisation realises it has no recovery plan
– A GDPR audit flags the database as non-compliant: data stored in plain text, retention periods ignored, no way to process Subject Access Requests
– A funding body asks for evidence of good governance and data protection, and the organisation cannot provide it
– The hardware it runs on finally fails: the laptop, the server, or the operating system everything depended on
Any one of these can happen without warning. The organisations that cope best are the ones that act before they are forced to.
The Risk Is Not Theoretical
We have worked with Irish organisations running critical systems on Windows 98 virtual machines because that was the only way to keep the old database accessible across a network. We have seen member records going back 20 years stored in plain text with no encryption. We have seen systems where the original developer had passed away, leaving the organisation with no documentation, no source code, and no way to change even a simple report.
These are not horror stories from decades ago. These are situations we have seen in recent years in organisations that are otherwise well-run and professional.
The database had simply fallen through the cracks.
The Good News
Every one of those situations was fixable. The data was recoverable. The organisation moved forward. And in each case, the process, while it took time, was far less disruptive than people had feared.
That is what this series is about. Not scaring you into action, but giving you a clear picture of the risks, the options, and what modernising a legacy system actually looks like in practice.
In Part 2, we talk about cost honestly, with real figures, so you know what to expect before you pick up the phone.
Ready to Have a Conversation?
If you have read this series and recognised your organisation in it, the next step is simple. Get in touch. We will have a chat, ask a few questions, and give you an honest view of what is involved. No charge. No obligation.
Back to: Legacy Database Migration Series
