Why Exit Terms Deserve the Same Attention as Price

Procurement teams negotiate SaaS contracts on the terms that matter on day one: subscription price, user counts, uptime, and support. The exit terms tend to be read last, if at all, because nobody signing a five-year deal expects to leave. Yet the exit terms are the ones that decide whether the company can meet its record obligations after the relationship is over. In regulated work, that is a compliance question, not only a commercial one.

Record Life Outlasts Contract Life

A GxP record has a legal life set by regulation and by the company’s own retention schedule. Batch records, stability data, deviation and CAPA files, training records, clinical trial records, and pharmacovigilance data all carry retention periods that commonly run well beyond the term of any software subscription. A contract that ends in year four does not end the obligation to produce a record created in year one.

EU GMP Annex 11 states the principle plainly: “Access to data should be ensured throughout the retention period.”1 FDA’s 2024 guidance on electronic systems in clinical investigations makes the same point from the contract side. It recommends that agreements with IT service providers include “A plan that ensures the sponsor will have access to data throughout the regulatory retention period.”2 Neither text says this is the vendor’s problem. Both put the duty on the regulated company.

The Exit You Plan Versus the Exit You Get

Some exits are planned. A company outgrows a system, consolidates platforms after a merger, or chooses a better product at renewal. Those exits leave time to negotiate. Others are not planned. The vendor is acquired and the product is retired. The vendor fails. A dispute leads to termination for breach. In those cases, the company has only what the contract already says.

The best-known example from cloud computing is not a GxP system, but it shows how short an unplanned exit can be. In September 2013, the cloud storage provider Nirvanix told customers it was closing and gave them roughly two weeks to retrieve their data, with a first deadline of September 30 that InfoWorld reported may have been extended to October 15.3 Customers holding large volumes of data had to move it over ordinary network links in that window. A validated GxP system adds a further burden: the export has to be complete, verified, and documented, not just copied.

The core point. The SaaS vendor operates the system, but the regulated company owns the records and the retention obligation. An exit clause is how the company keeps control of its records when the vendor relationship ends, whether the ending is planned or not.

Why Standard Terms Fall Short

Standard SaaS agreements are written for general business customers. Their exit terms usually look something like this: the customer may download its data during a short period after termination, using the export tools in the product, after which the vendor deletes it. That wording leaves the important questions open. Does “data” include the audit trail? Does the export keep the link between each record and its electronic signatures? Is the format documented? Who pays for help? What happens to backups? What if the export fails verification on day 28 of a 30-day window?

For a GxP buyer, each of those open questions is a risk to record integrity. Settling them is easiest before signing, when the vendor wants the deal, and hardest after notice of termination, when the vendor has little reason to help.

What the Regulations Expect When a SaaS Contract Ends

No GxP regulation contains a clause titled “exit.” The expectations come from requirements on record access, readability, audit trails, signatures, and supplier agreements. Read together, they describe what an exit has to deliver.

EU GMP Annex 11

The current Annex 11, in force since 2011, sets several requirements that apply directly to the end of a SaaS relationship.1

  • Formal agreements (clause 3.1). When third parties provide or retain a computerized system or related service, formal agreements must exist and should state the third party’s responsibilities clearly. The services covered include retaining a computerized system and data processing.
  • Migration (clause 4.8). When data are transferred to another format or system, validation should include checks that data are not altered in value and/or meaning during this migration process. An exit is a migration.
  • Data storage (clause 7.1). Stored data should be checked for accessibility, readability, and accuracy, and access should be ensured throughout the retention period.
  • Audit trails (clause 9). “Audit trails need to be available and convertible to a generally intelligible form and regularly reviewed.” An audit trail that cannot leave the vendor’s system in readable form fails this test at exit.
  • Electronic signatures (clause 14). Signatures are expected to be permanently linked to their respective record.
  • Archiving (clause 17). Archived data should be checked for accessibility, readability, and integrity, and the ability to retrieve the data should be ensured and tested when relevant changes are made to the system.

