Company

How do you take over app development from a previous vendor?

A long wooden table and yellow chairs in a meeting room

A vendor handover involves more than receiving the code. Find out which access and information to prepare, and how to plan support alongside the first development changes.

A new team needs the code, a way to run it and an understanding of how the business uses the application. A repository link alone is not enough. Before the handover, establish which services must keep working, who currently handles incidents and which changes users need most. This separates urgent support from the longer development backlog.

1. What should you prepare before changing vendors?

Start with a short explanation of who uses the app, what they do with it and which tasks matter most to the business. Add known defects and requested changes. Distinguish problems that stop people working from ideas that can wait.

Prepare an inventory of the material and services to hand over:

  • the repository, its history and the version currently running in production;
  • instructions for building, testing and releasing the application;
  • the servers, databases and third-party services it relies on;
  • integration documentation and contacts who understand those connections;
  • service costs, renewal dates and the accounts used for billing.

Identify who controls each account and can grant the new team access. Separately agree what code, documentation and support responsibilities will be transferred. These are matters for the parties to settle; a technical review does not replace contractual arrangements.

2. Why check whether the application can be rebuilt?

A working production system does not prove that the supplied code can reproduce the same version. The incoming team should check the build, configuration and dependencies, preferably in a test environment. This can expose missing files, undocumented manual steps or services available only through the former vendor’s accounts.

Ask the team to complete a few important user tasks and make a small trial change. Check how that change will be tested and rolled back, as well as whether it works. Missing documentation does not make the project unusable, but recovering the necessary knowledge must be included in the initial work.

Grant access to data and services according to the agreed tasks. Establish who manages accounts and when obsolete permissions will be removed. Passwords should not be sent alongside project descriptions or bug reports.

3. How should support pass to the new team?

Record who handles requests until the handover and when the new vendor takes responsibility. Explain where incidents are reported and who can approve a release. If the outgoing team is available, prepare specific questions and a list of missing information for them.

Avoid filling the first stage with every overdue feature. It might cover making the build repeatable, resolving an urgent defect and delivering one small change that users can check. That provides a practical way to assess how the team works with the existing application before committing to a larger programme.

4. What should the initial assessment deliver?

You need to know what can be developed in the current code, what slows changes down, which risks need attention and where to start. Recommendations should distinguish verified problems from questions that still need investigation. Rewriting the entire app is not the default answer to every difficulty.

Aseity provides code audits and technical consulting, including assessments when a company takes over a project from another vendor. The output is a short document with recommendations and an order of actions, discussed with your team. It can then inform an agreed first stage of product development and ongoing support.

5. Questions before handing over an application

Does the app need to be rewritten immediately?

No. First assess how it works and where its limitations are. Some problems may be addressed in particular modules, configuration or the release process.

What if there is almost no documentation?

Collect what is available and identify people who know the system. Reconstructing the setup instructions and essential business rules should be an explicit task with an agreed scope.

Can all future changes be priced straight away?

Before the code and integrations have been reviewed, such an estimate depends on many assumptions. Agree the assessment and initial tasks first, then use the findings to plan further work.

Have a project to deliver?

Describe it in a few sentences. We will reply with questions or a proposal for a call.

Describe your project

Back to blog