Every external engineering engagement ends, whether because the work moves in-house, the product changes direction, or the provider is replaced. How it ends is decided long before, at the moment the contract is signed. Without an exit plan, the client discovers during the notice period that obligations to support a handover were never agreed, that access is scattered across accounts, and that personal data still sits in places nobody has listed. With an exit plan, the transition is a scheduled project with defined deliverables. This guide explains the relevant termination rules under German law, the clauses an exit plan should contain, and a handover sequence that can be run in practice.
The numbers: why exit risk is real
Dependency on external technology and capacity is the norm in German industry, not the exception. In a 2025 study on digital sovereignty, Bitkom found that 96% of companies in Germany source digital technologies or services from abroad, and 90% of those say they cannot do without them. Bringing work back in-house is slow: Bitkom's 2025 survey of 855 companies put the average time to fill an IT vacancy at 7.7 months, and its 2026 study still counted around 79,000 unfilled IT positions. The long-term outlook is tighter, not looser. The IW Köln projected in 2026 that Germany will be short of 4.3 million workers by 2036 as the baby boom cohorts retire. An exit that depends on hiring a replacement team in a hurry is therefore an exit that will probably fail.
Termination rights: the statutory baseline
The applicable rules depend on the contract type, and framework agreements usually modify them. It still helps to know the statutory baseline.
- Werkvertrag: under BGB §648, the client may terminate at any time until the work is completed. The contractor is then generally entitled to the agreed remuneration, less saved expenses and earnings from alternative use of its capacity. The statute presumes that the contractor is entitled to 5 percent of the remuneration attributable to the part of the work not yet performed. Both parties may terminate for good cause without notice under BGB §648a.
- Dienstvertrag: where no fixed term applies, ordinary notice periods follow BGB §621 for service contracts that are not employment relationships, depending on how the remuneration is calculated. Extraordinary termination for good cause is governed by BGB §626.
In practice, most framework agreements define their own notice periods, often combined with a sprint- or month-based rhythm. What the statute does not provide is any obligation of the provider to actively support a transition to a successor. That has to be agreed.
The exit clause: what it should contain
- Transition period. A defined period after notice during which the provider continues delivery at reduced scope and supports the handover, with the applicable fee.
- Transition obligations. An explicit duty to cooperate in the handover to the client or a successor: knowledge transfer sessions, answering questions, joint work on selected items.
- Handover deliverables. A list of what must be delivered, referenced in an annex and kept current during the engagement (see below).
- Rights of use. Confirmation that the rights of use granted during the engagement survive termination and cover all work delivered up to the end, including work in progress.
- Return and deletion of data. In line with Art. 28 Abs. 3 lit. g DSGVO, the processor deletes or returns all personal data after the end of the services, at the controller's choice, unless storage is legally required, with written confirmation.
- Access revocation. All access rights are revoked on a defined date, and all secrets the provider had access to are rotated.
- No hostage situations. No retention of code, documentation or data as leverage in a payment dispute; disputes are handled separately.
Handover deliverables
The handover list should be defined at the start and maintained throughout, so that the exit does not become a documentation project under time pressure.
| Deliverable | Content | Verification |
|---|---|---|
| Source code and history | All repositories in client-owned accounts, complete history, no local-only branches | Repository inventory checked against the provider's list |
| Build and deployment | Pipelines, infrastructure as code, environment configuration | Client engineer performs a full build and deployment unaided |
| Documentation | System map, ADRs, runbooks, onboarding guide, interface documentation | Successor or client engineer follows onboarding guide without help |
| Open work | Backlog with status, work in progress on branches, known defects, open risks | Joint review session |
| Operations knowledge | Recurring incidents, monitoring and alerting setup, maintenance tasks | Walkthrough with recorded session |
| Third-party inventory | Dependencies, licences, external services, API keys in use | List checked against configuration |
| Data confirmation | Written confirmation of return or deletion of personal data | Signed statement |
A handover sequence
Illustrative timing for a mid-sized engagement; adjust it to the complexity of your system.
- Weeks 1 to 2: inventory. The provider updates the handover list and identifies gaps. The client names the receiving team and a handover lead.
- Weeks 2 to 4: knowledge transfer. Structured sessions per area, recorded and stored with the documentation. The receiving team asks questions in writing so answers are retained.
- Weeks 3 to 6: shadowing and reverse shadowing. First the receiving team observes the provider's work, then the receiving team does the work while the provider observes and corrects.
- Final week: verification and closure. Client engineers perform an unaided build, deployment and runbook exercise. Remaining gaps are closed or documented. Access is revoked, secrets are rotated, data confirmation is issued.
Plan the delivery scope of the transition period realistically. A team that is handing over cannot deliver at full pace at the same time, and the sprint Leistungsbeschreibungen in this phase should reflect that.
Preparing for exit from day one
The most effective exit preparation is the normal operating discipline of a well-run engagement: client-owned accounts, documentation in the Definition of Done, individual named access, and knowledge spread across more than one person. If these hold throughout, the exit is mainly a matter of verification and orderly closure. If they do not, no exit clause can fully compensate.
A useful annual check: ask what would happen if the engagement ended with three months' notice tomorrow. If the honest answer involves unknown accounts, missing runbooks or a single person who knows the deployment, fix that now rather than during the notice period.
Why a good provider wants this clause
A clear exit clause is sometimes seen as a sign of distrust. It is the opposite: it lowers the client's perceived risk, which makes it easier to start an engagement in the first place. A provider that is confident in its delivery has no reason to rely on switching costs. Ask every provider for the transition clause and the handover list in the framework discussion, before the first sprint starts.
This article is general information and does not constitute legal advice.
An exit plan written on day one is the cheapest insurance an external engagement can carry. niogod™ engagements run under a Werkvertrag or Dienstvertrag with a Leistungsbeschreibung and documented Abnahme for every sprint, so much of the record a handover needs is produced in normal delivery. If a transition clause is on your list for the next vendor discussion, it is a conversation worth having early.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation