Software Handover: What You Need Before Changing Development Providers

Software Handover: What You Need Before Changing Development Providers

Before you change development providers, make sure you will have – and can actually use – everything needed to run, change and publish your software without the old provider: the source code with its full history, access to every account and server, your data, instructions for building and deploying the system, and a list of every external service and password it depends on. Collect all of it while the old provider is still cooperating, and test it. The only real proof of a complete handover is that someone else can build and deploy the system from what you received.

Start with the contract

Before any technical step, read what you signed. Look for:

  • Rights to the code. Who owns it, or what licence you have – and whether it lets you give the code to another developer and change it. If the wording is unclear, ask a lawyer before the relationship ends, not after.
  • Handover obligations. Notice periods, whether the provider must help with the transition, and at what rate.
  • Whose name the accounts are in. Domains, hosting, app store accounts and paid services are often registered by the developer "for convenience". Our article on who owns your domain, hosting, code and accounts covers this in detail.
  • Personal data. If the provider hosts or processes personal data for you, GDPR requires a data processing contract. Ireland's Data Protection Commission lists among the minimum terms that at the end of the processing, on the controller's instruction, the processor deletes or returns the personal data. In practice: ask for the data to be returned first, then for written confirmation that it has been deleted.

If your system is a cloud service

If what you are leaving is a cloud service – software you use on subscription, or that the provider runs on its own servers for you – the EU Data Act may help. It has applied since 12 September 2025. According to the European Commission, providers of platform and software as a service must at a minimum let you export data in a commonly used and machine-readable format, and switching charges, including charges for data egress, are removed entirely from 12 January 2027. Germany's regulator, the Bundesnetzagentur, explains the steps: after the customer's notice, the provider has a maximum of two months to make the technical preparations; a transitional period of at most 30 calendar days follows (extendable to seven months if the provider shows that is not technically feasible); and the data must remain retrievable for at least 30 days after switching is complete. Services custom-built for one customer and not offered at broad commercial scale are partly exempt, though not completely. Whether and how this applies to your arrangement is a question for a lawyer, but it is worth knowing the rules exist.

The handover checklist

AreaWhat you should receive
Source codeThe complete repository with its history and all branches – not a zip copied from the server. Everything: back end, admin panel, mobile apps, scheduled jobs, import scripts, database migration files.
Build and deploymentStep-by-step instructions to install, configure, build and deploy; the versions of the language, framework and database the live server actually runs; configuration examples without real passwords.
Servers and accountsAdministrator access to hosting or cloud accounts, domain and DNS, the email-sending service, backups, monitoring and error reporting – ideally in your company's name.
DataA full database export and all uploaded files, a description of the main tables, where backups are kept and how to restore one.
External servicesA list of every integration – payments, couriers, accounting, maps, SMS, email – with the account it belongs to and who to contact there.
Passwords and keysA complete inventory of API keys, certificates and service passwords: what each is for and where it is stored.
LicencesPaid components, themes, fonts and libraries: in whose name, and whether they can be transferred.
KnowledgeAn overview of how the parts fit together, known bugs and open tasks, unusual business rules, and anything that "just has to be done by hand" every month.

For passwords and keys, the OWASP Secrets Management Cheat Sheet sets a useful standard: it should be "immediately apparent to an organization what a secret is used for and where to find it". It also warns against secrets hardcoded in source code – if the handover reveals passwords inside the code, moving them into configuration is a sensible early task.

Mobile apps: the store accounts matter most

An app published under the developer's own store account is not fully yours until it is transferred. Both stores allow transfers, with conditions:

  • Apple App Store. The account holder starts the transfer and the receiving account holder accepts it. The app keeps its reviews, ratings and bundle ID, and users continue to receive updates. Some things don't move – the Apple Pay merchant ID, for example – and the new owner only receives sales information for transactions after the transfer, so back up what you need first.
  • Google Play. The original account submits the request and the target account approves it. Google transfers users, statistics, ratings, reviews and subscriptions, but not bulk exports or earnings reports, which should be downloaded beforehand. Connections to services such as Firebase or Google Analytics have to be set up again. If you don't want to keep the same app signing key, the new owner can request a key upgrade for new installs.

The simplest rule for the future: publish apps from developer accounts that belong to your company, and add developers as users.

Test the handover before you say goodbye

A folder of files and a document are not proof. Before the old relationship ends:

  1. Have the new developer build the system from the repository and deploy it to a test server using only the instructions received.
  2. Restore a recent backup into that test environment.
  3. Log in to every account on the list – hosting, domain, stores, external services.
  4. Make a small, real change and take it all the way to a test release.
  5. Write down every gap and send the old provider one consolidated list of questions.

If the contract allows, agree a short period during which the old provider answers questions. A few paid hours here are usually cheaper than reverse-engineering something nobody documented.

Close the old access – calmly and in order

Once the new team has everything working, remove the old provider's user accounts and change the passwords and API keys they knew. This is not an accusation; it is ordinary practice when someone no longer needs access. OWASP notes that a new secret should be quick to create and put in place, and that exposed keys should be revoked immediately. Do it in a planned order – create the new key, update the configuration, test, then revoke the old key – so integrations don't stop in the middle of a working day. See also our article on user roles and permissions.

What to expect from a new provider

Reading someone else's code takes time, so the first weeks will go partly into understanding the system rather than adding features; honest estimates include that. Be cautious if the first recommendation is to rewrite everything or to upgrade every component to the newest version. Old is not the same as broken: a working system on an older platform can stay as it is unless there is a real reason to change it – a vulnerability that actually affects it, a host or store dropping support, or a feature you need. Our article on legacy software explains how to decide. Equally, a good new provider should tell you plainly which parts are fragile.

Warning signs of an incomplete handover

  • you only have FTP access to the server, not a code repository;
  • nobody can explain how a new version gets to the live server;
  • some passwords are known only to the old developer;
  • the domain or the app store account is in the developer's name;
  • no one has ever restored a backup.

If you are planning to change providers, we can review what you have received, try to build and deploy it on a test server, and tell you plainly what is missing before you end the old contract. Read more about our web-based software development or contact us to talk about your system.

Sources

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.