Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

ERP Vendor Failure or Acquisition: Escrow, Exit Clauses and Continuity Planning

What if your ERP vendor fails or gets acquired? Escrow, change-of-control clauses, exit rights and a continuity plan: a practical guide for CIOs and CFOs.

ERP Vendor Failure or Acquisition: Escrow, Exit Clauses and Continuity Planning

An ERP contract is signed for ten years of use, but the vendor has no obligation to exist that long. It can be acquired, merged, run into financial difficulty, or simply retire the product you depend on. In most projects this risk appears nowhere: not in the business case, not in the selection scorecard, not in the contract. It surfaces the day it is too late to negotiate.

This guide deals specifically with the risk of vendor failure or acquisition and the contractual protections that answer it. General lock-in (exit costs, technical dependency) is covered in our ERP vendor lock-in assessment and exit strategy guide. The question here is narrower: what happens to your ERP if the vendor changes hands or ceases to exist, and what have you put in place?

Why Vendor Risk Is No Longer Theoretical

The business software market is in constant consolidation: private equity funds, software groups and long-established vendors keep buying mid-sized players, often to merge product lines or rationalise teams. We analysed this dynamic in our piece on European ERP market consolidation. For a customer, an acquisition is not bad in itself, but it moves the centre of decision-making: the roadmap, pricing policy and support level no longer depend on the team you signed with.

Even the largest vendors change owners. Koch Industries announced on 6 April 2020 that it had completed the acquisition of the remaining stake in Infor from Golden Gate Capital, according to Infor’s press release, with financial terms undisclosed. The release frames the deal as continuity of growth. But it illustrates a useful point: a change of control happens, even at a global vendor, without customers being asked for their opinion. The only thing that protects a customer then is what they negotiated beforehand.

Three Scenarios to Tell Apart

The three situations call for different protections.

  1. Insolvency or formal restructuring. The vendor stops trading or enters administration, receivership or liquidation. The risk is service interruption (SaaS) or the end of patches and support (on-premise). Insolvency law in most jurisdictions (for example administration in the UK, Chapter 11 in the US, collective proceedings in France) governs whether existing contracts continue and limits the effect of some automatic termination clauses. The exact scope depends on the jurisdiction and the type of proceeding: have your clauses validated by a lawyer before relying on them.
  2. Acquisition by a competitor or a fund. The service continues, but the trajectory changes: product put into maintenance mode, forced migration to another product line, price increase at renewal, support consolidation. The risk is slow and costly rather than sudden.
  3. Product end-of-life. The vendor survives but abandons the version or module you use. This is the most frequent scenario and the one least covered by classic escrow.

Risk also differs by size. A niche vendor (industry-specific ERP, local solution) carries a higher risk of failure or dependence on a few key people, but offers considerable negotiating flexibility. A large vendor has a very low risk of failure but a real risk of strategic shift, with little room for a mid-sized customer to negotiate. Adjust your effort accordingly: escrow and financial health checks for the niche vendor; change-of-control, pricing and end-of-support clauses for the large one.

Escrow: What It Is and What It Covers

The principle of software escrow is simple: the software’s source code is deposited with a trusted third party, and the vendor and customer agree it will be released to the customer in defined circumstances, for example when the vendor can no longer support the product, as described by the Society for Computers and Law. The arrangement involves three parties: the vendor, the beneficiary customer and the escrow agent.

On-Premise Source Code Escrow vs. SaaS Escrow

For an ERP installed in your own data centre or at a hosting provider of your choice, classic escrow deposits the source code, build scripts and technical documentation. On release, you (or a third-party provider) can in theory rebuild and maintain the deployed version.

For a SaaS ERP, code alone is not enough: the application runs in the vendor’s environment. SaaS escrow therefore extends protection beyond code to data and environment, because your data now lives in the cloud, according to the same SCL analysis. In practice, a usable SaaS deposit should contain:

  • the source code and dependencies for the production version;
  • deployment scripts and a description of the infrastructure (IaC, containers, configuration);
  • operating procedures (runbooks): backup, restore, upgrade, monitoring;
  • regular copies of your data and configuration;
  • the inventory of third-party components and their licences, plus the cloud account access needed to run them.

Some providers also monitor the vendor’s payments to its hosting provider as an early-warning signal. NCC Group describes such a monitoring and continuity approach on the SaaS side in its escrow-as-a-service offering. Check case by case what each offer actually covers.

Limits: Code Without a Team or Infrastructure Is Rarely Usable

This is the central caveat. Receiving an ERP’s source code is not the same as receiving a working ERP. You need:

  • developers able to read and maintain a code base they did not write, often a very large one;
  • a production infrastructure to rebuild, with its third-party licences (database, reporting engine);
  • the ability to keep up with regulatory changes (e-invoicing, taxes, accounting standards) that the vendor handled until then.

For a full ERP, this takeover cost is considerable and rarely budgeted. Escrow is therefore less a continuity insurance than a transition safety net: it buys you the time and the right to migrate without being locked in. A well-designed escrow includes a verification test of the deposit (does the code compile, does the deployment work?). Without that check, you may be holding a useless archive.

