Request a quote
Emergency SectorsCareers About us Blog Get in touch
Two developers at a desk with two monitors full of code; the standing colleague points at a line

Software escrow: what if your software supplier goes under?

Software escrow is an arrangement under which the source code of a package is held by an independent third party, so you can get to it if the supplier goes into administration or stops. It sounds like insurance, but it only works if data, documentation and a plan sit alongside that code. This is what to know before you sign one.

7 min read Written by the ITproposal team
Short answer

Software escrow places the source code of a package with an independent third party, with release conditions agreed in advance.

Source code alone will not keep you running: without build instructions, data, documentation and someone who can work with it, you have a folder of files.

With SaaS, your data matters more than the code. Secure exportability and an exit plan, and have the escrow agreement itself reviewed by a lawyer.

What software escrow is, and what it is not

Software escrow involves three parties: the supplier, the customer and an independent escrow agent. The supplier deposits the source code and related materials with the agent. A software escrow agreement sets out when the agent releases them to the customer, usually on insolvency, when the supplier stops maintaining the product, or when it persistently fails to meet its obligations.

Escrow does not give you a second supplier. It gives you the right and the means to have the package maintained yourself, or by someone else. Whether that works in practice depends on what was deposited and who picks it up afterwards.

Nor is it a guarantee that the software keeps running. When a supplier fails, the service desk, the hosting and further development usually go too. Escrow only covers the part for which the code is needed.

When it is worth it

For most software you do not need escrow. Microsoft 365, a mainstream accounting package or a standard CRM can be replaced by another product if something goes wrong. Escrow becomes worth considering when three things are true at once:

  • The package is business critical. Without it, a core process stops: planning, production, patient records, the tills.
  • There is no alternative you can switch to quickly. Bespoke software, sector software with a handful of customers, or an integration only this supplier understands.
  • The supplier is small or dependent. A firm with a few developers, one key person or one large investor.

A useful test from your business continuity plan: how long can you manage without this system, and how long would it take to choose a replacement, configure it and migrate the data? If the second is far longer than the first, the escrow conversation is worth having.

Source code alone is not enough

The most common mistake is a deposit that contains nothing but a copy of the code. A developer who has to take over the package needs much more. Agree what the deposit must contain as a minimum:

  • Build instructions that let an outsider get from code to a working version, including the compilers, frameworks and versions used.
  • Dependencies: third-party libraries and components, and under what licence they may be used once the supplier is gone.
  • Database and configuration schemas, migration scripts and the settings that belong to your installation.
  • Technical documentation on the architecture, the integrations and the known quirks.

Ask for verification. Many escrow agents offer to check whether the deposit is complete and whether a working build can be produced from it. Without that test you only find out whether the deposit is usable on the day you need it, which is the worst day to find out.

With SaaS it is about your data and the environment

With software delivered as a service, the source code on its own does little for you. The application runs in the supplier’s cloud environment, on its account, with its configuration. If it fails, that environment can be offline within days because the hosting bill goes unpaid.

That is why there are variants that go beyond code, often called SaaS escrow or continuity escrow: arrangements covering access to the hosting environment, keeping the hosting paid for a bridging period and transferring the cloud account. What exactly they cover varies by provider; read it rather than assume it.

More important than any escrow variant is being able to take your own data with you. Ask the supplier in advance how you get a complete export, in what format, with which fields and attachments, and how long it takes. An export you have never tried is a promise.

What you arrange alongside escrow

Escrow is one measure against supplier risk, and usually not the first. The same preparation that helps when a supplier fails also helps when you simply want to switch:

  • Data exportability, written into the contract and actually tested once a year, in an open or documented format.
  • An admin account of your own and your own backups of the data, so you are not relying on the supplier’s backup.
  • Documentation of your own configuration: which integrations exist, which processes depend on it, who the key users are.
  • An exit plan with the steps, the timescales and the cooperation the supplier provides when you move.

How such a move works once it happens is covered in our article on changing IT supplier without damage.

Reading the release conditions

The most valuable part of an escrow agreement is the list of events that trigger release, and the procedure that goes with it. Look at three questions:

  • What counts as a trigger. Only insolvency, or also the end of support for your version, an acquisition by a party that phases the product out, or a prolonged failure to fix serious defects.
  • Who decides and how fast. Whether the supplier can object, how long that period is, and what happens in the meantime.
  • What you may do with the code. Only use and maintain it for your own organisation, or also have it modified by a third party.

On insolvency, an administrator or liquidator is appointed to act for all creditors. How an escrow arrangement stands against that is a legal question that differs by jurisdiction and by agreement. It belongs with a lawyer, not with your IT supplier.

Escrow is not a one-off

A deposit that is three years old does not help you with the version you use today. Agree that the supplier delivers an up-to-date deposit with each major release, or at a fixed frequency, and that the agent tells you when that does not happen.

Name someone internally who owns the arrangement. They track whether deposits arrive, whether verification has been done, and whether the agreement still matches what you use. Packages get replaced, modules are added and suppliers move to the cloud; the escrow agreement does not follow on its own.

Keep it in your contract register next to the support agreement and the data processing agreement, with the renewal date.

Where our work stops

What we do. We help with the technical side: mapping which systems are business critical and how dependent you are on a supplier, testing data exports, setting up backups and admin accounts in your organisation’s name, documenting your configuration and writing an exit plan that is technically workable.

What we do not do. We are not an escrow agent: we do not hold source code for third parties, verify deposits or enter into escrow agreements. Nor are we lawyers. We do not assess whether an escrow agreement or its release conditions are legally sound, including on insolvency. Have that reviewed by a lawyer, and choose the escrow agent yourself.

Frequently asked

Questions we get about this

The five that come up most often.

What is software escrow?

Software escrow is an arrangement between a software supplier, a customer and an independent escrow agent. The supplier deposits the source code and related materials with the agent, who releases them to the customer if an agreed event occurs, such as insolvency or the end of maintenance. That lets the customer have the package maintained if the supplier disappears.

When do you need software escrow?

When a package is business critical, there is no alternative you can move to quickly, and the supplier is small or vulnerable. For standard software you would simply replace with another product, escrow is usually unnecessary. Check in your continuity plan how long you can manage without the system and how long a replacement would take.

Does software escrow work for SaaS?

Source code alone does little for SaaS, because the application runs in the supplier’s environment. Some variants also cover access to the hosting and a bridging period. More important is that you can obtain a complete export of your own data, both in the contract and in practice.

What should a software escrow deposit contain?

Besides the source code: build instructions, the versions of tools and frameworks used, third-party dependencies and their licences, database and configuration schemas, and technical documentation. Have the deposit verified, so you know a working build can be produced before you need it.

Can you draft or hold our escrow agreement?

No. We are not an escrow agent and not lawyers: we do not hold source code for third parties, and we do not draft or legally assess escrow agreements. We do help with the technical work around it, such as testing data exports, documenting your configuration and an exit plan.

Do you know what happens if your supplier disappears?

We map which systems are business critical, test whether you can get your data out and write the exit plan. The escrow agreement itself goes to your lawyer.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call