Plan the exchange of the company that maintains your software: access, knowledge, continuity and criteria for accepting the transfer without depending on promises.
Index
Supplier switching begins before choosing who will take over the code. If no one can publish a version without help from the previous team, the company still doesn't control its operation. The new contract needs to cover the transition in addition to the desired improvements.
Decision this guide helps you make: Transfer operational responsibility without losing access or knowledge.
Raise what really sustains the system
Repository is just one part of delivery. Identify hosting, banking, storage, DNS, queues, store accounts, third-party integrations and billing. For each resource, record ownership, administrator, and access recovery. Carry out this inventory with representatives of the two suppliers and the company. Credentials must be transferred through secure mechanisms, never inserted into the ticket document.
Hire a verifiable absorption phase
Request a separate delivery to prepare the environment, run tests and publish a small change for approval. It allows you to discover hidden dependencies before taking on new features. The incoming supplier must explain what it has managed to reproduce, what depends on third parties and what risks remain. A recorded meeting helps, but is not a substitute for running independently.
Agree on a Shared Responsibility Window
Define who responds to incidents during the handover, who approves changes and when the previous team stops operating. Avoid two teams publishing without coordination. Bigger changes can wait until the new team demonstrates restoring, monitoring, and rolling back a post. The duration of the transition should reflect the complexity encountered, not a standard timeframe promised without access.
Accept transfer by evidence
A good conference asks the incoming team to perform tasks without live instruction: climbing the room, finding an error, restoring copy, and explaining a critical integration. Compare the result with the inventory. Pending issues need someone responsible and an agreed date; Items without resolved ownership should not disappear in a generic acceptance.
- Request an inventory of accounts, services and responsible parties.
- Include independent publishing and restoration in the acceptance.
- Separate transition cost from evolution budget.
A scenario to check out in the demo
Hypothetical example: the company can access the code, but publications depend on an account from the old provider. The first milestone in the transition would be to carry out an approval publication under the company's administration and register the procedure. New features only come into effect after confirming this autonomy. If the account cannot be transferred, the proposal needs to explain the necessary migration and its impact.
Briefing to request a proposal
- List of resources whose administration still depends on the previous supplier.
- Internal person authorized to receive access and approve passage.
- Critical operation that the incoming team must demonstrate without assistance.
Prepare the assessment with Quantum9
Take the available map, the current contract and the problems observed. The conversation must define a safe absorption range and the necessary access to estimate the effort. If the system is stable, an organized walkthrough is often more important than immediately rewriting components.
Discover the scope of Software engineering and evolution and deepen the context in related guide.