Terminating a SaaS agreement: notice, refunds and clauses to include

The European Data Act, applicable since September 2025, transforms SaaS contract termination: you can switch cloud providers within a maximum of 2 months, without contractual obstacles or abusive fees. You still need to manage notice, potential refunds and the clauses required to secure exit and data migration.

1) Terminating a SaaS agreement in 2026: the new framework

The Data Act (EU) 2023/2854 imposes switching obligations for data processing services (IaaS, PaaS, SaaS): no technical or legal barriers, facilitated portability, and a maximum period of 2 months to switch from the request, unless complexity is duly justified by the parties (Chapter VI, art. 23 to 31, EUR-Lex).

• When the Data Act applies: cloud/SaaS service, customer located in the EEA, planned switching to another provider or insourcing (self-hosting).
• What changes: clauses requiring longer notice or disproportionate exit fees are unenforceable against the customer in this context (EUR-Lex, Chapter VI).
• What the Data Act does not regulate: compensation outside switching, commercial refund arrangements or termination for breach, which remain governed by general law and the contract.

For a SaaS-focused operational summary, also see: terminating a SaaS agreement using the Data Act and early termination of a SaaS agreement.

2) Termination notice: duration and practical cases

2.1 Indefinite-term contracts

Under French law, either party may terminate an indefinite-term contract at any time, subject to reasonable notice and good faith (Civil Code, art. 1211). In B2B SaaS practice: 30 to 60 days depending on the solution's scope and data volume.

2.2 Fixed-term contracts (firm commitment)

Except for serious breach or specific provisions, early termination of a fixed-term contract may incur exit fees (e.g. withdrawal compensation). However, for switching within the Data Act, the provider must allow exit within a maximum of 2 months and cannot impose contractual constraints contradicting that period (EUR-Lex, Chapter VI). Migration and egress fees are regulated: only direct, reasonable costs may be charged, with a trajectory towards free switching established by the Regulation.

2.3 Automatic renewal: information and termination

In B2C, advance information about automatic renewal is regulated (the “Chatel law”), under DGCCRF supervision (économie.gouv.fr — Automatic renewal; Service-Public). In B2B, the contract and general law primarily apply; prudence calls for a clear termination window before renewal (see Service-Public Pro).

3) Refunds, fees and penalties: who pays what?

• No automatic refund of prepaid periods in B2B: it all depends on the contract. Unless stipulated otherwise, amounts already due remain payable. For termination due to provider breach, termination may entail restitution (pro rata) according to the contract's structure (Civil Code, art. 1229).
• Switching fees: the Data Act strictly regulates technical portability/migration charges and prohibits contractual obstacles to exit (EUR-Lex, Chapter VI). Egress fees must reflect direct costs and be transparent.
• Penalty/withdrawal clauses: they must be proportionate, otherwise a judge may revise them (Civil Code, art. 1231-5).

To address these matters before signing, see our recommendations on points to check in a B2B SaaS agreement and a SaaS licence agreement.

4) Termination for serious breach: method and evidence

For repeated breaches (unmet SLA, prolonged outages, GDPR non-compliance), you may serve formal notice on the provider and, if non-performance persists, unilaterally terminate the contract (Civil Code, art. 1226). Document incidents (logs, tickets, screenshots, SLA metrics).

• SLA: specify availability commitments, service credits, outage thresholds and exit rights for repeated breaches. See our SLA: obligations and drafting guide.
• GDPR/DPA: as controller, you must regulate the processor (art. 28 GDPR). The CNIL outlines mandatory clauses (security, subprocessors, audit, return/deletion). Also consult our DPA guide for SaaS.

In litigation practice, formalise a clear, traceable notice (registered letter with acknowledgement/timestamped email). Useful guidance is available on justice.fr and in our commercial contract termination article.

5) Clauses to include (buyers and providers)

• Termination for convenience: possible at any time with notice ≤ 60 days where the customer chooses switching under the Data Act (and 30–60 days for standard indefinite-term contracts).
• Exit assistance/portability: open formats (CSV/JSON/Parquet), schemas, automated exports/APIs, log transfer, milestone schedule, integrity validation, reasonable provider assistance.
• Deletion/archiving: purge after exit assistance, with data return and certified deletion, subject to statutory retention obligations (see CNIL, security and minimisation).
• Exit fees: transparent, limited to direct costs and Data Act-compliant; no deterrent egress fees.
• SLA/credits: recurring outages = penalty-free exit right beyond a threshold (e.g. 3 months below SLA).
• Limitation of liability: calibrated (data, unavailability, business interruption) and coordinated with security obligations.

These points complement the key SaaS agreement checks and SaaS licence agreement points to watch.

6) Exit procedure: the 8-step checklist

1. Check Data Act eligibility: cloud/SaaS service, EEA customer, planned switching/insourcing (EUR-Lex, Chapter VI).
2. Review the contract: termination, renewal, exit assistance, SLA, fees, DPA.
3. Notify in writing (registered letter/email): Data Act basis, 60-day timetable, portability and assistance requirements.
4. Organise migration: batch extraction, schema mapping, ETL tools, integrity checks (hashes, counts).
5. Freeze production changes on the provider side (code freeze) during switchover.
6. Test in staging with the new provider, validate functional parity.
7. Switch over: cutover window, rollback plan, user communications.
8. Close out: deletion certificate, access revocation, compliant final billing (direct costs only).

7) Common pitfalls and warning signs

• Notice > 2 months for a switching-related exit: non-compliant with the Data Act, unenforceable.
• Disproportionate egress/migration charges (deterrent pricing, proprietary lock-in): beware of unfair-clause risk under the Data Act.
• Undocumented data (opaque schemas): require export specifications.
• Unlisted subprocessor chains: update the DPA (CNIL, art. 28 GDPR).

8) Brief notification template (adapt as needed)

Subject: Notice of termination and switching request (Data Act — 60-day period)
Dear Sir or Madam,
Under Chapter VI of the Data Act (EU) 2023/2854 and the contractual provisions, we notify you of our decision to terminate for convenience to switch to another provider. The attached migration timetable provides for a complete switchover within 60 days of this notice.
Please arrange portability of all our data (open formats + logs) and provide duly substantiated details of your related direct and reasonable costs.
After migration, we will request a certificate of deletion of our data, subject to statutory retention obligations.
Yours faithfully,

Quick FAQ

Does the Data Act apply to B2B SaaS?
Yes, where the service is a “data processing service”. It requires exit within a maximum of 2 months and regulates fees (EUR-Lex, Chapter VI).

Is a pro rata refund automatic?
Not in B2B: it depends on the contract. For provider breach, general termination law may allow restitution (Civil Code).

How should data deletion be managed?
Provide for return + certified deletion and GDPR/DPA compliance (see CNIL).

To frame the entire contractual lifecycle, supplement this with our content on SLAs, the GDPR DPA, and the commercial termination procedure.

Official resources: EUR-Lex — Data Act; Civil Code (Legifrance); CNIL; DGCCRF — Automatic renewal; Service-Public (automatic renewal); Service-Public Pro.