Two points to settle before signing:

  • The real cost. It includes deposit and update fees, any technical verification, and often a split between vendor and customers. Ask for a detailed quote: the price depends on the verification level and scope. For an ERP, it is generally the verification, not the mere deposit, that gives escrow its value.
  • Who triggers the release. The escrow agreement must list the trigger events precisely (insolvency proceedings, cessation of business, end of support, uncured material breach) and the procedure: who establishes the event, within what time, and what recourse exists if the vendor disputes it. A vague trigger paralyses the release the day you need it.

The Clauses to Negotiate

Escrow only protects in extreme cases. Most of the protection is won in the main contract’s clauses, including on the integrator side (see also our article on fixed price vs. time and materials for the project part).

  • Change of control. Require notification within a defined period, and a right to terminate without penalty, with a pro-rata refund of prepaid amounts, if the vendor is acquired by a direct competitor or the product is deprecated in the months that follow.
  • Exit and reversibility. Describe the handback: format, timeline, assistance. Exit must be a contractual deliverable with a known cost, not a statement of principle.
  • Data export in an open format. Require a complete export (data, attachments, history, audit logs) in a documented format (CSV, JSON, SQL, XML). An export that loses the relationships between objects is unusable.
  • End-of-support notice. Set a minimum support period after the announcement of a product or version retirement, with regulatory patches included during that period.
  • Price caps. Cap subscription and maintenance indexation (index, annual ceiling), and prohibit re-scoping of the licensed perimeter after an acquisition.
  • Continuity during insolvency proceedings. Provide for data access and continued service during a transition period, without assuming that an automatic termination clause will be enforceable: have it reviewed by an insolvency lawyer.

Assessing Vendor Health Before Signing

A simple scorecard applied to every finalist beats a feeling of confidence. Eight to ten criteria are enough:

  1. Published accounts: revenue, profit, cash and equity over several years (company registry filings).
  2. Ownership: independent vendor, subsidiary of a group, or private equity fund approaching exit.
  3. Customer concentration: does it depend on one or two large accounts?
  4. Recurring revenue: share of subscription and maintenance versus licences and projects.
  5. Roadmap: published, dated, and delivered over the last two years.
  6. Product investment: size of the R&D team, release frequency.
  7. Partner ecosystem: several independent integrators able to take over a project.
  8. Comparable references: customers of your size and sector who are willing to talk.
  9. Key-person dependency: founder, architect, single product expert.
  10. Track record of transparency: past reaction to incidents, price changes and product retirement announcements.

Score each criterion from 0 to 2 and compare. The aim is not to eliminate niche vendors but to calibrate protections: a low score calls for a verified escrow, a costed exit plan and an independent data backup.

The Customer-Side Continuity Plan

Whatever the quality of the contract, continuity is prepared on your side. Three workstreams matter most.

Independent data backups. Do not rely solely on the vendor’s backups. Schedule regular exports, stored with a third party, in a format readable outside the ERP, and test restoration at least once a year. An export that has never been reopened is only a hypothesis.

Documentation of your configuration. Chart of accounts, workflows, permissions, pricing rules, custom reports, scripts: everything that makes your instance different from a standard one must be described and kept outside the vendor. This is what allows another provider, or another product, to take over your business logic.

Dependency mapping. List the interfaces (bank, payroll, e-commerce, e-invoicing, EDI), the APIs in use, the vendor’s subcontractors and third-party platforms. For each dependency, identify what breaks if the vendor disappears tomorrow, and how long a workaround would take.

Add one last item: a costed exit plan (duration, resources, budget) updated every year. It is not there to be executed, but so that the decision, when the day comes, is made on facts.

Table: Scenario, Warning Sign, Action, Clause

ScenarioWarning signImmediate actionProtective clause
Vendor insolvencyLate supplier payments, executive departures, delayed releases, late filing of accountsExport all data, activate escrow if conditions are met, secure accessEscrow with precise triggers, continuity during proceedings, open export
Acquisition by a competitorAcquisition announcement, leadership change, product-line mergerCheck the notification period, review price and support clauses, open a market consultationChange of control with exit right, price cap
Product end-of-lifeVersion in “maintenance only”, silent roadmap, product team departuresCost the migration, get the end-of-support date in writingMinimum end-of-support notice, regulatory patches included
Degraded supportRising response times, rotating contactsDocument incidents, escalate per service levelsService levels with penalties, right to terminate for breach
Price rise after acquisitionNew price list, re-scoping of the licensed perimeterCompare with the contractual cap, do not sign an amendment under pressureCapped indexation, frozen scope

10-Point Checklist Before Signing

  1. Has the vendor been scored on the health scorecard (accounts, ownership, customer concentration)?
  2. Does the contract provide change-of-control notification and a penalty-free exit right?
  3. Is exit described (format, timeline, cost, assistance)?
  4. Is the data export complete, documented, in an open format, with attachments and logs?
  5. Is escrow provided for (or justified as unnecessary for this vendor profile)?
  6. Are the release trigger events and the party who establishes them defined?
  7. Is the deposit technically verified, with a fixed update frequency?
  8. Are the end-of-support notice and continued regulatory patches in writing?
  9. Is indexation capped and the scope frozen in case of acquisition?
  10. Is an internal continuity plan (independent backups, documentation, dependency mapping, costed exit plan) budgeted?

A contract that fails to answer at least half of these points deserves renegotiation before signing, rather than after an event.

Going Further

To compare your finalists on an objective basis, including vendor risk, download our ERP evaluation scorecard: 30 criteria across 100 points to compare three vendors side by side.