The draft revision of Annex 11, released for consultation in 2025 and still a draft, goes further and names the issue directly. Its section on supplier and service management lists what a contract with a service provider should cover. One item reads: “Defines an exit strategy by which the regulated user may retain control of system data.”4 The draft also says archived data and metadata should be retrievable in a format that allows searching and sorting, or exportable to a tool that does. The draft has no final text or effective date, so it is not yet a requirement. It is a clear signal of where inspectors’ expectations are heading.

21 CFR Part 11

Part 11 applies to electronic records and signatures that FDA’s predicate rules require. Several of its controls apply to records held in a SaaS system, whoever operates it.

  • Section 11.10(b) requires “The ability to generate accurate and complete copies of records in both human readable and electronic form suitable for inspection, review, and copying by the agency.”5
  • Section 11.10(c) requires protection of records to enable their accurate and ready retrieval throughout the records retention period.
  • Section 11.10(e) requires secure, time-stamped audit trails, and adds: “Such audit trail documentation shall be retained for a period at least as long as that required for the subject electronic records and shall be available for agency review and copying.”
  • Section 11.50 requires signed records to show the printed name of the signer, the date and time of signing, and the meaning of the signature, and requires those items to be part of any human readable form of the record.6
  • Section 11.70 requires signatures to be linked to their records so that they cannot be excised, copied, or otherwise transferred to falsify an electronic record by ordinary means.7

FDA’s Part 11 scope and application guidance describes how the agency applies some of these controls. It says FDA does not intend to object if a company archives required electronic records to paper, microfilm, or a standard electronic file format such as PDF, XML, or SGML, provided predicate rule requirements are met and “the records themselves and any copies of the required records should preserve their content and meaning.” On copies, it adds that if a company can search, sort, or trend its records, “copies given to the Agency should provide the same capability if it is reasonable and technically feasible.”8 That sentence is a useful test for any export format you accept at exit.

FDA and EMA Guidance on Hosted and Outsourced Systems

FDA’s 2024 questions and answers guidance on electronic systems in clinical investigations addresses hosted systems directly. Beyond recommending an access plan for the retention period, it says: “When systems are decommissioned and cannot be recommissioned or a contract with a hosted system ends, sponsors should ensure that the metadata are obtained and retained and can be linked to each corresponding data element.”2 The guidance is written for clinical investigations, but the reasoning applies to any GxP record held in SaaS.

EMA’s guideline on computerized systems and electronic data in clinical trials is more explicit still about vendor failure. In its annex on agreements, it says: “Agreements should ensure reliable, continued and timely access to the data in case of bankruptcy, shutdown, disaster of the vendor, discontinuation of service by the vendor or for reasons chosen by the sponsor/investigator (e.g. change of vendor).”9 Its section on database decommissioning adds that the sponsor should ensure, contractually where a service provider is involved, that archived formats allow the database to be restored, including dynamic functionality and metadata such as audit trails, event logs, edit checks, queries, and user logs. Where restoration is no longer possible, the data and metadata should still be available in dynamic data files.

The UK MHRA’s data integrity guidance covers cloud and SaaS providers in its own section. It says contracts should ensure timely access to data, including metadata and audit trails, for the data owner and regulators, and that “Contracts with providers should define responsibilities for archiving and continued readability of the data throughout the retention period.”10

SourceWhat it expects at contract endContract term it points to
EU GMP Annex 11 (2011)Access for the full retention period; readable audit trails; data unchanged in value and meaning during migrationExport completeness, migration verification, archive access
Draft Annex 11 (consultation, not final)A contract that defines an exit strategy so the user keeps control of system dataA written exit plan in the contract
21 CFR Part 11Complete copies in human readable and electronic form; audit trails kept as long as the records; signature manifestation and linkageExport formats that keep audit trails and signatures with records
FDA clinical systems guidance (2024)A plan for access through the retention period; metadata obtained and linkable when a hosted contract endsRetention plan and metadata in the export
EMA clinical computerized systems guidelineContinued access on bankruptcy, shutdown, or change of vendor; restorable archive formatsInsolvency and discontinuation clauses, archive format
MHRA data integrity guidanceDefined archiving responsibility and continued readability for the retention periodPost-termination retention terms

The EU Data Act Switching Rules: What Applies and When

The EU Data Act, Regulation (EU) 2023/2854, includes a chapter on switching between data processing services. It sets minimum exit terms for cloud contracts across sectors, and it matters to GxP buyers because it gives them rights they used to have to negotiate for.11

Application Date and Scope

The Data Act applies from 12 September 2025. Its switching rules apply to providers of data processing services, wherever they are established, that provide those services to customers in the EU. The definition of a data processing service is broad, covering on-demand network access to a shared pool of configurable computing resources.

Two points of scope are worth confirming for your own contracts. First, Germany’s Bundesnetzagentur (Federal Network Agency), which publishes guidance on the Act, states that the rules apply to all typical cloud service delivery models such as IaaS, PaaS, and SaaS. Second, it states that both existing contracts concluded before 12 September 2025 and new contracts concluded after that date must comply with the switching chapter.12 This differs from the Act’s separate chapter on unfair contract terms, which has its own later dates for older contracts. Your legal team should confirm how each of your contracts is treated.

The Minimum Contract Terms

Article 25 requires the switching rights and obligations to be set out in a written contract and lists what that contract must include at a minimum.11 The terms most relevant to a GxP exit are these:

  • Notice period. A maximum notice period to start the switching process, which may not exceed two months.
  • Transitional period. A mandatory maximum transitional period of 30 calendar days to complete the switch, during which the contract stays in force and the provider must give reasonable assistance, maintain business continuity, share known risks to continuity, and keep the data secure.
  • Longer transitions. If 30 days is technically unfeasible, the provider must say so within 14 working days of the request, justify it, and propose an alternative period of no more than seven months. The customer also has the right to extend the transitional period once, for a period the customer considers more appropriate.
  • Exit strategy support. An obligation on the provider to support the customer’s exit strategy relevant to the contracted services, including by providing all relevant information.
  • Data specification. An exhaustive specification of all categories of data and digital assets that can be ported, including at a minimum all exportable data, and an exhaustive list of any internal data exempted because of a risk to the provider’s trade secrets.
  • Retrieval period. A minimum data retrieval period of at least 30 calendar days after the transitional period ends.
  • Erasure. A clause guaranteeing full erasure of the customer’s exportable data and digital assets after the retrieval period, or after a later date the parties agree, provided the switch was completed successfully.

Article 26 adds an information duty. The provider must describe available switching methods, formats, restrictions, and known technical limitations, and must point the customer to an up-to-date online register of the data structures, data formats, standards, and open interoperability specifications in which exportable data are available. For a GxP buyer doing due diligence, that register is a good place to start.

2 monthsMaximum notice period to start switching under Data Act Article 2511
30 daysMaximum transitional period, extendable by the customer once, plus at least 30 days for retrieval11
12 Jan 2027Date after which providers may not impose any switching charges11

Switching Charges

Article 29 phases out switching charges. From 11 January 2024 to 12 January 2027, providers may charge reduced switching charges that do not exceed the costs directly linked to the switching process. From 12 January 2027, they may not impose any switching charges at all.11 Before signing, the provider must give clear information on standard service fees, early termination penalties, and any reduced switching charges. A GxP contract signed in late 2026 will run mostly in the period after charges end, so the fee terms should be written with that date in mind.

Exceptions and Pending Changes

Article 31 sets out a narrow regime for custom-built services. Where most of a service’s main features were custom-built for one customer and the service is not offered at broad commercial scale, some obligations do not apply, including the charge phase-out. The written contract terms in Article 25 still apply. Non-production versions offered for testing and evaluation for a limited time are outside the switching chapter entirely.

