- 01
Market
Saudi Arabia
- 02
Written for
CIO, Procurement
- 03
Decision
Plan an orderly vendor exit, or negotiate contract terms that make one possible later
- 04
Languages
EN · AR
The sequence
The sequence an orderly vendor exit follows
The order is deliberate: artefacts are verified while the vendor is still cooperative and paid, knowledge moves while its holders are still present, and nothing is switched until the successor has run beside the incumbent.
A five-step exit flow — verify escrow and artefacts, run knowledge transfer, hand over credentials, untangle licences, cut over from a parallel run — with a fallback branch that extends the parallel run if the successor is not ready.
- 01
Verify the escrow and artefacts
Confirm the code, data exports, build instructions and documentation are current and complete — by building and restoring from them, not by reading a manifest.
- 02
Run knowledge-transfer sessions
Structured sessions where the receiving team performs deployments, fixes and operational tasks under the incumbent's guidance, with recordings and written runbooks as the output.
- 03
Hand over credentials and access
Transfer every account, key, domain, certificate and third-party service into your control, rotate what the vendor held, and close what only the vendor used.
- 04
Untangle the licences
Identify every licence the system depends on that is held in the vendor's name — tools, components, subscriptions — and reassign, replace or re-purchase each before the vendor's accounts close.
- 05
Cut over from a parallel run
The successor operates the system alongside the incumbent for an agreed period, carrying real work, before responsibility formally transfers and the exit completes.
Extend the parallel run
If the successor cannot yet carry the system alone, the parallel period extends rather than the cutover proceeding on schedule — a late exit is recoverable; a failed one in production is not.
At signing
The vendor exit terms worth negotiating on signing day
Every step of the sequence above depends on something the contract either secured or did not. Escrow verification requires an escrow clause with a defined refresh cadence and your right to test it. Knowledge transfer requires contracted handover days — priced and scheduled — because "reasonable assistance" is whatever the departing vendor decides it is. Credential handover requires that accounts, domains and infrastructure were registered in your name from the start, since transferring ownership of a domain or cloud account mid-dispute can take longer than the transition itself. Licence untangling requires a register, maintained through the relationship, of every dependency held in whose name.
None of these terms is adversarial, and the negotiation is easiest at the moment trust is highest. A capable vendor agrees to them readily, because they cost a well-run vendor almost nothing — the repository was going to be yours anyway, the documentation was going to exist anyway. A vendor that resists exit terms at signing, when the relationship is at its warmest, is describing how it intends to hold you. That resistance is not a negotiating position to overcome; it is information about the vendor.
In practice
A vendor exit run without a standstill, illustrated
Illustrative — a typical engagement shape, not a named client
An organisation decides not to renew with the outsourcer that has built and operated its core customer system for years. The contract, negotiated well, contains escrow, handover-day and account-ownership clauses. The system must keep serving customers throughout.
- 01Months before expiry, the escrow is exercised: the receiving team builds the system from the deposited code and restores from the data export, surfacing gaps — an undeposited configuration store, an outdated build script — while the incumbent is still contracted to fix them.
- 02The contracted handover days are spent on doing, not presenting: the receiving engineers deploy releases, resolve simulated incidents and run the operational calendar under the incumbent's supervision, producing runbooks the incumbent reviews for accuracy.
- 03Credentials, domains and third-party services move into the organisation's control on a tracked register; licences held in the outsourcer's name are reassigned or replaced; and the successor team then operates in parallel with the incumbent through an agreed period of real workload before the formal cutover.
The relationship ends at the contract date with the system running, the knowledge held by the new team in writing and in practice, and no period in which the organisation could not deploy, recover or operate its own system.
Our role
What we take on in a vendor exit, and what stays yours
- 01
The receiving team
We take over systems from departing vendors — verifying the artefacts, absorbing the knowledge transfer and operating through the parallel run — including codebases whose documentation is thinner than anyone admitted.
- 02
Exit terms reviewed before you sign anyone
On a new contract, we review the escrow, handover, ownership and licence clauses from the engineering side — whether what is promised is technically sufficient to rebuild and run the system without its author.
- 03
An exit standard we accept against ourselves
Every term this page recommends demanding of a vendor, we accept in our own contracts — your repository, your accounts, contracted handover — because an exit-ready engagement is simply a well-run one.
Whether and when to leave a vendor is your commercial decision; our work is making the leaving technically boring — verified artefacts, transferred knowledge, and a cutover that never bets the operation.
Common questions
What buyers ask
What should a software escrow arrangement actually contain?+
Everything needed to rebuild and run the system without its author, which is more than source code. That means the code and its full history, the build and deployment instructions, the configuration for each environment with secrets handled securely, database schemas and a recent data export, the dependency list with versions, and the operational documentation. Two clauses decide whether the escrow is real: a refresh cadence tied to releases, so the deposit tracks the system rather than its first version, and a verification right that lets you periodically build from the deposit. An escrow no one has ever built from is a hope, not an arrangement.
How long should the parallel run last in a vendor transition?+
Long enough for the successor to have handled the system's real rhythms, which is a coverage question rather than a calendar one. The period should span at least one full operational cycle of the system — its billing runs, month-end loads, seasonal peaks or release cadence — plus at least one genuine incident or failure drill handled by the successor with the incumbent observing. Systems with long cycles or high stakes justify longer runs; a simple internal tool needs far less. The honest criterion for ending it is a demonstration: the successor has deployed, recovered and operated unassisted. Set the trigger as capability shown, with the calendar as a budget, not the other way round.
Can we exit a vendor whose contract never mentioned exit at all?+
Yes, but expect to buy at exit what the contract failed to secure at signing. The practical route is to negotiate a transition addendum while the commercial relationship still has value to the vendor — remaining payments, a reference, future work — exchanging that value for handover days, artefact delivery and account transfers. Start earlier than feels necessary, because goodwill decays as the end date approaches, and begin reconstructing independently what you can: your own inventory of systems, credentials the vendor holds, and licences in its name. The worst position is discovering at termination that the vendor owns the domain, the cloud account and the only copy of the deployment knowledge. If that describes your current contract, the time to fix it is now, mid-relationship — not at renewal, and not at the end.
In this cluster
Plan a transition with us
A transition-planning conversation — whether you are negotiating a new contract's exit terms or already need to leave an incumbent in an orderly way.
Start the conversation
