How to deliver an application to another team without relying on the developer

Published on 2026-11-14 by frfrand

Checklist of repositories, documentation, secrets, infrastructure, CI/CD, access, and testing for a software handover.

# How to deliver an application to another team without depending on the developer

A project is not fully delivered if the client has a working URL but cannot recover the code, change credentials, or rebuild the deployment. The transfer must demonstrate that a different team can operate and maintain the system without depending on the author's memory.

1. Ownership and repositories

Deliver appropriate access to the Git repository under an organization controlled by the owner. Identify the production branch, delivered version/tag, licenses, and dependencies. Include instructions for git clone, installation, test execution, and build. Confirm that the history does not contain secrets; if there were leaks, rotate credentials—deleting the last commit is not enough.

2. Minimum documentation

| Document | Content | | --- | --- | | README | Objective, local startup, commands, tests | | Architecture | Services, API, DB, queues, and dependencies | | Infrastructure | Domains, DNS, VPS, proxy, and storage | | Runbook | Deploy, restart, health checks, rollback | | Data | Schemas, migrations, backups, and restoration | | Operations | Known incidents, alerts, and contacts |

Document difficult decisions and known limitations; do not turn the README into an enormous manual that is impossible to update.

3. Access without sharing passwords

Use roles per person and individual credentials in GitHub, hosting, DNS, database, email provider, and third-party services. A secrets manager facilitates transfers; do not deliver a real .env file via email or chat. Apply least privilege, rotate credentials after handover, and revoke tokens from the outgoing team once the new team has verified control.

4. Data transfer and deployment

Prepare a recoverable backup and a tested restoration procedure. Document how to deploy a new version from Git, run migrations, check health, consult logs, and roll back to a compatible version. If the system processes payments or personal data, define a transition window and supervision tasks. Avoid transferring unnecessary or sensitive data without authorization.

5. Independence test

The new team must be able, on its own: 1. Clone, install dependencies, and run tests. 2. Deploy a small fix in staging. 3. Locate logs and metrics from a simulated incident. 4. Restore a copy in test infrastructure.

Record evidence of each step and note blockers. Delivery is accepted when those tests are passed and the owner confirms receipt of essential resources.

6. Transition and closure

Define support period, responsibilities, and procedures for follow-up questions. Transfer billing accounts and domain ownership when applicable. Deliver final inventory of components, licenses, recurring costs, pending risks, and documentation. Deactivate old accesses only after verifying that the operation does not depend on them.

Related: what is CI/CD and database migrations.

Frequently asked questions

Is delivering a ZIP enough? No. Is it mandatory to deliver secrets in plain text? No, secure access controls are transferred. How do I verify the delivery? With an operational test executed by the new team.

  • handoff
  • documentación
  • GitHub
  • DevOps
  • mantenimiento

Keep reading

All articles · VPS plans