Checklist · Taking over a project
Handing over a software project: the checklist for both sides
By MervenorPublished Last reviewed 4 min read
A handover fails when something the old team held in its head or its own accounts does not move with the code. Move the code with its history, every account into the owner's name, every secret rotated, and enough documentation for someone new to build and deploy it. Agree a short support window, then remove the old team's access.
Why handovers go wrong
Most handovers move a zip file or a repository and nothing else. The domain is still in the agency's registrar account, the hosting is billed to a former employee's card, the deploy only works from one laptop, and the reason for half the design is in someone's memory. None of that shows up until something breaks.
Before the handover
Agree in writing what is being handed over, by when, and who on each side signs it off. Make an inventory together: repositories, environments, accounts, third-party services, scheduled jobs and data stores. If the relationship is ending badly, secure the accounts that matter most before announcing anything; the 10-step recovery checklist gives the order.
The checklist
Code with its history
Transfer the repositories themselves, with every branch and tag, not a copy of the latest files. Confirm nothing lives only on someone's machine.
Accounts in the owner's name
Domain and DNS, hosting and cloud, databases, email sending, analytics, app stores, payment providers and every paid API. Billing moves too.
Secrets rotated
Every key, password and token the old team could see is replaced after the transfer, not before.
Environments and deploys
The receiving team builds and deploys from a clean machine, following written steps, at least once while the old team is still available.
Data
Backups exist, a restore has been tested, and the schema and its migrations are in the repository.
Documentation
A README that gets someone running, a runbook for common incidents, an architecture overview and a list of the important decisions and why they were made.
Open work
Known bugs, half-finished features, pending upgrades and anything promised to customers, in the issue tracker.
Licences and agreements
Third-party licences, and a signed assignment of the work to the client if the contract requires one.
The handover call
Book at least one working session where the old team walks through the architecture, the deploy and the last few incidents, and the new team asks questions with the code open. Record it if both sides agree. Most of the value is in the questions nobody thought to write down.
After the handover
Agree a short window in which the old team answers questions, then remove its access from every repository and account on a named date. Check the alerts and monitoring now go to the new owners. Within the first weeks, have the receiving team confirm they can still build, deploy and restore without help.
Questions people ask
Who should own the accounts during a project?
The client, from day one, with the agency invited as a user. It costs nothing and removes the hardest part of any later handover.
What if the old agency will not hand over?
Recover what you can in the right order (domain first), then rebuild the rest from what is deployed; the recovery checklist covers it.
How long should a handover take?
Long enough for the receiving team to deploy and restore on its own once while the old team is still reachable.
Receiving an application from another team? The Perlustra audit checks what you have received in five business days and gives you a priced plan. Handing client work over as an agency? We take it on as a white-label partner.