CCaaS procurement archive context checklist: what to confirm before the old contact-center platform goes dark

Short answer

Check three milestones in order: before the new platform vendor is awarded, before cutover to the new platform, and before access to the old platform ends. At each one, confirm whether the company can still link call segments to final resolutions: each transfer hop to the next, a later repeat call to the original case, and cases to their outcome. Name who owns each answer and what is lost if the item is skipped. Every date comes from the company's procurement plan or the old contract.

Visual briefFull-size diagram
A vertical countdown with three milestones (vendor award, cutover and old platform switch-off) where checklist items about transfer identifiers, case links, retention and ownership tick off in turn.
The checklist as a countdown to switch-off. Dates come from the company's own procurement plan and old contract.

This checklist belongs to the CCaaS procurement guide. The linking question is first asked in the 15-minute meeting agenda; this page tracks it through to switch-off.

Setting the countdown

Write down three dates and where each came from before marking anything.

MilestoneUsual source of the dateIf there is no date yet
Vendor awardThe procurement timeline in your engagement planStart milestone one anyway; its items do not depend on the award date
CutoverThe new platform's go-live and number-porting planRecord who sets go-live and return when it is fixed
Old platform switch-offThe current contract's term, renewal notice or termination letterLeave it open with one item: "confirm the access end date"

Each item gets one of three states: confirmed (a named person said so), unknown (with a name for who will find out) or at risk (the current plan loses it). Keep the sheet at metadata level and share it only with the people who answered. No call IDs, customer names, recordings or transcripts belong in it.

Two clocks run at once. The contract clock ends access to the old platform. The platform's own retention clock may delete records sooner. Amazon Connect, for example, documents that contact records are available for 24 months from initiation and are then deleted, and that each contact search covers up to 8 weeks at a time. Other platforms differ, so ask the administrator what theirs keeps.

Milestone one: before the vendor is awarded

Requirements are still open, so this is the cheapest moment to protect the chain.

ConfirmOwnerIf skipped
How the current platform links transferred segments (a shared identifier, or none)Platform administratorNobody knows what "import history" needs to preserve
Whether repeat calls are attached to the original case or ticket, and roughly how oftenCRM or ticketing ownerThe weakest link in the chain stays invisible
That the RFP asks for historical records with transfer identifiers and case references, not only recordingsConsultantThe winning vendor imports audio and drops the joins
The CEO, who can authorize a licensing discussion about the company's records, by nameOwner or CEOAn interested company has nobody able to say yes

Amazon Connect documents what a preserved join looks like: every transferred or consulted record carries the ID of the first record in the call, plus pointers to its neighbors. If the current platform has an equivalent, the RFP should name it.

Milestone two: before cutover

Migration scope is set and test loads run. Closed history is the usual casualty.

ConfirmOwnerIf skipped
Whether historical contact records migrate, and for how many yearsMigration leadYears of chains stay only in the old platform
Whether migrated records keep their transfer identifiers and case referencesMigration leadHistory arrives as isolated segments
Where agent notes, dispositions and closure reason codes live, and whether they moveCRM ownerThe outcome end of the chain is separated from the calls
Whether counsel has confirmed how notice and consent were handled for recordingsCounselRecordings stay out of any later discussion by default

The contact-center migration retention page covers recording retention in more depth, and the call recording retention policy guide explains how policies are usually written.

Milestone three: before the old platform is switched off

After access ends, whatever was not copied may be out of reach for good.

ConfirmOwnerIf skipped
The exact access end date under the old contractFinance or procurement leadThe date is discovered after it passes
Who can export historical records from the old platform, by namePlatform administratorNobody has the rights or the knowledge in time
Where retained records will live, who can read them, and that the copy includes the linking fieldsIT leadA copy exists but its segments cannot be joined
Whether any records are nearing the platform's own retention limit before switch-offPlatform administratorThe oldest chains age out regardless of the contract

Reading the checklist back to the owner

Illustrative. A fictional 520-person travel assistance provider finished all three milestones. The consultant's summary for the COO:

AreaStateNote
Transfer hopsConfirmedShared identifier on every hop for five years
Repeat calls to casesPartialCase reference attached on most repeat calls since a 2022 wrap-up rule
Case outcomesConfirmedClosure reason codes in the CRM
Migration scopeAt riskVendor quote covers recordings only; identifiers not included
Own copy of recordsConfirmedNightly copy to company storage, owned by IT
Consent reviewConfirmedCounsel reviewed notice wording in 2023
Authorized contactConfirmedCEO, with the COO as sponsor

The "at risk" line is a procurement fix, not a referral question: ask the vendor to include identifiers. The rest is a sound metadata-level description.

If the CEO wants to explore licensing, disclose first: you are a SourceX referral partner; SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout; if a qualifying license completes and every payment condition is met, SourceX may pay you a reward that it funds separately and never deducts from the company's payout.

Then check fit: 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 70% of the data is in English. Client contracts, for outsourced centers especially, and consent practices can limit reuse, so the company's counsel decides. SourceX's current data needs, the rights review result and any offer stay unknown until SourceX reviews an application.

Introduce with the CCaaS procurement introduction email after signing the Channel Partner Agreement. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Illustrative only: a $400,000 payout to the company would mean a $70,000 default reward; the rewards page lists every condition. For the wider vendor-selection record type, see procurement and vendor workflows and the guide to assessing procurement approvals and exception workflows.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the checklist shows the call chains survive switch-off and the owner wants to talk, register as a partner, check who qualifies and read the program terms before you introduce them.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is go-live the deadline?

Usually not. The date that matters is when access to the old platform ends under its contract, plus any retention limit inside the platform itself. Confirm both rather than assuming either.

What if the company keeps its own copy of contact records?

Then milestone three is mostly about confirming that copy includes the transfer identifiers and case references, not just the call metadata, and that someone owns it.

Should procurement documents mention this checklist?

The migration requirement can go in the RFP: import historical contact records with their transfer identifiers and case references. The referral itself never belongs in procurement documents.

Sources

  1. docs.aws.amazon.com/connect/latest/adminguide/identify-conferenc…
  2. docs.aws.amazon.com/connect/latest/adminguide/ctr-data-model.html
  3. docs.aws.amazon.com/connect/latest/adminguide/contact-search.html
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment