01 · Checklist
What should you collect when taking over code from another vendor?
Collect the items in the table, in this order, and tick each one only after you have used it yourself. A document that exists is not the same as a procedure that works. The sections below explain each group. If you are early in a dispute, read the signs a project needs rescue first.
| Area | What to collect | Proof it is done |
|---|---|---|
| Access | Repository admin, cloud account roles, domain registrar, DNS, app-store accounts, third-party service logins | You can log in with accounts in your own organization |
| Code | Full repository with history, branches, build scripts, dependency lists, licences | A new machine builds the code from the repository alone |
| Documentation | Architecture notes, data model, API specs, runbooks, known issues | A new engineer finds the answer to three test questions in the documents |
| Environments | Production, staging and test setups, configuration, secrets inventory, deploy steps | You deploy a change to staging without help |
| Data | Database schema, backups, restore steps, data retention rules | A restore into a clean environment succeeds |
| Knowledge transfer | Recorded walk-throughs, a named contact for questions, a list of open work | The outgoing team answers a question list in writing |
02 · Access
Which access should you move first?
Move ownership of the code, cloud accounts and domain first, because everything else depends on them.
- 01
If these sit under the vendor's logins, they control the project even after the contract ends.
- 02
Ask for admin roles on accounts in your organization's name, not shared passwords. Rotate every credential the vendor used once you have your own, and remove their access on the day they hand over. Also list third-party services the app calls, such as payments, email and maps, since each has its own account and billing.
03 · Documentation
What documentation is worth asking for?
Ask for the documents that answer how the system fits together and how to run it: an architecture overview, the data model, API descriptions and runbooks.
- 01
Those save the most time for a new team.
- 02
Expect gaps. Many projects have little written down. In that case an independent code audit can produce the missing structure from the code itself, and it records what is risky at the same time. Treat any document as a claim until you have compared it with the code.
04 · Environments
How do you confirm the environments really work?
Confirm environments by using them: build the code on a clean machine, deploy to staging, and restore a database backup.
- 01
These three tests find most handover problems within days.
- 02
Collect a list of configuration values and secrets, who owns each, and where each is stored. Check that production and staging are separate, and that staging does not point at production data. Ask what runs on a schedule, such as jobs, backups and certificate renewals, since nobody notices those until they stop.
05 · Knowledge transfer
How do you get knowledge out of the outgoing team?
Get it through a written question list and recorded sessions, not a single meeting.
- 01
Walk through the code with the people who wrote it, record the sessions and ask them to explain the parts that look odd.
- 02
Agree a short period of paid availability after the last day, with a named contact and a response time, so your new team can ask what the documents do not say. Put it in the exit terms before the old vendor leaves, since goodwill fades quickly. Compare your plan against the guide to choosing a rescue team if you are still selecting who takes over.
06 · Next step
How does Ace8 take over code from another vendor?
Ace8 is the modernization practice of AceMQ.
- 01
AceMQ engineers start with a read-only look at the code under an NDA, run a code audit, then stabilise it, add tests and a deploy pipeline. The method is on the software project rescue page. The price is a quote on request, with a fixed price for the first audit.
- 02
Request a rescue audit and we will say what state the handover is in and what to collect next.