The European Commission’s Digital Omnibus package, published in November 2025, proposes changes to these rules. The Commission describes a narrow exemption for custom-made services and for services from small and medium-sized enterprises and small mid-caps, limited to contracts signed before the Data Act applied.13 A July 2026 Greenberg Traurig analysis of the Council’s compromise text also describes a proposal to allow proportionate early termination penalties in fixed-term contracts, and notes that the text was still subject to negotiation.14 As of this writing, these are proposals. The switching rules in force are the ones in the 2023 regulation.

The Commission has also published draft non-binding standard contractual clauses for cloud computing contracts, including clauses on switching and exit, with a template switching and exit plan.15 They are voluntary, but they are a useful starting point for wording, and several of their structures appear later in this article.

What the Data Act does not do for a GxP buyer. A 30-day retrieval period protects against a vendor refusing to release data. It does not provide access for a 25-year retention period. The definition of exportable data excludes assets protected by the provider’s intellectual property or trade secrets, and the provider may list internal data it will not export. The Act does not say that an export must keep audit trails linked to records or signatures linked to what was signed. And it applies only to services provided to customers in the EU. A US-only contract gets none of these rights unless they are written in. Treat the Data Act as the minimum and negotiate GxP terms on top of it.

Export Completeness: What Your Data Has to Include

The most common gap in SaaS exit terms is a definition of “customer data” that sounds complete but is not. Ask a vendor what its export includes and the answer is often a list of record types. A GxP record is more than its current values. It includes the history of how it got there, who signed it and why, and the configuration that gave it meaning.

The Parts of a GxP Record

It helps to break the export into parts. Each part below needs to be named in the contract, because a vendor that exports only the first part can claim to have exported “all customer data” in good faith.

Record componentWhat it includesWhy it matters at exitAcceptable export form
Record contentCurrent field values, documents, attachments, resultsThe record itselfStructured data (CSV, JSON, XML) with a data dictionary; native files for attachments
Version historyAll prior versions and lifecycle statesShows what was effective whenEach version as its own record, with state and effective dates
Audit trailWho did what, when, old and new values, reason for changeRequired for the life of the record under Part 11 and Annex 11Structured data keyed to record and version identifiers
Electronic signaturesSigner name, date and time, meaning, link to the signed versionSignatures must stay linked and readableStructured signature records plus a human readable rendition showing the manifestation
ConfigurationWorkflows, lifecycles, picklists, field definitions, user rolesExplains what records meant at the timeConfiguration export or documented specification, versioned
User and access historyAccounts, roles, and permission changes over timeSupports attributability of past actionsStructured data with effective dates
System logs relevant to GxPLogin history, alarms, interface logs where they support recordsSupports reconstruction and investigationsStructured data or log files with a stated format

Audit Trails Are Exportable Data

The Data Act defines exportable data as input and output data, including metadata, generated or cogenerated by the customer’s use of the service, excluding the provider’s protected assets.11 An audit trail of the customer’s actions on its own records is metadata generated by the customer’s use of the service. Even so, write it down. Name audit trails, signature records, and version history explicitly in the contract’s list of exportable data, and confirm that none of them appear in the provider’s list of internal data exempted for trade secret reasons. A provider that treats its audit trail tables as internal system data could, in theory, place them on that list. The contract should rule that out.

Formats That Keep Content and Meaning

A spreadsheet of field values with no definitions is an export, but it may not preserve content and meaning. FDA’s test is useful here: if you can search, sort, and trend records in the live system, the copies should allow the same where reasonable and technically feasible.8 The draft Annex 11 sets a similar bar for archived data.4 In practice, ask for three things:

  1. Structured data in an open, documented format, with a data dictionary that defines every table, field, code, and relationship. Proprietary database dumps that only the vendor’s software can read do not meet this need.
  2. Native files for attachments, with the identifiers that link each file to its record and version.
  3. Human readable renditions, such as PDF, for records that are signed or released, showing the signature manifestation required by Part 11. Renditions support review. They do not replace the structured data, because a PDF alone cannot be searched or trended at scale.

ISO/IEC 19941, the international standard on cloud interoperability and portability, gives a shared vocabulary for these discussions, separating data portability from application portability and describing the facets of each.16 It is a reference for terms, not a compliance requirement, but it helps when your IT, quality, and legal teams need to agree on what “portable” means.

