Change the supplier arrangement without losing the knowledge.

Veylund: Veylund reviews the arrangement and can coordinate the agreed handover between supplier, sponsor and receiving team.

Your company: Your sponsor arranges access and supplier participation, makes contractual decisions and provides people who can accept the work.

A transfer depends on access, supplier cooperation and receiving capacity. Legal advice and detailed technical audits are separately scoped.

1. Review before deciding to leave

   Examine commitments, delivered work, spend, access and responsibilities. Include the supplier’s perspective and compare practical alternatives.

2. Make the transfer explicit

   Name the accounts, documentation, product knowledge and operational responsibilities to transfer. Agree who will receive and check each part.

3. Check continuity with the receiving team

   Sequence the transfer around ongoing delivery. Verify the agreed access and knowledge, and record any unresolved dependency.

Completion: The review supports an informed decision. A transfer ends when the agreed access and knowledge have been accepted by the receiving owners.

Illustrative situation, not a client case study.

Starting point: A company wants to bring development in-house, but has not checked account access or what the incoming team needs to operate the product.

Agreed work: Review the gaps and work through a staged transfer with named receiving owners, rather than treating a code export as a completed handover.