When the person who built your system leaves, everyday work may continue while uncertainty grows behind the scenes. Who can restore it, renew a service or investigate the next fault? The first task is establishing what the business controls and what knowledge needs to be recovered.
Recover access before changing the system
Build an inventory of source code, hosting, database, domains, licences and third-party accounts. Arrange access through authorised business administrators. Check contractual rights to the code and documentation before transferring them to a new supplier. Preserve a working copy before attempting repairs.
Practical checks
- Identify business-owned accounts and their administrators.
- Locate the latest source code and release instructions.
- Record scheduled jobs, integrations and renewal dates.
- List unresolved faults and critical business workflows.
Questions and answers
Should we share the former developer’s personal login?
Use authorised account recovery or administrator-managed invitations instead. Give the new supplier appropriate access without relying on somebody else’s personal credentials.
Can a new developer understand undocumented software?
Often, but investigation takes time. A technical review and demonstrations from experienced staff help reveal how the system works and where the main risks lie.
Discuss your existing software
Digital Solutions can review the available system and discuss an appropriate next step. Feasibility, access requirements and the scope of any chargeable investigation are agreed before work proceeds.
Explore our software support, project rescue and modernisation services.
Book a free 15-minute software review or contact Digital Solutions.