Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment
GuideGuide

A software handover checklist for taking over code from another vendor.

A handover fails when it is a single meeting. Use this list to collect access, documents, environments and knowledge before the old vendor leaves.

AceMQ engineering team4 min readEngineer-reviewed

Stacks we work in

  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
The short answer

A software handover checklist covers four things: access to the code and accounts, documentation, working environments, and knowledge transfer from the people who built it. Collect all four before the outgoing vendor's last day, and prove each one by building and running the system yourself. If a handover has already gone wrong, see software project rescue.

Next stepFixed-price assessmentInventory, risk score and a phased roadmap with a fixed price for phase one.Book a fixed-price assessment

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.

AreaWhat to collectProof it is done
AccessRepository admin, cloud account roles, domain registrar, DNS, app-store accounts, third-party service loginsYou can log in with accounts in your own organization
CodeFull repository with history, branches, build scripts, dependency lists, licencesA new machine builds the code from the repository alone
DocumentationArchitecture notes, data model, API specs, runbooks, known issuesA new engineer finds the answer to three test questions in the documents
EnvironmentsProduction, staging and test setups, configuration, secrets inventory, deploy stepsYou deploy a change to staging without help
DataDatabase schema, backups, restore steps, data retention rulesA restore into a clean environment succeeds
Knowledge transferRecorded walk-throughs, a named contact for questions, a list of open workThe 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.

  1. 01

    If these sit under the vendor's logins, they control the project even after the contract ends.

  2. 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.

  1. 01

    Those save the most time for a new team.

  2. 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.

  1. 01

    These three tests find most handover problems within days.

  2. 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.

  1. 01

    Walk through the code with the people who wrote it, record the sessions and ask them to explain the parts that look odd.

  2. 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.

  1. 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.

  2. 02

    Request a rescue audit and we will say what state the handover is in and what to collect next.

FAQ

Frequently asked questions

Short answers to what buyers ask first. Something else on your mind? Ask an engineer.

A list of what a new team needs from the old one: access, code, documentation, environments, data and knowledge transfer, each with a way to prove it works.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

Inventory
Every application, its stack and what it depends on.
Risk score
Where a change is likely to break, ranked.
Phased plan
What moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer.

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.