App takeover and developer handover checklist
This checklist scores how ready you are to take over an app from a developer or agency who is leaving or has left, across 16 items from source code and store accounts to signing keys, domains and legal ownership. It ranks what is missing by risk and writes a takeover plan in order, and runs in your browser.
Updated
Takeover readiness
41 / 100
At risk. 12 of 16 items need action, 3 of them critical.
- Pass · Source codeYours
- Fail · Source codePartly yours
- Fail · App StoreNot yours
- Fail · Google PlayNot yours
- Fail · Signing keysNot yours
- Fail · Signing keysNot yours
- Pass · Domains and DNSYours
- Fail · Hosting and cloudPartly yours
- Fail · Shared accessPartly yours
- Fail · Third-party servicesNot yours
- Fail · Data and backupsPartly yours
- Fail · Legal and IPPartly yours
- Fail · CI/CD and releasesNot yours
- Fail · DocumentationPartly yours
- Pass · Analytics and crash reportingYours
- Pass · Design filesYours
Your takeover plan, in order
App takeover plan (readiness 41/100, At risk) 1. Today: ask for a dated handover plan and a walkthrough call. Everything below is cheaper while they are still reachable. Phase 1: secure access (first week) 2. App Store: If the apps sit in the developer's own account, start an app transfer to your account before they leave. Open your own Apple Developer membership first. 3. Google Play: Add yourself as an owner on the existing Play Console, or move the app to your own account with a transfer. Do this before any other change. 4. Signing keys: Get the keystore file and both passwords into your password manager. With Play App Signing the upload key can be reset through Play Console; an app signing key you manage yourself cannot be reset if you lose it. 5. Signing keys: These hang off the Apple Developer account. Once you are Account Holder or Admin, create fresh ones and update the build settings, rather than hunting for the developer's files. 6. Hosting and cloud: Make your company the root or owner of each cloud account, add the new team as users, then remove the old developer's access. 7. Shared access: List every service that sends codes to the developer. Move the recovery email and the 2FA device on each one to a company address you control. Phase 2: protect data and money (weeks 1 to 3) 8. Third-party services: Make an inventory of each service and who the account belongs to. Create your own accounts and rotate every key once the new team has taken over. 9. Data and backups: Get read access, take a fresh backup into an account you own, and restore it into a scratch environment. A backup never restored is a hope. 10. Legal and IP: Read the contract for the ownership clause and for any licensed or open-source code inside. If it is silent, get a short IP assignment signed before the handover ends. This is a checklist item, not legal advice. 11. Source code: Clone with all branches (git clone --mirror) and keep the mirror. History is how a new team learns why something was built that way. Phase 3: make it runnable and documented (weeks 3 to 6) 12. CI/CD and releases: Run a full release from a clean machine or your own CI with the developer watching. Whatever fails is a missing secret or an undocumented step. 13. Documentation: Have the outgoing developer record a walkthrough of setup and deploy, and write down every environment variable and cron job. 14. Once access is yours: change every shared password and remove the previous team's logins. 15. Before new features: have the code read by someone independent, so you know what you own. That is what a code audit is for.
| Area | Item | Your answer | Risk points |
|---|---|---|---|
| App Store | The Apple Developer account is in your company's name, and you are the Account Holder | No, or the developer or agency holds it | 5 |
| Google Play | The Google Play Console account is yours, and you are an owner | No, or the developer or agency holds it | 5 |
| Signing keys | You have the Android upload keystore and its passwords, or the app uses Play App Signing | No, or the developer or agency holds it | 5 |
| Signing keys | You control the Apple certificates, provisioning profiles and the push (APNs) key | No, or the developer or agency holds it | 4 |
| Third-party services | Payments, maps, SMS, email, push and AI keys are on accounts in your name, billed to your card | No, or the developer or agency holds it | 4 |
| CI/CD and releases | You can build and release the app yourself: pipelines, scripts and secrets are in your accounts | No, or the developer or agency holds it | 3 |
| Hosting and cloud | AWS, Google Cloud, Azure, Vercel or the server host: you own the root account | Partly, or I am not sure | 2.5 |
| Data and backups | You can reach the production database, and you have restored a backup at least once | Partly, or I am not sure | 2.5 |
| Shared access | No login depends on the developer's personal email, phone number or 2FA device | Partly, or I am not sure | 2 |
| Legal and IP | A signed contract or assignment says your company owns the code, designs and content | Partly, or I am not sure | 2 |
| Source code | You hold the full commit history, not a single squashed copy | Partly, or I am not sure | 1.5 |
| Documentation | A README, an environment variable list and a deployment runbook exist and are current | Partly, or I am not sure | 1.5 |
- The weights are our own judgement of what stops you shipping, fixing or paying for the app if left unsolved. They are not an industry standard.
- Nothing you select here leaves your browser.
Code Audit: from ₹90,000 / $950
You do not yet hold everything, so the code is the next unknown. A code audit (from ₹90,000) reads it and returns a fix, refactor or rebuild verdict with file-and-line findings; we also do the takeover itself.
How is the takeover readiness score worked out?
Sixteen items cover what a new team needs before it can safely run an app: the code and its history, the Apple and Google accounts, the signing keys, the domain, the cloud accounts, third-party keys and billing, the database and its backups, CI/CD, documentation, analytics and the legal ownership of the work.
Each item has a weight from 2 to 5 for how badly its loss hurts. Having the item in your own name counts nothing against you, a partial or uncertain answer counts half the weight, and an item the developer or agency holds counts all of it. Items that do not apply to your app are left out of both sides. The score is 100 minus the share of weight lost.
The takeover plan orders what is missing in three phases. First, anything that gives someone else control over your app: accounts, domain, keys. Second, data and money. Third, the work of making the app runnable and documented without the old team. Inside a phase, the highest risk comes first.
score = 100 × (1 − Σ weight × gap ÷ Σ weight) gap: yours 0, partly 0.5, not yours 1; items that do not apply are skipped
Who should own each part of an app?
| Part of the app | Should be owned by | Why it matters |
|---|---|---|
| Source code repository | Your company (organisation owner) | The developer can be a member, never the owner |
| Apple Developer account | Your company, Account Holder | Apps and certificates hang off this account |
| Google Play Console | Your company, owner role | Store listing, releases and upload keys are managed here |
| Android keystore / upload key | Held by you, backed up twice | Play App Signing lets Google hold the signing key; a self-managed signing key cannot be reset if lost |
| Domain and DNS | Your company, at a registrar you log in to | Email, deep links and store verification all depend on it |
| Cloud and hosting | Your company, root or owner | Servers, databases and storage bills sit here |
| Payment, maps, SMS and AI accounts | Your company, your card | Keys can be revoked by the account owner at any time |
How to check whether you can take over your app
- 1Choose your situationSay whether the developer or agency is still working with you or has already gone. The plan changes: a walkthrough call is only possible while they are reachable.
- 2Answer all sixteen itemsMark each one as in your name, partly or unsure, or held by them. If you do not know, choose the middle answer; it is the honest one and it scores half.
- 3Read what is missing, ranked by riskThe table puts the items that could stop you releasing or paying for the app at the top. Fix those first even if they look technical.
- 4Copy the takeover planThe plan lists the steps in order with the first week devoted to access. Send it to the outgoing developer as the handover request, or to the team taking over.
Frequently asked questions
What should be on a developer handover checklist?
How do I take over an app from a developer or agency who has left?
What happens if my developer registered the app under their own Apple or Google account?
Do I need the Android keystore if the app uses Play App Signing?
Is this checklist legal advice about who owns my code?
How long does an app takeover usually take?
Sources
- Google Play Console Help: Use Play App Signing (checked 11 Nov 2026)
Need a custom dev tool for your team?
We build internal tools, dashboards, APIs, and SaaS platforms. If you can describe it, we can ship it.
Built by CountryDevs · No signup · No ads · We count visits, never what you enter