Exit clauses: how to leave without losing everything
The clauses that decide what happens when you end a web or software relationship, what a fair exit contains, and the terms that trap.
The short answer
Every web and software relationship ends one day, well or badly, and the exit clause decides which. It defines the notice period in each direction, what is handed over, in what form, by when, at what cost, and what happens to accounts, data and access. A fair exit is short notice either way, hand-over of code, data, documentation and accounts included in the price, and cooperation with the successor for a defined period. The trap terms are long lock-ins with auto-renewal, hand-over charged separately or left undefined, accounts and domains in the supplier’s name, and ownership contingent on final settlement. The best exit clause is one you never need, because everything was in your name and documented from the start; the clause is the backstop for when it was not. Have an advisor review the wording for your jurisdiction; the substance below is what to insist on.
What a fair exit clause contains
| Element | Fair | Trap |
|---|---|---|
| Notice | One to three months, either direction | Twelve months; auto-renewal; notice only in a window |
| Hand-over scope | Code with history, documentation, data exports, accounts, service list | Undefined, or “reasonable assistance” |
| Hand-over form | Repository transferred; documents; credentials in your manager; exports in open formats | A zip file; a call |
| Hand-over timing | Completed within the notice period | After final payment; when convenient |
| Hand-over cost | Included | Charged hourly, uncapped |
| Accounts and domains | Already in your name; confirmed at exit | In the supplier’s name; transfer at their discretion |
| Ownership | Passes per milestone for work paid | Contingent on final settlement |
| Successor cooperation | Defined period of questions answered | None |
| Data | Exported and then deleted by the supplier, confirmed | Retained indefinitely or unclear |
Negotiating it at signing
- Put everything in your name from day one: domain, hosting, repository, services. The exit clause then has little to transfer.
- Define the hand-over scope and form as a list in the contract.
- Set notice at one to three months in both directions, with hand-over inside it.
- State that hand-over is included in the fees, with a cap on any extra if a cap is unavoidable.
- Make ownership pass per milestone for work paid.
- Add successor cooperation for a defined period.
- Require data deletion confirmation after export.
Using it well
Give notice in writing as the clause requires. List the hand-over items and dates from the contract and track them. Keep the relationship professional; the successor will need answers. Confirm accounts, verify the repository and documentation with the successor, export and check the data, and get deletion confirmed. A fair clause makes this a checklist; a poor one makes it a negotiation you enter with less power than you had at signing.
What this means for you
Negotiate the exit at signing: short notice either way, a defined and included hand-over, ownership per milestone, accounts already yours, successor cooperation and data deletion confirmed. Put everything in your name from the start so the clause is rarely needed. A relationship you can leave cleanly is one both sides keep earning, which is the outcome the clause exists to protect.
Frequently asked questions
What should the hand-over include?
The repository with full history, transferred to your account; documentation that a successor can work from; credentials and accounts moved to your control or confirmed there; data exports in usable formats; a list of third-party services and their status; and cooperation with the successor for a defined period, all included in the agreement rather than charged as an extra.
How much notice is reasonable?
One to three months in either direction for ongoing maintenance and support, with the hand-over completed within that period. Twelve-month terms with auto-renewal and long notice exist to make leaving painful. A supplier confident in their work does not need them, and their presence is information.
The contract says the supplier owns the code until final payment. Is that a problem?
It can be: a dispute over a final invoice leaves you without rights to something you have mostly paid for. Prefer ownership passing per milestone for work paid, and a clause that a disputed final invoice does not withhold hand-over of paid work. Have an advisor review; the wording matters.