# CCaaS procurement archive context checklist | SourceX

Canonical: https://refer.sourcex.si/resources/ccaas-procurement-archive-context-checklist
Last updated: 2026-11-05

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.

This checklist belongs to the [CCaaS procurement guide](/guides/moment-ccaas-procurement-contact-center-consultants). The linking question is first asked in the [15-minute meeting agenda](/resources/ccaas-procurement-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.

| Milestone | Usual source of the date | If there is no date yet |
|---|---|---|
| Vendor award | The procurement timeline in your engagement plan | Start milestone one anyway; its items do not depend on the award date |
| Cutover | The new platform's go-live and number-porting plan | Record who sets go-live and return when it is fixed |
| Old platform switch-off | The current contract's term, renewal notice or termination letter | Leave 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.

| Confirm | Owner | If skipped |
|---|---|---|
| How the current platform links transferred segments (a shared identifier, or none) | Platform administrator | Nobody knows what "import history" needs to preserve |
| Whether repeat calls are attached to the original case or ticket, and roughly how often | CRM or ticketing owner | The weakest link in the chain stays invisible |
| That the RFP asks for historical records with transfer identifiers and case references, not only recordings | Consultant | The winning vendor imports audio and drops the joins |
| The CEO, who can authorize a licensing discussion about the company's records, by name | Owner or CEO | An 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.

| Confirm | Owner | If skipped |
|---|---|---|
| Whether historical contact records migrate, and for how many years | Migration lead | Years of chains stay only in the old platform |
| Whether migrated records keep their transfer identifiers and case references | Migration lead | History arrives as isolated segments |
| Where agent notes, dispositions and closure reason codes live, and whether they move | CRM owner | The outcome end of the chain is separated from the calls |
| Whether counsel has confirmed how notice and consent were handled for recordings | Counsel | Recordings stay out of any later discussion by default |

The [contact-center migration retention page](/systems/contact-center-migration-call-recordings-retention) covers recording retention in more depth, and the [call recording retention policy guide](/guides/call-recording-retention-policy) 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.

| Confirm | Owner | If skipped |
|---|---|---|
| The exact access end date under the old contract | Finance or procurement lead | The date is discovered after it passes |
| Who can export historical records from the old platform, by name | Platform administrator | Nobody has the rights or the knowledge in time |
| Where retained records will live, who can read them, and that the copy includes the linking fields | IT lead | A copy exists but its segments cannot be joined |
| Whether any records are nearing the platform's own retention limit before switch-off | Platform administrator | The 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:

| Area | State | Note |
|---|---|---|
| Transfer hops | Confirmed | Shared identifier on every hop for five years |
| Repeat calls to cases | Partial | Case reference attached on most repeat calls since a 2022 wrap-up rule |
| Case outcomes | Confirmed | Closure reason codes in the CRM |
| Migration scope | At risk | Vendor quote covers recordings only; identifiers not included |
| Own copy of records | Confirmed | Nightly copy to company storage, owned by IT |
| Consent review | Confirmed | Counsel reviewed notice wording in 2023 |
| Authorized contact | Confirmed | CEO, 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](/resources/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](/rewards) lists every condition. For the wider vendor-selection record type, see [procurement and vendor workflows](/data-types/procurement-and-vendor-workflows) and the guide to [assessing procurement approvals and exception workflows](/guides/how-to-assess-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](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce them.

## Sources

- https://docs.aws.amazon.com/connect/latest/adminguide/identify-conferences-transfers.html
- https://docs.aws.amazon.com/connect/latest/adminguide/ctr-data-model.html
- https://docs.aws.amazon.com/connect/latest/adminguide/contact-search.html
- https://refer.sourcex.si/terms
