Maintenance and Support Agreement in France: Template and Key Clauses (2026)

A maintenance and support agreement in France, often called a contrat de maintenance et de support, sets out how a supplier keeps a product, software or equipment running after it is delivered. The commercial heart of the deal is the service level: uptime, how fast the supplier responds, how fast it resolves, and what happens when it misses. The legal heart is a single French-law question, whether the supplier owes an obligation de moyens or an obligation de resultat. Get both right and the contract works. This is general information, not legal advice; confirm a live deal with a French lawyer. ## What law governs a maintenance and support agreement in France? There is no single statute for maintenance contracts. They are ordinary service contracts governed by the general law of obligations in the Code civil, reformed in 2016, together with the commercial rules in the Code de commerce where the parties are businesses. If the supplier processes personal data on the customer's behalf, the RGPD (the French name for the GDPR) and the Loi Informatique et Libertes apply, and the CNIL is the supervisory authority. French value added tax, the TVA, applies to the fees, so the contract should state whether prices are hors taxes or toutes taxes comprises. ## Obligation de moyens or obligation de resultat French law draws a sharp line between two kinds of promise, and a maintenance contract should say which one it is making. - An obligation de moyens is a duty to use reasonable skill and care, the diligence of a competent professional. The customer who complains must prove the supplier fell short. Most support promises (best efforts to fix, to advise, to maintain) are obligations de moyens.

• An obligation de resultat is a duty to deliver a defined outcome. If the outcome is not met, the supplier is liable unless it proves an outside cause (force majeure). A firm uptime figure or a guaranteed resolution time can create an obligation de resultat. Name the standard for each promise. A supplier should resist turning a target response time into a guaranteed result unless it is willing to carry that risk. ## Service levels, response and resolution The SLA is the operating core. Draft it with care. - Uptime or availability, stated as a percentage over a measured period, with the method of measurement and the exclusions (planned maintenance, customer-caused outages, force majeure).
• Incident severity levels, usually critical, major and minor, each with a plain definition.
• Response time, how fast the supplier acknowledges a ticket, by severity.
• Resolution time or a target for a workaround, by severity. Decide whether these are obligations de moyens or de resultat.
• Support hours and channels, business hours or 24x7, and the languages of support.
• Support tiers, for example a basic, standard and premium plan, with what each includes. ## Service credits and remedies If the supplier misses the agreed levels, the usual remedy is a service credit, a reduction of the fee. Set out the credit schedule, how it is calculated and claimed, and whether credits are the customer's sole remedy for a missed level or sit alongside termination rights for persistent failure. Under French law a penalty-style figure (clause penale) can be reviewed by a judge if it is manifestly excessive or derisory, so keep credits proportionate and framed as a price adjustment. ## End of life, versions and spare parts For software, say which versions are supported, how long after a release, and the notice before a version reaches end of life (EOL). For hardware, address spare-part availability and lead times. A clear EOL and version-support policy prevents the common dispute where a customer expects indefinite support for an old release. ## Data protection, RGPD and CNIL If support involves access to systems holding personal data, the supplier is usually a processor (sous-traitant) acting on the customer's instructions. The RGPD requires a written data processing agreement with the mandatory content: subject matter, duration, nature and purpose, types of data, security measures, sub-processing rules, assistance with data subject rights, and deletion or return of data at the end. Name the CNIL as the French authority and address where data is hosted and whether any transfer leaves the EU. ## Other key clauses - Scope, exactly what is maintained and supported, and what is excluded (new development, training, third-party products).
• Fees and TVA, the annual or monthly charge, indexation, and tax treatment.
• Term and renewal, often one year with tacit renewal; note French consumer rules on tacit renewal do not bind business-to-business deals in the same way, but state the position clearly.
• Liability, a cap and exclusions, drafted so it is not struck down for defeating an essential obligation.
• Intellectual property, confirming the customer's licence continues and the supplier keeps its tools.
• Reversibility, handing back data and documentation on exit so another supplier can take over.
• Governing law and jurisdiction, French law and a named court or arbitration. ## A simple drafting skeleton 1. Parties and date

2. Definitions (incident, severity, availability, support tier)
3. Scope of maintenance and support
4. Service levels (uptime, response, resolution)
5. Standard of each obligation (moyens or resultat)
6. Service credits and remedies
7. Support tiers, hours and channels
8. Versions, updates and end of life
9. Fees, indexation and TVA
10. Data protection (RGPD processor terms)
11. Liability and cap
12. Term, renewal and termination
13. Reversibility and exit assistance
14. Governing law and jurisdiction (France)
15. Signatures ## Keeping maintenance contracts under control The hard part of a support portfolio is rarely one contract. It is tracking which SLA applies to which customer, when each renewal falls, which service-credit schedule is in force and whether each deal carries an obligation de moyens or de resultat. That work, drafting from a tuned template, flagging risky clauses, tracking renewals and keeping versions straight, is what an AI contract workspace can hold in one place. Adira is built for this, with per-clause risk review, plain-English clause editing and a live activity timeline; it is India-first today with other jurisdictions on its roadmap, so verify local depth before relying on it for French law. More at Adira. The law above stands on its own. ## Bottom line A French maintenance and support agreement turns on two things: a precise SLA with credits that bite, and a clear choice between obligation de moyens and obligation de resultat for every promise. Draft the service levels, the remedies and the RGPD processor terms with care, state the TVA position, and get French advice before signing a real deal.