Software Development
Software Handover Checklist: What to Secure Before a New Developer Takes Over Your App
Taking over an app someone else built should start with a checklist, not a maintenance quote. Here is what to secure first, starting with the Android signing key that can lock you out of your own app for good.
A software handover checklist secures what your business needs before a new developer takes responsibility for your app: the app signing keys and store accounts, access to every code repository and server, an inventory of passwords and secrets, backups proven by a restore test, and written confirmation that your company owns the code. Get all of it before work starts.
What should a software handover checklist include?
A software handover checklist lists everything your business needs to keep running and changing its software if the outgoing developer stopped answering tomorrow. Most templates online are written for the end of a build. Taking over a live app from someone else is a different job, and the order matters, because most gaps are inconvenient and one can be permanent.
Here is the list we use, highest consequence first:
- App signing. Play App Signing enrolment for Android, who holds the upload keystore, and who holds the Apple distribution certificate.
- Store accounts. Your company stays the Account Holder on App Store Connect and the owner of the Google Play Console. The developer gets a role, not the account.
- Code ownership. Written confirmation of who owns the code and the intellectual property.
- Repositories. Access to every repository, including server configuration and shared libraries.
- Secrets and DNS. Every password, API key and environment variable, plus access to your domain's DNS records.
- Server access. Admin access, and a straight answer to who else holds it.
- Backups. Where they are stored and the date of the last successful restore.
- Knowledge. Time with the outgoing developer, the known defect list and twelve months of incident history.
Keep the answers in one software handover document your business owns. On ownership, South African law does not default in your favour. MJ Kotze Inc notes in its software project handover checklist that without a written IP assignment signed under section 22(3) of the Copyright Act, copyright remains with the developer.
A good developer has most of this ready in an afternoon. One who stalls on item 3 or item 7 is telling you something.
Why Play App Signing and the upload keystore come first
If an Android app is not enrolled in Play App Signing and its upload keystore is lost, nobody can publish an update to that app again. The keystore is a password-protected file that proves an update comes from the app's owner, and Google Play refuses any update without it. With Play App Signing, Google holds the main signing key and a lost upload key can be reset. Without it, the only way out is a new store listing at zero installs, with every existing user stuck on the old version. Google has required it for new apps since 2021, so the danger sits with older apps, the kind that tend to change hands.
Ignoring it costs more every year. According to Google Play's target API level requirements, since 31 August 2026 every new phone app and app update must target Android 16, and existing apps targeting lower than Android 15 stop being available to new users on newer Android phones. An app nobody can update falls behind that rule and loses those new users.
When a South African agricultural business asked us to scope the takeover of a platform another developer had built, with ERP-linked job tracking, a Flutter app on both stores and a self-hosted server, we wrote the keystore into the proposal as a blocking item. No assessment hours and no maintenance commitment until someone confirmed Play App Signing enrolment and who held the upload key. We called it the highest-consequence unknown in the engagement, because discovering it in month two is too late.
How to take over an app from another developer without inheriting surprises
Be careful with a new developer who quotes a fixed monthly maintenance fee before reading the code. They are guessing. The better route is a short assessment with capped hours, spent where the risk turns out to be, ending in a risk register written for the people paying. In that proposal we wrote that we do not quote a maintenance commitment on a codebase we have not read. Then compare what the maintenance retainer in an app development quote covers. Taking over an existing platform is ordinary custom software development work and starts with reading, not pricing.
Book the outgoing developer's time in writing, with an end date: four to eight hours over at least two sessions, after the new team has its own access to the code, so the questions are real ones. On backups, ask whether they sit on a different machine from the server and when someone last restored one. It is the same question as asking where your business records actually live. If nobody on your side can judge the answers, a fractional CTO who owns the handover can run this list for you.
If you own a live app that someone else built, run this checklist now, while the developer still answers your messages. If you are about to switch developers, make the signing keys and the ownership letter conditions of the final payment. Skip it only if your company already holds every account and key, plus a backup someone has actually restored.
Questions about software handover
What should a software handover checklist include?
A software handover checklist should include app signing keys and Play App Signing status, store accounts in your company's name, written code ownership, repository access, a secrets and DNS inventory, server access, backups with a tested restore date, and time with the outgoing developer. Put the signing keys first.
What questions should you ask when taking over a software project?
Ask who holds the Android upload keystore and the Apple certificates, whose name the store accounts are in, who else has server access, where backups live and when one was last restored, and who owns the code in writing. When we scoped a takeover for an agricultural business, those answers, ownership aside, blocked the start of work.
What happens if the Android upload keystore is lost?
If the app is enrolled in Play App Signing, Google can reset the upload key and updates continue. If it is not enrolled and the keystore is lost, nobody can update the app again. The only remedy is a new store listing that starts with zero installs, and existing users stay on the old version.
Who owns the source code of my app in South Africa?
Not automatically you. MJ Kotze Inc's handover checklist notes that without a written IP assignment signed under section 22(3) of the Copyright Act, copyright remains with the developer. Check your contract and get a signed assignment, reviewed by an attorney, before a new developer takes over.
Should my app store accounts be in my company's name or the developer's?
In your company's name. Your business should be the Account Holder on App Store Connect and the owner of the Google Play Console account. Developers get a role such as App Manager or Release Manager. If a developer owns the account, moving the app later depends on their goodwill and their time.
Arnaud Brunel
Founder, Brunel Studios
Arnaud Brunel is the founder of Brunel Studios, a software product studio based in Cape Town. He has spent the last 8 years building digital products for founders and SMEs across South Africa and Africa, working across mobile, web and AI-native platforms.
LinkedIn ↗