Dynamic Records and Restorability

Some systems hold records that only make sense in their dynamic form. An EDC database with edit checks, queries, and derivations is one. EMA’s guideline addresses this for clinical trial databases, asking that archived formats allow restoration of dynamic functionality and metadata where possible, and that data and metadata remain available in dynamic data files where restoration is not possible.9 For these systems, decide at signing whether the exit plan is a restorable archive, a vendor-hosted read-only instance for the retention period, or a validated transformation into another system. Each has different contract terms.

Test the export before you sign. Ask the vendor to export a sandbox tenant seeded with realistic records: a document with three versions, an approved record with two signatures, a record changed after approval with a reason for change, and a few attachments. Load the export into a neutral tool. Check that you can find every version, read every audit trail entry, match every signature to the version it signed, and open every attachment. Count records on both sides. If the vendor cannot produce this in a sandbox before signing, it will not be easier at termination.

Transition Assistance, Timelines, and Fees

An export file is the end of an exit, not the whole of it. Between notice and deletion there is a sequence of work: confirming the data scope, running trial exports, verifying them, loading the destination, and keeping the source system available while all of that happens. The contract should say who does each part, how long it can take, and what it is charged.

Keep the Source System Running

The Data Act requires the provider to continue the service and maintain business continuity during the transitional period.11 For a GxP system, write that the service continues in its validated state, under the same change control, release, and security terms, until you confirm the switch is complete. A system that drops to a degraded support tier after notice creates validation questions you do not want during a migration.

Plan for a read-only access period as well. After cutover, quality and regulatory teams often need to look up records in the old system for months while the new archive or system is accepted. A read-only period, priced in advance, avoids negotiating an extension under time pressure.

Assistance You Can Count On

Data Act Article 25 requires reasonable assistance during switching.11 “Reasonable” is not a plan. The contract should list the assistance in concrete terms: named roles from the vendor (for example, a migration lead and a technical contact who knows the data model), response times for export questions, the number of trial exports included, support for reconciliation queries, and cooperation with your destination provider. The Data Act also places a duty of good faith cooperation on all parties to a switch, including the destination provider.

The Commission’s draft clauses offer a practical structure: a switching and exit plan attached to the contract, which names contacts, lists each data category with its metadata and format, sets the order and timing of exports, and requires a test export with part of the data before the full run.15 The draft clauses also note that self-service export tools for SaaS may not migrate some databases and setups properly or completely, which can require manual work by the provider. That is a reason to test the tools in advance and to keep the vendor’s obligation to help even where a self-service tool exists.

Timelines That Fit Validation

The Data Act’s 30-day transitional period is a maximum the provider must meet, not a limit on the customer. A validated migration of a large GxP system can take longer, because the verification required by Annex 11 clause 4.8 takes time. Use the customer’s right to extend the transitional period, and set out in the contract how the extension is requested. For contracts outside the EU, negotiate a transition period sized to your largest system, with the right to extend at the same rates.

The financial sector offers a model worth borrowing. The EU’s Digital Operational Resilience Act requires financial entities to have exit strategies for ICT services that support critical or important functions, with exit plans that are comprehensive, documented, and tested and reviewed periodically. It also requires contracts for those services to include a mandatory adequate transition period during which the provider keeps providing the service.17 DORA does not apply to pharma companies, but its structure fits GxP systems well.

Fees Fixed at Signing

Exit fees negotiated after notice are set by the party with more bargaining power, which is the vendor. Fix them at signing. In the EU, switching charges are limited until 12 January 2027 and prohibited after.11 Outside the EU, or for work the vendor argues is not part of switching, agree in writing which exit work is included in the subscription, which is billable, and at what rate. Include a cap. Cover the read-only access period, any long-term archive service, and the format conversion work for audit trails and signatures, because those are the items most often quoted separately.

1

Notice and Exit Decision

Give notice under the contract. Confirm the destination: a new system, your own archive, or a third-party archive. Freeze configuration changes in the source system.

