How to switch software development companies without losing your code, data or apps

Switching software development companies usually happens under pressure. Deadlines keep slipping, invoices keep coming, or your developer has simply stopped answering. At that point the real risk is not technical. The real risk is finding out, too late, that your domain, your hosting, your source code or your app's developer account belong to someone else.

This checklist is the one we use when we take over a project. It covers who owns the code, every account you need to recover, the right order to do it in, and the mistakes that cost founders weeks.

01Start with ownership: who owns the source code?

In the United States, code written by an outside contractor generally belongs to the contractor unless your contract assigns the intellectual property to you in writing. Many founders assume they own what they paid for. Without an IP assignment clause, that is often not the case.

Before you announce anything, pull up your contract and look for:

• an IP assignment or source code ownership clause, and what it covers;
• the termination and notice terms;
• any handover or transition obligations (documentation, knowledge transfer);
• whether third-party or pre-existing code is licensed to you rather than assigned.

If ownership is unclear, fix it in writing before the relationship ends. A short source code ownership agreement signed now is far cheaper than a dispute later. This guide is general information, not legal advice: have a lawyer review your specific contract.

02The access checklist

For every item below, the rule is the same: you must be the owner of the account, not a guest on it.

Domain and DNS

Check which registrar holds the domain and, above all, whose name is on it. The registrant should be your company, with an email address you control. To move the domain, you need the authorization code and the domain must be unlocked. Registrars often block transfers for a period after a recent registration or transfer, so check early. If DNS is managed elsewhere, such as Cloudflare, recover that access too.

Repository and database

Ask for the repository to be transferred to your organization on GitHub, GitLab or Bitbucket, with its full history. A zip file is not a handover: you lose the history, and nothing proves it matches what runs in production. For the database, get a full backup and restore it somewhere to prove it works.

How to transfer an app to another developer account

Apple and Google both offer an official way to move an app from one developer account to another: App Transfer in App Store Connect, and app transfer in the Google Play Console. Both require the accounts to be in good standing with current agreements accepted, and some services (push notifications, in-app purchases, sign-in, iCloud) may need to be reconfigured afterwards. Start the process early and read each store's current requirements before you begin.

03The right order

1. Secure the domain and DNS. They can take your site and email down overnight.
2. Get the repository and a tested database backup.
3. Move payment and app store accounts into your name.
4. Rotate every password and API key. The previous vendor should keep no access.
5. Have the new team audit the project before any new development starts.

04Red flags during a handover

• "We'll send you the code at the end" with no repository access today.
• Production running on the vendor's personal or agency account.
• No documentation of how to build and deploy the project.
• Secrets and API keys hardcoded in the source code.
• Pressure to rebuild from scratch before anyone has looked at what exists.

05How to tell your current developer

Secure the critical accounts first, then end the engagement in writing. Respect the notice period, and attach a precise list of what you expect and by when: repository transfer, database backup, account ownership changes, documentation. Keep it factual and polite. You will likely need a few answers from them during the transition, and a calm handover is faster than a fight.

Ask for a written inventory of every service the product uses. That is where the surprises hide: an email service on someone's personal credit card, an API key tied to a test account, a certificate that expires next month.

06If your developer has disappeared

It happens more often than people think. Where to start:

• Domain: if your company is the registrant, the registrar can restore access with proof of ownership. If the developer registered it in their own name, get legal advice quickly.
• Hosting and cloud: if the account is billed to your company, the provider can usually restore access once you prove it.
• App stores: Apple and Google support can help when the developer account belongs to your organization.
• Code: without repository access, parts of the code can sometimes be recovered from the production server. It is a last resort, and an audit will tell you what is salvageable.

Keep a written record of every attempt to reach them. It matters if the situation has to be settled another way.

07SaaS products: your data, not just your code

If you are moving off a SaaS tool rather than custom software, the question becomes data portability. Check which export formats your contract guarantees (CSV, SQL dump, API), whether exports include attachments, history and settings, and how long data stays available after cancellation. If customer personal data is involved, plan its transfer and its deletion on the old platform.

08Questions to ask your next development partner

• Will every account be opened in our company's name from day one?
• Does the contract include a full IP assignment for the code?
• Where is the code hosted, and will we have admin rights on the repository?
• How is the project documented, and how would another team take it over?
• What happens to our access if we stop working together?

09Next time: write the exit into the contract

The easiest switch is the one you planned for on day one. With your next development partner, ask for an IP assignment clause, every account opened in your company's name from the start, documentation kept up to date, and a written handover process. A good partner will agree without hesitation: they keep clients through the quality of their work, not by holding their access hostage.

10What happens after the switch

Once you hold the keys, the new team's first job is to understand what exists: code quality, security, dependencies, hosting and running costs. That is exactly what the Lunarion audit delivers: a written diagnosis, priorities and the cost of each option, before you commit to anything.

11Frequently asked questions