Help for owners
Old databases and tools still hold customer data and nobody has deleted it
Short answer
Old systems rarely hold only old data. Retired apps, test copies, exports and forgotten servers often still contain real customer records and are looked after by nobody. Find them first, decide which data you must keep, copy what you need, then switch off and delete in stages. Deleting before you know what depends on it is the risk.
Does this sound like your situation?
- I replaced my old website or app and I am not sure the old server was switched off.
- A former developer or agency may still have copies of the database.
- Spreadsheets of customer details sit in email and shared drives.
- There are test or staging copies built from real data.
- A customer asked me to delete their data and I could not say where all of it is.
Why does this happen?
Switching on is a project, switching off is not
Moving to a new system has a budget and a deadline. Retiring the old one has neither, so servers, databases and accounts keep running quietly.
Copies multiply
Exports for a report, a staging copy for testing, a backup before a migration and a download by an agency all become separate copies of the same customer records.
Nobody owns the old thing
The person who knew what was on the old server has often left. Paying for the hosting is automatic, so nobody looks at it.
Unmonitored systems get attacked first
An old site or database that nobody updates is exactly the kind of system an attacker looks for, and the data on it is as real as the day it was collected.
What can I do about it today?
- Make a list of every place customer data might beCurrent and former websites, apps, servers, databases, spreadsheets, email attachments, accounting and marketing tools and agency copies. Ask each person who has worked on them.
- Check what you are still paying forLook through hosting, domain and cloud invoices for services nobody uses. They often point to forgotten systems.
- Do not delete anything yetFirst decide what you must keep, for how long and why. Whether you must keep or must delete records is a legal and accounting question for your adviser, not for me.
- Restrict access to what you findRemove old logins and shared links, and ask former suppliers in writing to confirm what they hold.
- Take a copy of what you need, then retire in stagesSave what the business needs, switch the old system off, wait a while to see whether anything breaks, and only then delete.
- Write down the resultA one-page register of where customer data lives, who owns each place and when it should be reviewed.
When should I bring someone in?
- A customer has asked for their data to be deleted and you cannot find all of it.
- An old system was hacked or exposed.
- You do not know whether an old server still has live connections to your current app.
How do I handle it?
- Find the data before judging itI look for databases, storage, backups and servers across your hosting and cloud accounts and the code that talks to them.
- Check what still depends on each systemBefore anything is switched off, I check what connects to it, so retiring it does not break something current.
- Keep a verified copy of what you needA tested archive is made for what you choose to retain, separate from the live systems.
- Retire in steps with a way backAccess is closed, the system is stopped and watched, and deletion is the last step, confirmed with you in writing.
- Leave a registerA simple list of where data lives, so the next clean-up is smaller.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
How long should I keep customer data?
That depends on your country, your industry and the kind of data. It is a question for a lawyer or accountant, and I will not give a number.
Can I just delete the old server?
Not first. Check what depends on it and keep a copy of what you must retain. Then retire it in steps.
Are backups part of this?
Yes. Backups can hold old customer data too, so a deletion plan has to say what happens to them.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.