Guides for specific software problems · Software takeover
Your developer no longer replies? How to get your software back.
It happens more often than you'd think: the freelancer has a new job, the agency has downsized, the only developer has retired. Suddenly software you earn money with depends on a person who can no longer be reached. The good news: it can almost always be rescued — if you do the right things in the right order.
Does this sound familiar?
- Emails and calls to your developer or agency go unanswered.
- You don't know exactly where your website or app is hosted.
- Credentials for the server, domain or code are held only by the provider.
- An urgent change or bug has been waiting for weeks.
- Security updates haven't been applied for a long time.
Why this happens
Knowledge in one head
Many custom systems were built by a single person. Without documentation, all the knowledge sits in that one head.
Accounts held by the provider
Domain, hosting and code often run on the provider's account — convenient at the start, risky when the collaboration ends.
Small clients fall behind
Agencies prioritise big projects. Anyone who only needs occasional maintenance waits — or isn't served at all anymore.
No maintenance contract
Without an ongoing agreement there's no commitment on when someone will respond. Every job starts from zero.
What to do now
-
1
Inventory your accounts
List everything: domain registrar, hosting, server, code repository, database, email, app store accounts, analytics. Note whose name each account is in.
-
2
Request in writing
Request missing credentials and the source code in writing, with a deadline. Check your contract to see what usage rights you have to the code; if in doubt, a lawyer can help.
-
3
Take a backup
As soon as you have access: a full backup of files and database, before anyone changes anything.
-
4
Move accounts to your company
Domain, hosting and repository belong in an account owned by your company. Providers get access, not ownership.
-
5
Hand over to a team, not a person
So the situation doesn't repeat itself, maintenance should sit with a team that has fixed response times.
How we help
We take over existing software — even without documentation and even when the original developer is no longer involved. Since 2008 we've got to know many systems built by others.
- Assessment: what runs where, what's missing, what's urgent?
- Getting to grips with unfamiliar code, whatever the language or framework
- Security updates and urgent fixes first
- Code, repository and accounts in your company's name
- Firm commitments: same-day changes to the live system on a Production plan
Frequently asked questions
Do you also take over software without documentation?
Yes, that's the normal case. We read our way in and document what we find along the way — so you're never dependent on a single person again.
What if I have no access to the code at all?
Then the first step is to get access back. If only the live website is available, we check what can be reconstructed from it. Legal questions are best handled by a lawyer.
Which technologies do you work with?
PHP (TYPO3, WordPress, Laravel, Symfony), Ruby on Rails, JavaScript and more. We're not tied to any language.
How quickly can you respond?
On a Production plan, everything received before 09:00 Japan time is done on the same Japanese business day — for you in the US, usually by the next morning.