How to exit an IT contract: an overview of termination options
SaaS, IT, hosting, integration: an overview of how to terminate an IT contract under French law, and the right reflexes to have
Clients usually reach out to me when the contractual relationship is deteriorating, when a strategic shift forces them to exit, or when the provider has become a friction point they want to remove.
At that stage, the first question is almost always the same: can I get out? And if so, how?
This article walks through the different ways to terminate an IT contract under French law, whether it's a SaaS subscription, an integration project, a hosting contract, a maintenance agreement, or a development contract.
This is the step clients overlook most often. Before reaching for a statutory ground, you need to know what was actually signed.
Most IT contracts include specific termination provisions: initial term, automatic renewal, notice period, termination clauses, and specific early-exit cases. These contractual provisions are your first reading grid. If a clause grants you a clear right to terminate, you don't need to dig for a more complex legal basis.
Check the term as well. A contract for an indefinite term can in principle be terminated at any time with reasonable notice. A fixed-term contract, on the other hand, cannot be unilaterally terminated before its end date without a specific legal basis.
Once that review is done, you can identify the most appropriate path among those that follow.
Termination for convenience allows the client to end the contract without having to prove any breach by the provider. It is a contractual right, not a general statutory right.
It is more common in IT services contracts (development, integration, consulting) than in SaaS contracts, where it is often absent or heavily restricted. When it does exist, it generally comes with conditions:
An important point: in the absence of a termination-for-convenience clause in a fixed-term contract, you have no general right to exit before the end date. Many clients believe they can terminate "with notice" as they would under an indefinite-term contract. That is not the case.
On the provider side, I almost always recommend excluding this right entirely, since it negatively affects contract value.
The Data Act has significantly shifted the contractual balance for a specific category of contracts: data processing services, which essentially cover SaaS, IaaS, PaaS, and similar cloud services.
For these contracts, the European regulation creates a specific termination right allowing the client to switch providers or bring the service in-house, with a maximum notice period of two months. This right applies even to contracts entered into before 12 September 2025, which makes it a powerful lever.
Important: this right does not cover IT contracts in general. An integration contract, a development contract, a pure maintenance agreement, or a consulting engagement is not covered by the Data Act. Don't try to invoke it for these contracts: it simply doesn't apply.
I've written a full guide on this topic: terminating a SaaS contract under the Data Act. For an audit of your situation as a client, you can also check out the dedicated page.
This is the most contested and litigated ground. When the provider fails to meet its commitments, the client can, under certain conditions, end the contract.
Article 1224 of the French Civil Code provides three routes for termination on grounds of non-performance:
The central criterion is the seriousness of the breach. A one-off delay, an isolated mistake, or a marginal SLA shortfall generally won't suffice. The breach must make continuing the contract unreasonable for the client.
In practice, in IT contracts, breaches that justify termination for fault typically include:
For development contracts specifically, I've laid out the key contractual best practices in this article on software development contracts.
Unilateral termination is risky. If the court later decides the breach was not serious enough, the client ends up being the party at fault for ending the contract. It is far better to thoroughly document breaches and escalations before sending the termination notice.
Beyond the three main routes, IT contracts often contain specific termination triggers. They are sometimes very useful and largely underused by clients.
Change of control of the provider. This clause lets the client terminate if the provider is acquired or comes under the control of a third party. It is valuable when the provider is bought by a direct competitor of the client, or when the acquisition materially changes the nature of the service. Check the precise definition of "change of control": ownership threshold, economic versus capital control, possible exclusions.
Assignment of the contract. Contracts frequently provide that the provider cannot assign its rights and obligations without the client's consent. In case of an unauthorised assignment, the client can generally terminate.
Insolvency proceedings. The French Commercial Code strictly governs the fate of ongoing contracts when the provider enters safeguard, judicial reorganisation, or liquidation proceedings. Termination is not automatic: the court-appointed administrator decides whether to continue the contract. The client generally has limited room to terminate on its own initiative during this period, except for unequivocal payment default or non-performance.
Prolonged force majeure. Brief force majeure events generally don't justify termination. But if the event extends beyond a certain duration (often set contractually, for example 30 or 60 days), the contract usually allows either party to terminate.
Compliance and ethics clauses. More and more contracts provide a termination right in case of non-compliance with regulatory or ethical obligations (international sanctions, anti-corruption, ESG, serious ethical misconduct). These clauses must be handled with care: any trigger must be justified and documented.
Once the legal basis is chosen, execution matters as much as the decision itself.
The form prescribed by the contract takes precedence. Many contracts impose a specific form for termination notices: registered letter with acknowledgement of receipt to a specific address, notification through a contractual platform, dual notification (legal and operational), or specific formalities for certain grounds. If the contract requires a particular form, that form is binding. A termination notice sent by simple email when the contract requires a registered letter can be challenged — and may be deemed unenforceable.
Where the contract is silent. Absent a contractual requirement, a registered letter with acknowledgement of receipt remains the safest route. It establishes the date of receipt and the content of the notice. An email with a read receipt may suffice for a low-stakes contract, but offers weaker evidentiary value.
Content of the notice. A termination notice should include at a minimum: identification of the contract concerned, the ground and legal basis invoked (contractual clause, Article 1226 of the Civil Code, Data Act, etc.), the requested effective date, and the proposed transition terms. If termination is based on breach, attach the prior formal notice and list the specific breaches found.
Prepare the migration before sending the notice. This is a classic mistake: sending the termination notice and only then realising no exit plan was prepared. You then end up in a weak position, having to negotiate reversibility and exit terms under pressure that you could have secured calmly upstream.
Before sending the notice, identify:
A termination, even a well-founded one, can lead to a dispute. A few precautions significantly reduce that risk.
Document everything. Breaches identified, escalations, exchanges, commitments made by the provider. If a dispute arises later, this documentation is what makes the difference.
Reserve your rights in the notice. Wording such as "the client expressly reserves all its rights, including in respect of damages suffered as a result of the provider's breaches" prevents silence from being construed as a waiver.
Manage operational communication carefully. A termination handled abruptly can turn a manageable transition into a stand-off. A provider that feels mistreated can drag its feet on data portability, refuse accommodations, or contest the grounds. A firm but professional tone, combined with a clear transition plan, generally speeds up the exit.
Many clients arrive thinking they have only one exit option, when in fact several are available. Choosing the right legal basis is no small matter: depending on the route, the cost, the timeline, and the litigation exposure vary considerably.
A termination for convenience with a fee may be expensive but avoids litigation. A termination for breach removes the fee but exposes the client to litigation if the seriousness of the breach is contested. A termination under the Data Act, when applicable, is often the fastest and least costly route — but it only covers data processing services.
If you're preparing to exit an IT contract or want to assess your options before sending notice, let's set up a call to review your situation.
The Data Act limits what SaaS vendors can charge when you switch providers. Permitted fees, prohibited charges, and the 2027 deadline explained.
Stuck in a SaaS contract your company no longer needs? The EU Data Act gives you a legal right to switch providers. Eligibility, process, and pitfalls.
Let's build together to grow your business
I have been supporting software and SaaS companies for over 10 years, helping them structure their business, protect their intellectual property and strengthen their contracts.
