How to switch developers or agencies without losing your product
What to secure before you say anything, what a proper handover includes, and the mistakes that make switching painful.
Short answer
Before you tell your current developer you're leaving, make sure you own and can access everything: the code repository, hosting, domain, database, app store accounts and every paid service. Then ask for a written handover, and have the new team prove they can release a change on their own before the old contract ends.
Switching developers is common, and usually fixable. What makes it painful is doing things in the wrong order: announcing the change, then discovering the code, the hosting or the app store account was never in your name.
This guide is the order that avoids that. It isn't legal advice. If there's a dispute over the contract or payments, talk to a lawyer.
Step 1: Take stock, quietly
Before any conversation about leaving, list everything your product depends on and check who controls it. Here's where things usually live:
| What | Where it usually lives | What you need |
|---|---|---|
| Source code | GitHub, GitLab or Bitbucket | Owner or admin access on a repository your company owns |
| Hosting / servers | AWS, Google Cloud, Azure, DigitalOcean, or a hosting provider | Account in your company's name, your card on file |
| Domain and DNS | GoDaddy, Namecheap, Cloudflare and similar | Domain registered to you, login you control |
| Database and backups | Usually inside the hosting account | Access, plus a recent backup you have a copy of |
| Mobile app listings | Apple Developer, Google Play Console | Developer accounts in your company's name |
| Paid services | Payments (Razorpay, Stripe), email, SMS, maps, analytics | Accounts and billing in your name |
| Design files | Figma or similar | Owner access to the files |
| Secret keys and settings | Environment variables on the server | A list of what exists, transferred securely |
If anything important sits in the developer's personal or company account, that's your first priority.
Step 2: Move ownership into your name
Ask to be added as an owner or admin wherever you aren't already. Where possible, transfer the account itself to your company and put billing on your card. Most platforms have a standard transfer process. Framed as tidying up admin, this rarely causes friction.
Step 3: Check the contract
Look for four things: who owns the intellectual property and when it transfers, the notice period, any handover obligations, and what's still owed on either side. Settle outstanding questions before the handover, not after.
Want someone experienced to look at your project? The first 15-minute call is free.
Step 4: Ask for a proper handover
A handover is more than a zip file of code. Ask for:
- How to run the product on a new developer's computer, step by step.
- How changes get released to the live product.
- A list of every setting and secret key the product needs (the list, not the values sent over email).
- A short overview of how the pieces fit together.
- Known bugs and unfinished work.
- Every third-party service used, and what it's for.
- Credentials shared through a password manager, not chat messages.
Step 5: Make the new team prove it
Before the old contract ends, ask the new developer or agency to make a small change and release it to the live product entirely on their own. If they can, the handover worked. If they can't, you've found the gap while the old team can still help.
Step 6: Close the door behind you
Once the new team is running independently, remove the old team's access and change shared passwords. It's routine, not personal.
Common mistakes
- Paying the final invoice before the handover is done.
- Announcing the switch before securing access.
- Agreeing to a full rebuild without a second opinion. New teams often recommend starting over. Sometimes that's right. Often the existing code is fixable, and a rebuild costs months. An independent review can tell you which it is.
- Losing knowledge that was never written down. Ask the outgoing team to record short walkthrough videos of the tricky parts.
Not sure whether you need to switch at all? Start with how to tell if your developer is doing a good job.
Common questions
Who owns the code when I hire an agency?
It depends on your contract. Most founders want a clause saying the intellectual property transfers to their company on payment, with the code kept in a repository the company owns. If your contract is unclear, get legal advice.
My developer won't give me access to the code. What can I do?
Ask in writing, referring to your contract. Most access problems are resolved once the request is formal. If it becomes a dispute over ownership or payment, speak to a lawyer.
Should I rebuild the product with the new developer?
Not without an independent opinion. A rewrite is expensive and slow. Often the existing code can be fixed. An outside review can tell you which parts are worth keeping.