Short answer
Before handing a project to a new developer, gather source code access, server and hosting access, database backups, domain and DNS control, third-party account credentials, existing documentation, a list of known problems and the business goals. Ownership of all accounts should be in your name.
In this article
Access
- Source code repository (GitHub, GitLab or Bitbucket) with admin rights
- Hosting or cloud account and server access
- Domain registrar and DNS
- Database access and a recent backup
Third-party services
- Email and notification services
- Payment providers and API keys
- Analytics, error tracking and monitoring
- App store or developer accounts for mobile apps
Knowledge
- Any documentation, diagrams or design files
- A list of known bugs and complaints
- What the software must do and who uses it
- Contacts for previous developers, if reachable
Business context
- Your top three priorities for the next 90 days
- Deadlines, launches or campaigns that matter
- What must never break
Do not worry if something is missing
Missing items are normal in takeovers. A good team works out what can be recovered and what must be rebuilt, and tells you plainly.
Missing most of this list? That is fine. Start with our free assessment and we will tell you what can be recovered.
Related solutions
- Abandoned project takeover: The developer stopped replying, the agency closed, or the project simply ran out of steam. We take over the code, the servers and the plan, and get you moving again.
- Move off an old developer's server: If your software runs on a server or account you do not control, we move it to hosting that is yours, safely and with documentation.
- Finish an unfinished app: You paid for something that stopped at 60%. We work out what is really done, what is missing, and the fastest safe way to launch.
Prefer a quick answer? Try the free fix-or-rebuild self-check.