How to Transition From Another Supplier to Progressive Robot
Moving from an existing development agency, freelancer, or in-house team to Progressive Robot requires careful planning. This article guides you through what to expect and what you need to do.
What We Need at Transition
- Code repository access: We need read access to your existing codebase to conduct a technical assessment
- Documentation: Any existing technical documentation, architecture diagrams, and README files
- Infrastructure access: Credentials for your hosting environment, DNS management, and third-party services
- Supplier handover: Ideally, a structured handover session with your outgoing supplier
- Licence and service accounts: A list of all third-party services in use and who holds the accounts
Our Transition Process
- Technical assessment: We review the existing codebase and infrastructure to understand the current state
- Risk identification: We identify any immediate technical debt, security issues, or compliance gaps
- Transition plan: We agree a phased transition plan — this may include a period of dual running before full handover
- Knowledge transfer: We work with the outgoing supplier (if co-operative) to capture undocumented knowledge
- Stabilisation period: First 30 days of our management focused on stability before introducing new development
Managing the Outgoing Supplier
Outgoing suppliers are sometimes unco-operative. We recommend: retaining access to all your own accounts, not relying solely on the outgoing supplier for passwords, and being prepared for the transition to take longer than planned if co-operation is limited. We will advise you on your legal options if a supplier withholds code or data that belongs to you.