2

Confirm the Data Scope

Walk through the exit schedule with the vendor. Confirm every data category, its metadata, and its format, and confirm nothing GxP-relevant is on the exempted list.

3

Trial Export and Reconciliation

Export part of the data. Load it into the destination. Reconcile record counts, versions, audit trail entries, and signatures. Fix gaps before the full run.

4

Full Export and Verification

Run the full export. Verify integrity with checksums where possible and documented checks where not. Record the results in a migration report.

5

Destination Acceptance

Accept the data in the destination under your own procedures, including retrieval tests that show records can be found, read, and printed with their signatures.

6

Read-Only Access Period

Keep read access to the source system for an agreed period so teams can resolve questions and spot-check records against the destination.

7

Deletion and Certificate

Instruct deletion only after acceptance. Receive a written deletion certificate covering production, backups, and subprocessors.

8

Final Review and Closure

Complete a final review of the retired system, file the exit records, and update the system inventory and retention records.

Retention After Termination and Certified Deletion

Two questions decide what happens after the export. Where will the records live for the rest of their retention period? And when, and how, will the vendor’s copies be destroyed? The contract should answer both, because the default answers in standard terms (the customer keeps whatever it downloaded, and the vendor deletes on its own schedule) rarely meet GxP needs.

Choosing Where Records Live After Exit

There are four common choices. Each is valid. The point is to choose one deliberately for each system and write the supporting terms into the contract.

OptionHow it worksStrengthsContract terms needed
Migrate to a new systemRecords move into the replacement system, with historyOne place to look; records stay usableExport completeness, trial exports, assistance, extension rights
Your own validated archiveRecords move to an archive the company controlsNo ongoing dependence on the old vendorFormats, data dictionary, renditions, verification support
Third-party archive serviceA specialist provider holds records for the retention periodBuilt for long retentionSame export terms, plus a new contract with its own exit clause
Vendor read-only archive tierThe old vendor keeps a read-only instance after the subscription endsRecords stay in their native form; useful for dynamic dataFixed long-term fees, validated state, inspection access, and an exit from the archive itself

The last option deserves care. A read-only archive tier keeps the company dependent on the same vendor for as long as the records must be kept, which may be decades. If you choose it, the archive contract needs its own exit clause, its own price protection, and the same insolvency terms as the main contract.

Deletion Only After Acceptance

The Data Act requires a contract clause guaranteeing full erasure of the customer’s exportable data after the retrieval period, provided switching was completed successfully. It also allows the parties to agree a later date.11 Use that flexibility. For GxP data, the contract should say that the vendor deletes only on the customer’s written instruction, given after the customer has accepted the export and the destination. A deletion deadline that starts automatically at termination can pass while a verification issue is still open.

Where the records include personal data, such as clinical trial participant data or employee training records, the GDPR adds its own rule. A processor must, at the controller’s choice, delete or return all personal data after the end of the services and delete existing copies, unless EU or member state law requires the data to be stored.18 GxP retention and data protection deletion can conflict. The contract should make clear that deletion by the vendor happens after return, and that the company, as the party with the retention duty, keeps the records it is legally required to keep.

What a Deletion Certificate Should Say

A one-line email saying “your data has been deleted” is not evidence you can file. The Commission’s draft clauses include a provider confirmation, within a set number of working days, that erasure has been completed, with an exception for personal data the provider must keep by law.15 Build on that. A useful deletion certificate states:

  • The tenant, environment, and data categories deleted, matched to the exit schedule
  • Each location covered: production, sandboxes and test copies, replicas, backups, logs, and any subprocessor systems
  • The method of deletion and the date it was completed
  • For backups that are not deleted immediately, the date by which they expire under the normal rotation, and confirmation that they are protected until then
  • Anything retained, with the legal basis and the planned deletion date
  • The name and role of the person signing for the vendor

File the certificate with the system retirement records. It closes the record of where the data went.

Legal holds and inspections. Before instructing deletion, check for open legal holds, pending regulatory questions, and ongoing investigations that touch the system. The contract should let you pause deletion for those reasons without penalty, and should require the vendor to preserve the data until you lift the pause.

When the Vendor Is Sold, Fails, or Ends the Product

Planned exits are the easy case. The harder cases are the ones the company does not choose. The life sciences software market sees regular acquisitions, and acquisitions often lead to product consolidation. Smaller vendors, including some with strong GxP products, can fail. Each event needs its own terms, written before signing.

Acquisition and Change of Control

When a vendor is acquired, the contract usually passes to the new owner, and the new owner’s product strategy may differ from the one you bought into. The Commission’s draft termination clauses recognize change of ownership or control as an event that may, by contract or by law, lead to termination, and they address what happens to switching and erasure rights in that case.15 For a GxP buyer, the useful terms are:

  • Notice of change of control within a set period after it happens.
  • Assumption of obligations. Any assignment of the contract requires the new party to assume all obligations, including the exit, quality agreement, and audit terms.
  • A right to exit without penalty for a period after a change of control, with exit assistance at the agreed rates and no early termination fee.
  • No change to data location or subprocessors without the notice and approval terms already in the contract.

Product Retirement

An acquirer that retires a product rarely breaches the contract by doing so. It simply declines to renew. Protect against this with an end-of-life clause: a minimum notice period before the product is withdrawn, long enough to select, validate, and migrate to a replacement, plus a commitment to keep the product supported and in its validated state until the end of that period. Tie the exit assistance and fee terms to retirement as well as to termination, so that a non-renewal triggers the same help as a termination.

Bankruptcy

Bankruptcy is the case where contract terms are weakest, because a failing vendor may not have the people or money to perform them. For contracts governed by US law, Section 365(n) of the Bankruptcy Code lets a licensee of intellectual property keep its rights under the license if the bankrupt licensor rejects the contract, but it excludes rights to specific performance beyond exclusivity.19 A Mayer Brown analysis notes that the protection covers only certain types of intellectual property, not service arrangements, and recommends making the agreement expressly subject to Section 365(n), stating renewal rights clearly, allocating payments between licensed rights and services, and considering an escrow of tangible embodiments such as source code.20

For a SaaS customer, the limits are plain. What you need when a vendor fails is your data and, for a while, a working system. A license to software you cannot run, on infrastructure you do not control, does not give you either. EMA’s expectation that agreements ensure continued access to data in case of bankruptcy or shutdown is a requirement about outcome, not about legal form.9

Escrow for SaaS

Traditional source code escrow was designed for installed software. A Lewis Silkin overview explains why it fits SaaS poorly: some providers will not agree to it, SaaS depends on a mix of source code, object code, third-party integrations, and specific hardware configurations, and traditional escrow usually does not cover data. It also notes that escrow agreements typically deal with release triggers but not ongoing use.21

SaaS escrow arrangements that include data, hosting environment details, and continuity support exist, and for a critical system with a small vendor they may be worth the fee. If you use one, define the release triggers objectively (for example, insolvency events or a sustained failure to provide support), require regular deposits, and pay for verification that the deposit is complete and usable.

The Best Protection: A Current Copy You Control

The most dependable protection against vendor failure is not legal. It is a recent, complete, verified copy of your data held outside the vendor’s environment. Negotiate a right to scheduled full exports during the term, in the same format and with the same completeness as the exit export, at no extra charge or at a fixed fee. Run them on a schedule set by the system’s risk, store them in your own controlled environment, and test that they can be read. If the vendor fails with two weeks’ notice, as happened to Nirvanix customers, you start from a recent verified copy rather than a rushed download.3

A practical rule. If a system holds records you would need to produce in an inspection, you should be able to produce them without the vendor’s help, from a copy no older than the period your risk assessment allows. Scheduled exports make that possible. Everything else in the exit clause is about doing it well.

Building the Exit Schedule: A Clause Checklist

