Handover · Checklist
Five checklist areas, an illustrative timeline, a handover record template and what to do if the previous developer will not cooperate.
Last updated: October 2026. Written by Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions.
Quick answer
A safe developer handover covers ownership and access (business-owned accounts, credentials in a password manager, rotated keys), documentation (PRD, data model, privacy rules, workflows, integrations, release routine, known issues), a walkthrough, a quality review of security and structure and written confirmation of ownership. Remove the outgoing developer’s access only after the new person understands the app. If the previous developer will not cooperate, secure what you control, commission an independent review and take legal advice if ownership is disputed.
Key takeaways
- The business, not the developer, should own the app account and services.
- Hand over documentation, a walkthrough, test accounts and a release routine.
- Review the app for security and structure; produce a risk list.
- Rotate credentials and remove old access after the transition.
- Confirm ownership and terms in writing.
In this guide
What is a developer handover?
A developer handover is the planned transfer of an app, its accounts, its knowledge and its responsibilities from one developer or studio to another person or team: a new agency, an in-house hire or the owner. Handovers happen when projects end, relationships change or people move on. Done carelessly, they strand the owner with an app nobody understands. Done well, the next person can work safely within days.
Handover checklist
1. Ownership and access
- The app account is owned by the business, with the outgoing developer as a collaborator, not the owner.
- Domain registrar, DNS, email service, payment provider, analytics and other services are in the business’s name.
- Credentials and recovery routes are stored in the business’s password manager.
- The incoming person is given only the access they need, and the outgoing developer’s access is then removed.
- Shared passwords and keys are changed after handover.
2. Documentation
- The PRD and any later scope changes.
- Data model, privacy rules and option sets described.
- Key workflows and scheduled tasks described.
- Integrations, calls, data exchanged and key locations.
- Release and rollback procedure.
- Known issues, workarounds and the reasons for decisions.
- A support runbook. See our guides to documenting an app and writing a runbook.
3. Walkthrough
- A recorded or live walkthrough of the data model, main flows and risky areas.
- A session on how to release safely and test access control.
- Time for the new person to ask questions, and a short period of availability afterwards.
4. Quality check
- The new developer reviews the app for security, data structure, performance and clarity. See our security guide and database design mistakes.
- A list of risks and recommended fixes is produced.
- Test accounts and the test checklist are handed over.
5. Commercial and legal
- Ownership of the work and documentation is confirmed in writing.
- Outstanding invoices, warranties and support terms are settled.
- Confidentiality continues, and data protection terms cover the transfer of access.
- Subcontractors and third-party tools are listed.
A handover timeline (illustrative)
| When | Action |
|---|---|
| Before the end date | Agree what will be handed over and when. Confirm ownership of accounts. |
| Two to four weeks before | Documentation completed and reviewed. Inventory of services and keys prepared. |
| One to two weeks before | Walkthrough sessions. The incoming person gets access and reviews the app. |
| Handover day | Final access changes. Credentials rotated. Sign-off. |
| After | A short period of questions. Review of issues found. Update the documentation. |
Handover record template
Handover record
App: ________ Outgoing: ________ Incoming: ________ Date: ________
Account and service ownership confirmed: ________
Documentation delivered (list): ________
Walkthroughs completed (dates): ________
Access granted to incoming and removed from outgoing (dates): ________
Credentials rotated: ________
Risks and recommended fixes: ________
Sign-off (owner, outgoing, incoming): ________
What if the previous developer will not cooperate?
- Establish who owns the accounts and what your contract says.
- Secure whatever you control first: domain, payment and email accounts.
- Commission an independent review of what exists.
- Decide whether to repair, partly rebuild or rebuild. See our comparison of Bubble.io and custom code for platform questions.
- Take legal advice if ownership is disputed.
What mistakes should you avoid?
- Leaving the app in the outgoing developer’s account.
- Skipping documentation because the relationship is ending.
- Forgetting to rotate credentials.
- Removing the outgoing developer’s access before the new person has understood the app.
- No walkthrough.
- No written confirmation of ownership.
Simple Automation Solutions takes over and reviews apps built by others, and supports handovers to in-house teams, with support from $35 per hour and no retainers or minimums. Builds start at $3,500. See what to cut before you build and what maintenance involves.
Frequently asked questions
What should be in a developer handover checklist?
Ownership and access, documentation, a walkthrough, a quality review, and commercial and legal confirmation, with credentials rotated and access changes recorded.
Who should own the app account?
The business, with developers added as collaborators.
How long should a handover take?
It depends on the app, but allow weeks for documentation, walkthroughs and review, not days.
What if the developer will not hand over?
Establish ownership, secure the accounts you control, commission an independent review and take legal advice if ownership is disputed.
Should the outgoing developer keep access?
Only for a short, agreed period for questions, then remove it and rotate credentials.
Taking over an app or handing one over?
Email us what you have. We will review it and help you plan a safe handover.
Athar Ahmad, Certified Bubble.io Developer and Tech Architect, Simple Automation Solutions
About Simple Automation Solutions (SA Solutions)
Simple Automation Solutions is a Bubble.io development studio led by Athar Ahmad, a Certified Bubble.io Developer and Tech Architect. It builds web and mobile apps, client portals and SaaS products for founder-led businesses such as law firms, accounting firms, boutique agencies and consultants. Services include a free 30-minute Idea Audit, a $345 Discovery Sprint (a Product Requirements Document delivered within 24 hours, credited toward the build) and builds starting at $3,500. Website: sasolutionspk.com.
