Leaving a Software Agency: The Handover Checklist
What should a software agency handover checklist include?
A software agency handover checklist should cover source repositories, deployment and recovery instructions, service accounts, credentials, licences, documentation and open issues. Treat the handover as complete when the replacement team can operate and change the software without depending on the outgoing supplier. Ask that team to demonstrate this through a witnessed deployment or recovery exercise before signing off.
The useful question is simple: if the outgoing agency became unavailable tomorrow, could your business keep running and could another team safely make the next change?
What should you agree before the handover starts?
Set the scope in writing. Name the products, websites, applications and supporting services being transferred. Include unfinished work, retired components that still hold business data, and services billed separately from development.
Assign someone from your business to accept the handover and someone from the replacement team to verify the technical parts. Ask the outgoing agency to name the person responsible for each item.
Give every checklist item an owner, an acceptance condition and a status. “Documentation shared” is too vague. “Replacement team followed the instructions and started the application” describes something you can verify.
Agree how questions will be handled during the transition, what support is included, and what happens to unresolved items when the engagement ends. Read the existing agreement before assuming that source ownership, account transfers or transition support are included.
What evidence should you collect for each item?
Use a shared checklist that records evidence alongside delivery.
| Area | What to receive | How to verify it |
|---|---|---|
| Repositories | Complete source, history and related assets | Replacement team can access, build and test the software |
| Deployment | Release instructions and rollback steps | Replacement team completes an agreed deployment |
| Accounts | Ownership, administrators, billing and recovery access | Your business can administer each account |
| Credentials | Secure access to required secrets | Replacement team authenticates through its own access |
| Licences | Dependency and subscription inventory | Each item has an identified owner and continuation decision |
| Open issues | Known defects, unfinished work and limitations | Replacement team reviews impact and next actions |
| Recovery | Backup access and restoration instructions | Replacement team restores and checks an agreed backup |
Keep passwords and recovery codes out of this checklist. Record where authorised people can retrieve them securely.
Which repositories and development materials should transfer?
Request every repository needed to build, test and maintain the product. Include the application, supporting services, automated tests, deployment definitions and reusable components developed for the project.
Ask the outgoing agency to identify which version is currently live and explain how it relates to the delivered source. Include design assets, editable originals and instructions for producing any generated materials.
The replacement team should verify that it can:
- Access the repositories through accounts it controls.
- Review the available change history and release records.
- Obtain the required development tools and dependencies.
- Build and run the application from a fresh setup.
- Run the tests and understand any failures or exclusions.
Ask about private packages or shared components controlled by the agency. For each dependency, agree whether it will transfer, remain available under a continuing agreement, or need replacement.
Keep ownership questions separate from access checks. Having a copy of code does not answer what your agreement permits you to do with it.
What should deployment and recovery instructions explain?
Ask for instructions written for a capable developer who has never worked on the product. They should explain prerequisites, required access, configuration, build steps, release steps and checks after release.
Include background jobs, scheduled tasks, integrations and any manual actions needed alongside a release. Ask what happens when a release includes a change to stored data, and which changes cannot simply be reversed.
The recovery instructions should identify available backups, who can access them, how to restore them and how to check the restored application. Agree what an acceptable recovery looks like for your business, including any acceptable loss of recent work.
A rollback should have a clear trigger, an owner and a verification step. “Deploy the previous version” is incomplete if nobody has checked what happens to data written by the newer version.
For guidance on making instructions usable, see documentation best practices in software projects.
Which accounts and credentials need attention?
Create an account inventory covering hosting, domain registration, business email delivery, file storage, payments, monitoring, analytics and other connected services.
For each account, record:
- The account owner and authorised administrators.
- The billing contact and payment responsibility.
- The recovery contact and authentication method.
- The services or products that depend on it.
- Whether ownership will transfer or continued access is required.
Prefer accounts owned by your business, with individual access for each supplier. Where the agency uses a shared account for several customers, agree a migration or a clearly defined continuing arrangement.
Transfer secrets through an agreed secure method. Check access from the replacement team's own accounts rather than relying on an outgoing developer's active session.
Plan credential changes and access removal around the transition. Before removing access, verify that releases, integrations and recovery arrangements work with the replacement credentials. The broader principles are covered in data security in modern applications.
What should the licence and subscription inventory contain?
Ask for an inventory of third-party software, paid components, fonts, images, plugins and subscriptions used by the product.
For each item, request the licence or purchase record, account owner, renewal arrangements and any restrictions relevant to continued use or modification. Flag anything purchased through the agency that your business cannot renew directly.
Do not accept “all dependencies included” as the final answer. Ask which items require an ongoing payment, a separate agreement or a replacement after the agency leaves.
Where rights or transfer terms are unclear, get the relevant agreement reviewed before treating the item as accepted.
How should open issues and unfinished work be handed over?
Request a current list of known defects, incomplete features, operational limitations and manual workarounds.
Each item should explain the affected behaviour, business impact, steps to reproduce where relevant, and the next recommended action. Distinguish work that has been released from work awaiting review, testing or deployment.
Ask for known test failures and areas without meaningful test coverage. A test report needs enough context for the incoming team to understand what it actually checked.
Include recurring maintenance tasks and decisions the team deliberately postponed. Use technical debt explained for founders to help separate accepted compromises from unfinished promises.
Acceptance need not mean every issue is fixed. It should mean the remaining issues are visible, understood and assigned.
How do you run a witnessed handover exercise?
Choose an exercise that tests the independence you need. A deployment tests the release path; a recovery tests restoration. Run both if both are acceptance conditions.
Use a controlled setting with agreed safeguards. For a deployment, ask the replacement team to make a small, reversible change, run the relevant checks, release it and verify the result. Include a rollback where appropriate.
For recovery, ask the team to retrieve an agreed backup, restore it into an isolated setting and check that the application and representative records work.
The outgoing agency may observe and answer questions, but the replacement team should operate the controls. Record every missing permission, undocumented step and intervention. Update the instructions, then repeat the affected steps without prompting.
A recording is useful supporting material. Successful execution is the acceptance evidence.
What common mistakes leave the handover incomplete?
Accepting a download as proof of usability. Verify that the replacement team can build and operate what it receives.
Leaving ownership until the final day. Resolve account, billing and licence questions while the outgoing team is still available.
Treating a meeting as documentation. Capture the instructions and decisions needed after the people leave.
Removing access before testing replacements. Verify the new access arrangements before completing the removal.
Signing off with unnamed exceptions. Give every outstanding item an owner, impact and agreed next action.
What else do founders ask about agency handovers?
Can we complete the handover without a replacement agency?
Use an independent technical reviewer or an appropriately qualified member of your team to verify it. Someone needs to test whether the materials work without the outgoing supplier's guidance.
What if we use a hosted product rather than custom software?
Adjust the checklist to your agreement. Focus on administration, data export, integrations, configuration and continuity. Do not assume the underlying source code is part of the purchase.
Should we sign off if some items remain open?
Only accept clearly recorded exceptions that your business understands and agrees to carry. Keep final acceptance separate from acknowledging that files or documents have arrived.
Once the handover is done, an inherited codebase audit checklist helps you confirm what you received.
*This post is general information, not legal advice. Check your own agreement and consult a qualified lawyer where rights or obligations are unclear. Last reviewed: October 2026.*