The terms above fit best in a single exit schedule attached to the master agreement, cross-referenced from the quality agreement. One schedule is easier to review, easier to update at renewal, and easier to show an inspector than terms spread across an order form, a data processing agreement, and a support policy. The Data Act’s requirement for an exhaustive specification of exportable data gives EU buyers a ready reason to ask for one.

Clause 1

Exportable Data

Named list of record types, versions, audit trails, signatures, configuration, user history, and logs. Confirm none are on the vendor’s exempted list.

Clause 2

Formats and Documentation

Open structured formats with a data dictionary, native attachments with identifiers, and human readable renditions of signed records.

Clause 3

Scheduled Exports During the Term

A right to full exports on a set schedule, with the same completeness as the exit export, at a fixed price.

Clause 4

Transition and Assistance

Service continues in its validated state; named vendor roles; trial exports included; extension rights; cooperation with the destination provider.

Clause 5

Fees

Exit work included in the subscription or billed at fixed rates with a cap; Data Act charge limits recognized; read-only access period priced.

Clause 6

Retention and Deletion

Post-exit location chosen; deletion only on written instruction after acceptance; deletion certificate covering backups and subprocessors; legal hold pause.

Clause 7

Change of Control and Retirement

Notice of change of control; assumption of obligations; penalty-free exit window; minimum end-of-life notice with continued validated support.

Clause 8

Insolvency and Continuity

Exit rights survive termination for insolvency; express Section 365(n) language where US law applies; escrow where risk justifies it.

Questions to Ask Before Signing

Use these questions in vendor selection, and record the answers in the supplier assessment:

  1. Show us the export of a seeded sandbox tenant, including audit trails and signatures. Which data does your export not include?
  2. Where is your Data Act register of data structures and formats, and which data do you list as internal and exempt?
  3. How long did your three largest customer exits take, and what help did you provide? (Ask for the process, not customer names.)
  4. Do you offer a read-only archive tier, and at what long-term price?
  5. What does your deletion certificate contain, and how long do backups persist after deletion?
  6. What are your commitments if the product is retired or the company is acquired?
  7. Will you support scheduled full exports during the term, and in what format?

Keep the Exit Plan Current

An exit schedule written at signing goes out of date as the system grows, new modules are added, and the vendor changes its data model. Review it during periodic review of the system. The draft Annex 11 lists contracts and key performance indicators with vendors and service providers among the items a periodic review should cover, and says a final review should be conducted when a system is taken out of use.4 A periodic review that includes a scheduled export test checks the exit plan in the same step.

Renewal is the second chance. If the original contract did not include these terms, renewal is when you have the most bargaining power to add them. Start the conversation well before the renewal date, so that the exit schedule is part of the renewal and not an afterthought to it.

Who Owns the Exit Clause

Exit clauses fall between functions. Procurement owns the contract, legal owns the wording, IT owns the technical export, and quality owns the record obligations. When everyone owns a part, nobody checks the whole. Assign one owner for each GxP SaaS exit schedule, usually the system owner with quality support, and make the exit schedule a required input to contract approval for any system that holds GxP records. A short review by quality before signature, using the checklist above, is far less work than an unplanned migration with gaps in the audit trail.

Conclusion

A GxP SaaS exit clause is a retention control written in contract language. The regulations are consistent about the outcome: complete records, with metadata, audit trails, and signatures, readable and available for as long as the retention period runs, whatever happens to the vendor. The EU Data Act now sets a useful minimum for cloud contracts in the EU, with capped notice periods, defined transition and retrieval periods, an exhaustive list of exportable data, and the end of switching charges from 12 January 2027. It does not provide decades of access or define what a complete GxP export looks like. That part is still the buyer’s job.

The companies that handle exits well settle the exit at signing. They name the data, test the export, fix the fees, decide where records will live afterward, write deletion around their own acceptance, and keep a current copy of their records in their own hands. Sakara Digital works with pharma and biotech organizations on GxP system selection, supplier oversight, and data integrity. If you are negotiating or renewing a SaaS agreement for a system that holds GxP records and want an independent view of its exit terms, we are happy to have that conversation.

For Further Reading