Business

Software Handover Checklist: What a Vendor Must Deliver Before the Project Closes

November 11, 2026 · 4 min read · Etzal Group Team

An application can pass every acceptance test and still leave its owner dependent on one vendor for every future change. The gap is closed at handover, and only if you ask for the right things. A software handover checklist agreed at the start of the project is the simplest protection a client has.

The items below are grouped by the question each one answers.

Can we get to everything?

  • Source code in a repository the client owns or can access, with full history, not a zip file of the last version.
  • Accounts for hosting, domain names, app stores, email, SMS and payment gateways registered in the company's name.
  • Credentials for servers, databases and third-party services, transferred through a password manager and rotated after handover.
  • Licences for any paid components, with renewal dates and who pays.
  • A list of every environment: production, staging, test, and where each lives.

Ownership of accounts is the item most often overlooked. A domain registered under a developer's personal email is a risk that surfaces at the worst time.

Can someone else run it?

  • Deployment guide. Step by step, from a clean machine to a running system.
  • Configuration reference. Every setting and environment variable, what it does and what a valid value looks like.
  • Scheduled jobs. What runs automatically, when, and what happens if it fails.
  • Monitoring and alerts. What is watched and who is notified.
  • Runbook. What to do for common incidents: the site is down, a queue is stuck, a job failed, the disk is full.

A good test is a dry run. Someone outside the project follows the guide and deploys to a fresh environment while the original team watches without helping.

Can someone else change it?

  • Architecture overview. One or two pages with a diagram: the main parts, how they talk to each other, and where data is stored.
  • Data model. The main tables or collections and what each important field means.
  • Integration notes. For each external system: what is exchanged, how it is authenticated, and who to contact.
  • Business rules. Where the non-obvious rules are implemented, with examples.
  • Development setup. How a new developer gets the system running locally.
  • Tests. How to run them and what they cover.
  • Known issues and shortcuts. An honest list of what was postponed.

Documentation does not need to be long. It needs to be true on the day of handover.

Is the data safe?

  • Backups running on a schedule, stored separately from the main system.
  • A restore test performed and recorded, with the time it took.
  • Retention rules: how long backups and logs are kept.
  • An export of all business data in an open format.
  • Personal data notes: what is stored, where, and how deletion requests are handled.

A backup that has never been restored is a hope, not a control. Insist on seeing one restore.

Is it secure today?

  • Administrator accounts reviewed, and vendor access reduced to what support requires.
  • Default and shared passwords removed.
  • Dependencies updated, with a list of versions.
  • Security findings from testing either fixed or listed with a plan.
  • A record of who has access to what.

What happens next?

  • Warranty. How long defects are fixed without charge and what counts as a defect.
  • Support agreement. Response times, hours, and how to report a problem.
  • Change process. How new requests are estimated and approved.
  • Contacts. Names, not just a general address.
  • Training delivered to users and administrators, with materials left behind.

How to run the handover

  1. Agree the list in the contract. Attach it as a schedule.
  2. Review it mid-project. Documentation written at the end is always thinner.
  3. Hold a handover session. The vendor walks through each item, and the client's team asks questions.
  4. Verify. Do the dry-run deployment and the restore test.
  5. Sign off in writing, listing any item still open and its due date.
  6. Release the final payment when the list is complete.

If the vendor stays on for maintenance

Handover still matters. People change, companies change, and a client that holds its own code, accounts and documents can negotiate support on equal terms. It also makes the vendor's own work easier when a new engineer joins the account.

We include a handover pack in every Enterprise Software project, and we are sometimes asked to assess a system handed over by another vendor. If you are about to close a project and want the checklist reviewed, write to us.

Summary

At handover you should hold the code, the accounts and the credentials. You should have documents that let someone else deploy, operate and change the system, backups that have been restored once, a security review, and clear terms for what happens next. Agree the list at the start and pay the last instalment when it is complete.

Frequently asked questions

When should handover be planned?

At contract stage. List the handover items in the agreement and tie the final payment to their delivery. Asking for documentation after the last invoice is paid rarely produces good documentation.

Who should own the accounts for hosting, domains and third-party services?

The client. Accounts should be registered under a company email address with the vendor added as a user. If the vendor owns the accounts, every future change, including changing vendor, depends on their cooperation.

How do we check that the documentation is good enough?

Ask someone who was not on the project to deploy the system to a fresh environment using only the documents. If they succeed, the documentation works. If they have to ask the original developers, add what they asked to the documents.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.