Contents
- Good and bad reasons to switch agencies
- Step 1: Review the contract and your rights
- Step 2: Secure every asset and access
- Step 3: Code audit by the new agency
- Step 4: Organise a transition phase and knowledge transfer
- Step 5: Choose the new agency carefully
- Typical risks when switching agencies
- Conclusion
- Frequently Asked Questions
If you want to switch app agency, one thing matters above all: source code, accesses and knowledge must be fully in your hands before the old partnership ends. An orderly switch takes a few weeks, but it prevents outages, data loss and expensive reconstruction work. This guide shows which steps make sense, and in which order.
Good and bad reasons to switch agencies
Switching is a significant effort. Before you start, make sure the problem really lies with the agency. Typical legitimate reasons include:
- repeatedly missed deadlines without a plausible explanation,
- rising bug counts after every release,
- no transparency about effort and progress,
- the agency does not (or no longer) offers the technologies or capacity you need,
- the agency is closing down or has lost the key people on your project.
Switches driven mainly by frustration about unclear requirements on your own side are less promising – the problem tends to repeat with the next partner. In that case an honest conversation about expectations and communication, as described in our article on working with an app agency, is the better first step.
Step 1: Review the contract and your rights
Before you give notice, read the existing contract carefully. Notice periods, rules for handing over materials and, above all, the usage rights to the source code are decisive. Do you hold exclusive, unlimited rights including the right to modify the code? Or did the agency reserve rights to certain components? This determines whether a new agency is even allowed to continue developing the code. Our article on source code ownership and usage rights provides background. If anything is unclear, get legal advice – this article is not legal advice.
Step 2: Secure every asset and access
The most critical part of the handover is a complete inventory. Use this table as a checklist:
| Asset | What you need | Common pitfall |
|---|---|---|
| Source code | Full repository with history, all branches | Only a ZIP of the latest state without version history |
| Store accounts | Apple and Google developer accounts in your company's name | The app sits in the agency's account and must be transferred |
| Signing keys | Android keystore or Play App Signing access, iOS certificates | A lost upload key delays updates |
| Servers and hosting | Admin access, infrastructure configuration, contracts | Servers are billed to the agency |
| Databases | Access, a current backup, schema documentation | No tested backup exists |
| Third-party services | Accounts for push, analytics, payments, e-mail delivery | API keys registered to developers' private accounts |
| Domains and certificates | Ownership and DNS access | The domain is registered to the agency |
| Design and documentation | Design files, specification, architecture and operations docs | Knowledge exists only in people's heads |
Once you have taken over, change all passwords and rotate API keys so the previous provider no longer has access. Schedule this so that live operations are not interrupted.
Step 3: Code audit by the new agency
Before the new agency quotes for further development, it should review what exists. A code audit answers questions such as:
- Can the app be built and released reproducibly from the repository?
- How current are frameworks and libraries? Are there known vulnerabilities?
- Are there automated tests, and how meaningful are they?
- Is the architecture understandable or heavily entangled?
- Which technical debt needs fixing in the short term?
The result is a solid basis for deciding whether to continue, modernise step by step or rebuild. AI-assisted analysis tools now help teams understand and document large unfamiliar codebases much faster. If the codebase is outdated, see our article on modernising legacy apps with AI.
Step 4: Organise a transition phase and knowledge transfer
Ideally, the old and new agency overlap for a few weeks. During this time, at least the following sessions should take place:
- Architecture walkthrough: the previous agency explains structure, interfaces and quirks.
- Joint build and release: the new agency builds and publishes at least once with guidance.
- Operations handover: monitoring, alerting, backups and known incident patterns are discussed.
- Open items: bug list, ongoing tickets and promised features are handed over.
If the previous agency is uncooperative or no longer reachable, the new agency has to reconstruct knowledge from code and infrastructure. That is feasible but takes noticeably longer – which is exactly why you should own the accesses from step 2 yourself.
Step 5: Choose the new agency carefully
A switch is the chance not to repeat the mistakes of the first partnership. When choosing, pay particular attention to how transparently the new partner works, whether it has experience taking over existing projects and how code rights are handled. Our article on finding the right app agency lists useful questions for the first meeting. Our clients always receive 100 % of the rights to the source code – so a later switch is possible at any time, even though we obviously do not aim for it.
Typical risks when switching agencies
- Feature standstill: no updates ship during the handover. Avoid switching just before important dates.
- Lost signing keys: without valid keys, updates cannot be published, or only with extra effort.
- Underestimated ramp-up: the new agency needs time to become as productive as the old one.
- Double costs: during the overlap you pay two providers. Budget for it from the start.
Conclusion
Switching agencies does not have to put your app at risk if you approach it in a structured way: review contracts, bring every asset and access under your own control, have the code assessed independently and plan a transition phase with knowledge transfer. The strongest protection, however, starts at project kick-off – if you own store accounts, servers and repository from day one, you can switch at any time. If you want to hand over an existing app, we analyse what is there and prepare a fixed-price offer for further development via our offer wizard.
Frequently Asked Questions
How long does switching app agencies take?
As a guideline, plan four to eight weeks for handover, audit and ramp-up. Large platforms or missing documentation can extend this.
Does the old agency have to hand over the source code?
That depends on the contract. If you acquired the usage rights to the code, you usually have a claim to it; if in doubt, seek legal advice.
Can an app be moved from one store account to another?
Yes, both Apple and Google offer a process for transferring apps between developer accounts. Ratings and users are retained, but certain prerequisites apply.
Is a rebuild better than a takeover?
Only if the code audit shows the codebase is barely maintainable or built on outdated technology. In many cases step-by-step modernisation is cheaper and less risky.