Trupeer Blog
要約
Switching outsourcing providers is often the right decision: better pricing, better service, new capabilities or a fresh start after a relationship that stopped working. But a vendor-to-vendor transition has one built-in weakness. The people who know how the work is done work for the provider that's leaving.
The incumbent has years of process knowledge, client-specific rules and workarounds. The incoming provider has none of it yet. And the client, caught in the middle, often knows less about the day-to-day detail than either of them. Knowledge transfer (KT) is the bridge, and it has to be built while the incumbent's team is shrinking and its attention is moving elsewhere.
This guide explains how to run knowledge transfer in a vendor-to-vendor transition when the incumbent is leaving, using a simple three-phase approach: capture fast, verify, certify.
What Is a Vendor-to-Vendor Transition?
A vendor-to-vendor transition is the transfer of outsourced work from one service provider, the incumbent, to another, the incoming provider. It's sometimes called a provider switch or a second-generation outsourcing transition, because the work has already been outsourced once.
Three parties are involved:
The client, who owns the work, the contracts and the relationship with both providers.
The incumbent provider, which is exiting and has a contractual obligation to support the handover.
The incoming provider, which takes over the work and is responsible for service from go-live.
Knowledge transfer is the core of the transition. The incoming provider needs to learn every process, system, rule and exception well enough to deliver the agreed service levels without the incumbent's help.
Why KT Is Hardest When the Incumbent Is Leaving
A vendor-to-vendor transition has all the usual transition risks, plus a few of its own:
Low incentive to cooperate. The incumbent is losing the contract. Its obligations come from the exit terms, and its best people may already be moving to other accounts.
Attrition during exit. Agents and team leads on an exiting account often leave or get redeployed before KT ends, taking knowledge with them.
Knowledge sits with the incumbent, not the client. After years of outsourcing, the client may no longer have people who know the process in detail.
Documentation is incomplete or out of date. Desktop procedures may not reflect how the work is actually done today, or may be held in the incumbent's own systems.
Fixed, compressed timelines. The exit date is set by the contract, so KT has to fit a window that's often shorter than anyone would like.
Two providers, two methods. The incoming provider may use different tools, templates and ways of working, so knowledge has to be translated, not just copied.
Because of these risks, KT that relies on live sessions and notes is fragile. If something isn't captured while the incumbent's people are still there, it's likely lost.
Who Owns the Knowledge? The Client's Role
The most important decision in a vendor-to-vendor transition is who owns the resulting documentation. The answer should be the client.
When the knowledge base belongs to the client, the next transition, whether to another vendor, to a captive GCC or back in-house, starts from a documented baseline instead of from scratch. In practice, that means:
Check the exit terms early. Work with legal and procurement to confirm what the incumbent must deliver: documentation, KT sessions, data, access and support time.
Set up tri-party governance. Name a KT lead at the client, the incumbent and the incoming provider, with a weekly review and a shared KT tracker.
Define KT deliverables as evidence. Every process should end with a recorded walkthrough, an approved SOP and certified staff, not just a completed session.
Store everything in a client-owned knowledge base. Neither provider should be the only holder of how the work is done.
The Capture, Verify, Certify Framework
When the incumbent is leaving, KT has to be fast without being careless. A three-phase approach keeps both in balance: capture knowledge quickly, verify it against the real work, and certify that the incoming team can deliver.
Phase 1: Capture Fast
The goal of this phase is to get knowledge out of people's heads and into a recorded, reusable form before the incumbent's team disperses.
Inventory every process and map the knowledge holders. For each process, note its volume, systems, service levels and who at the incumbent actually knows it. Prioritize processes where knowledge sits with one or two people.
Agree a recording protocol. Every KT session is recorded, whether it's an MS Teams or Zoom call or a screen recording of the work. SMEs show the real task in the real system, cover exceptions and use test or masked data where possible.
Record in parallel. Don't wait for scheduled sessions. Ask incumbent SMEs to record short walkthroughs of their own tasks using a tool like Trupeer's AI screen recorder, so several processes are captured at once.
Turn recordings into documentation within days. Upload recordings as they arrive. Trupeer turns each one into a step-by-step SOP with screenshots and a narrated video, so documentation keeps pace with KT.
Capturing fast matters most for the highest-risk processes. If you only get one session with a key SME before they leave, a recording of it is worth far more than notes.
Phase 2: Verify
Fast capture produces drafts. Verification turns them into a reliable source of truth.
SME review. The incumbent's SME checks each SOP for accuracy and adds missing exceptions while they're still available.
Client review. The client's process owner confirms the SOP matches the agreed process, policies and service levels.
Test against live work. During shadowing, the incoming team follows the SOP while watching the incumbent do the work. Every difference goes into a gap log.
Update for the future state. Adjust SOPs for the incoming provider's tools, escalation paths and reporting, so they describe how the work will run after go-live.
Close every gap. Fix each issue in the SOP and video, and re-record steps that turned out to be wrong.
Verification is where hidden tribal knowledge surfaces. The goal is to find it while someone who knows the answer is still in the room.
Phase 3: Certify
Certification proves the incoming provider can run each process to the required standard before the incumbent exits.
Assess against the approved SOPs. Use knowledge checks, practical walkthroughs and quality checks of real work, with the same criteria for everyone.
Pass reverse shadowing. The incoming team does the work while the incumbent watches, and error rates must meet the agreed threshold.
Certify per person and per process. Each team member is signed off on the processes they're allowed to run.
Get client sign-off. The client accepts KT for each process only when SOPs are approved, staff are certified and reverse shadowing has passed.
Certification turns "KT complete" from an opinion into evidence the client, incumbent and incoming provider can all point to.
Tri-Party Governance That Keeps KT on Track
Vendor-to-vendor transitions fail most often on coordination. A simple governance rhythm helps:
Weekly KT review with all three parties, covering progress per process, gaps, risks and escalations.
A shared KT tracker showing, for each process, whether it's recorded, documented, verified and certified.
A clear escalation path to senior sponsors for disputes about scope, access or cooperation.
Risk tracking for key-person dependencies, so processes held by one SME at the incumbent are captured first.
Common Mistakes in Vendor-to-Vendor KT
Counting sessions instead of outcomes. A completed session isn't proof that knowledge transferred. Track recordings, approved SOPs and certified staff instead.
Leaving documentation until after KT. By the time SOPs are written, the incumbent's experts may be gone.
Letting the incoming provider own the documentation alone. The client should keep a copy of everything, in its own knowledge base.
Skipping exceptions. The standard path is easy to teach. The exceptions cause the errors after go-live.
Ending KT on the contract date regardless of readiness. Plan certification well before the exit date, and use hypercare for what's left.
How Trupeer Helps in a Vendor-to-Vendor Transition
Trupeer supports each phase of the capture, verify, certify approach:
Capture: record KT sessions and SME walkthroughs with the AI screen recorder, or upload existing MS Teams and Zoom recordings. Each one becomes an SOP and a narrated video.
Verify: SMEs and the client review drafts instead of writing from scratch, and steps that need fixing are updated by re-recording only that step.
Certify: use the approved SOPs and videos as the basis for training and assessments, so every person is measured against the same content.
Keep it consistent: apply one template and brand kit so documentation looks the same whichever SME recorded it.
Support every location: translation creates SOPs, voiceovers and captions in each team's language from the same source.
Give the client ownership: publish everything to a searchable knowledge base the client controls, ready for the next transition.
The recording-first approach scales. Genpact used Trupeer to turn recorded process sessions and SME walkthroughs into 500+ SOPs and training videos in five languages in 3 months, for a program that would otherwise have taken 12. Read the Genpact customer story.
Vendor-to-Vendor KT Checklist
Before the incumbent exits, check that:
Every process has at least one recorded walkthrough from an incumbent SME.
Each process has an SOP and video, reviewed by the incumbent SME and approved by the client.
Known exceptions, workarounds and escalation paths are documented.
SOPs reflect the incoming provider's tools and ways of working.
The incoming team has passed reverse shadowing at the agreed quality level.
Every team member is certified on the processes they will run.
All documentation is stored in a knowledge base the client owns.
For related guides, see GCC setup knowledge transfer, the transition hypercare period, rebadging in outsourcing transitions and the GBS transition methodology.
Conclusion
In a vendor-to-vendor transition, the knowledge you need is leaving with the incumbent. You can't slow that down, but you can capture it faster. Record first, verify against the real work while the incumbent's experts are still available, and certify the incoming team before the exit date.
Do it in a knowledge base the client owns, and the next transition starts from a documented baseline. Start free with Trupeer and turn every KT session into SOPs and videos your incoming team can be certified on.
Frequently Asked Questions
What is a vendor-to-vendor transition?
It's the transfer of outsourced work from one service provider, the incumbent, to a new provider. The client, the incumbent and the incoming provider all take part, and knowledge transfer is the core of the transition.
How does knowledge transfer work in a vendor-to-vendor transition?
The incumbent's SMEs explain and demonstrate each process to the incoming provider's team. The knowledge is captured in SOPs and videos, verified through shadowing, and the incoming team is certified before the incumbent exits.
Why is KT difficult when the incumbent is leaving?
The incumbent is losing the contract, its people may leave or be redeployed, documentation is often out of date, the client may not know the process in detail, and the exit date is fixed.
What is the capture, verify, certify approach?
It's a three-phase KT method. Capture means recording every session and walkthrough quickly. Verify means checking SOPs with SMEs, the client and live work. Certify means assessing and signing off the incoming team before the incumbent exits.
Who should own the documentation in a vendor transition?
The client should. Keeping SOPs and videos in a client-owned knowledge base protects the knowledge if the incoming provider changes in future, or if the work moves to a GCC or back in-house.
How do you certify the incoming provider's team?
Assess each person against the approved SOPs using knowledge checks, practical walkthroughs and quality checks, require reverse shadowing to pass at the agreed quality level, and get client sign-off per process.
What should the client ask the incumbent to deliver at exit?
Typically documentation, recorded KT sessions, data, system access and SME support time. The exact obligations depend on the contract's exit and termination assistance terms, so check them with legal and procurement.
How can you speed up vendor-to-vendor knowledge transfer?
Record every KT session and walkthrough, have SMEs record tasks in parallel, turn recordings into SOPs and videos within days, and verify them while the incumbent's experts are still available.
