Ask about each asset separately
| Asset | Question to settle | Evidence |
|---|---|---|
| Custom code | Who holds rights, and what use/modification is permitted? | Agreed contract terms |
| Third-party component | Which licence and ongoing obligations apply? | Component and licence register |
| Cloud and domain accounts | Who owns billing/admin access and exit transfer? | Account owner and transfer procedure |
| Business data | Can a complete usable export be delivered? | Test export with relationships |
An exported folder of source files does not by itself prove ownership or provide a runnable system. Open-source components may have their own licence conditions. Record the actual agreed terms; this checklist does not determine legal rights.
Rehearse an exit deliverable
Before the final handover, have the receiving team build or run the agreed version in an isolated environment, inspect an export and locate the recovery procedure. List missing dependencies and resolve who provides them. Define any paid transition work separately in the proposal, without assuming that it is free or automatically included.
The company owns the repository but only the supplier can deploy. What remains unresolved?
Show the worked answer
Deployment account authority, build dependencies, release instructions and a receiving-team rehearsal. Repository ownership alone does not close the operational handover.