Transfer recovery is the work of repairing a call after a transfer lost the customer's context: the agent who picks up has to reconstruct what happened, and the case records how it ended. That history is spread across a telephony platform, a speech analytics tool and a CRM, and a migration retires at least one of them. This guide sets out what a CCaaS consultant should inventory, and why the real deadline is usually not the go-live date.
Why does a CCaaS migration put transfer recovery history at risk?
Because the routing history that ties the legs of one call together usually lives in the platform being replaced. The CRM keeps the case; the old platform keeps the chain.
Amazon Connect is a well-documented example. Each transfer creates a new contact record, linked to the one before it by a previous contact ID, and every leg shares an initial contact ID that identifies the first contact in the chain. AWS publishes logic that uses these IDs with agent and transfer timestamps to tell a consult, a conference and a transfer apart. Contact records are retained for 24 months from when the contact was initiated, and AWS suggests streaming them out if a company wants to manage retention itself. Other platforms have their own models and rules, which should be read in the vendor's documentation, not assumed. The point for an inventory is the same: if the routing chain is not described before the old platform goes, nobody can later say which calls were transferred, how often, or where context was lost.
Amazon ConnectWhat should be inventoried before a CCaaS migration affects call transfer recovery history?
Four things per record class: what it is, how many years it covers, who administers it and when access really ends.
| Record class | Coverage to note | Administered by | Access ends when |
|---|---|---|---|
| Contact segments with transfer links | Months held by the old platform | Telephony admin in IT | Platform retention window or contract end, whichever is first |
| Transcript segments | Years transcribed, which queues | Speech analytics owner in QA | Analytics subscription end |
| Recordings | Years retained, notice and consent practice | Compliance with IT | Storage contract and deletion schedule |
| CRM cases with resolution codes | Years in the CRM, code list versions | CRM admin in customer operations | Not affected by the migration, but join fields may be |
| Supervisor approvals and credits | Years, approval thresholds | Customer operations and finance | Not affected; check where approvals are logged |
| QA scorecards on transferred calls | Years, sampling method | QA lead | Follows the analytics or QA tool |
Add two counts if the head of customer operations can estimate them: transfers per month, and the share of cases closed with a transfer-related reason code. Estimates are enough.
Which date really ends access?
Each record class has its own last day, and the earliest one is often a subscription nobody linked to the migration plan. The graphic shows an Illustrative contact center where the go-live date is fixed and four other dates follow from contracts.
| Record class | Illustrative last access date | Set by |
|---|---|---|
| Transcript segments | 30 days after go-live | Speech analytics subscription, canceled with the old platform |
| Contact segments with transfer links | 90 days after go-live | Old platform contract end, within its 24-month record window |
| Recordings | 12 months after go-live | Storage contract |
| CRM cases and resolutions | No change | The CRM stays |
In this example the transcripts go first, a month after cutover, even though everyone is watching the go-live date. Ask for each date and who set it; the decision about what to keep belongs to the company.
What a partner should not do
Do not collect samples, screenshots or exports for the introduction, and do not recommend keeping records the company has no authority or reason to keep. Nothing should be copied for a licensing discussion. If recordings are in scope at all, the narrower rules on the contact center migration and recordings page apply, and who owns call recordings covers outsourced centers.
Does the company qualify?
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Partners must sign the Channel Partner Agreement before submitting introductions, and attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. The head of customer operations knows coverage; the company's counsel decides what customer calls, transcripts and consent notices allow; and the CEO, COO or owner typically authorizes a licensing discussion. Whether buyers want transfer recovery history and what the rights review concludes stay unknown until SourceX reviews it. See customer support workflows and the industries hub for neighboring record types.
Go deeper on call transfer recovery
- Call transfer recovery referral brief template gives a fill-in introduction note.
- Call transfer recovery exception examples works through transfers that lost context and how each was repaired.
- Call transfer recovery records across systems is a field map of how telephony, transcript and CRM records join.
- Who can license call transfer recovery records answers which decision-maker to introduce.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the cutover plan shows record classes with access dates the company has not yet weighed, register as a partner, check the company against who qualifies, and read the program terms before you introduce the executive who can authorize the discussion.