Legacy System Recovery Checklist for Singapore SMEs
Recovery starts with ownership and operational evidence, not a rewrite. Use this checklist to establish what the system does, who depends on it, and whether it can be changed safely.
Questions to answer first
- Who owns the source code, hosting account, domain, database, and deployment credentials?
- Which daily operations stop if the system is unavailable for one hour or one day?
- When was the last successful restore from backup, rather than the last backup job?
- Which integrations, scheduled tasks, shared folders, and manual workarounds depend on it?
- What is the smallest safe change that would reduce the most immediate risk?
A practical review sequence
Map the operating dependency
Name the users, workflows, deadlines, upstream inputs, downstream outputs, and the acceptable recovery time.
Recover technical ownership
Locate source code, production access, deployment instructions, database credentials, licences, domains, certificates, and vendor contacts.
Prove recoverability
Confirm backups include the right files and data, then test a restore in an isolated environment and document the result.
Create a safe change path
Establish a repeatable build, a non-production test environment, rollback steps, and named approval before making fixes.
Separate stabilisation from modernisation
Handle urgent availability, access, and data risks first. Evaluate replacement options only after the current system is understood.
Red flags
- Only one person knows how to restart or deploy the system
- Backups exist but no restore has been tested
- Production is the only test environment
- Source code differs from the running application
- A vendor account controls essential infrastructure without documented handover
Useful output
A short recovery pack: system map, ownership register, tested-backup result, immediate risk list, and a phased next-step recommendation.
Explore Legacy System Rescue & Modernisation