# Cost reduction archive checklist by milestone | SourceX

Canonical: https://refer.sourcex.si/resources/system-cost-reduction-archive-context-checklist
Last updated: 2026-11-04

Work through three milestones for every tool the cost program retires. Before the cuts are announced, list archive-holding tools, their admins and the renewal terms. Before cutover, confirm the binding end-of-access date in writing, read the vendor's post-cancellation policy and test a full export. Before switch-off, verify the final export, record where it lives and record the owner's licensing decision. Each check has a named owner and a known cost if it is skipped.

This checklist belongs to the [software rationalization and cost reduction guide](/guides/software-rationalization-cost-reduction), which explains why only a notice, a court order or a vendor policy creates a real cancellation date. The page below is the timing tool: it ties each check to the milestone where it is still cheap to do.

## How to use the countdown

Fill in one copy per tool, not one per program. Write the milestone dates from the company's documents at the top. If a date is not yet fixed, write "not fixed" and do only the first milestone's checks; the rest wait until something binding exists. The advisor asks the questions and records status words ("done", "not yet", "late", "not applicable"); the company does the work and keeps any evidence.

## Milestone 1: before the cost plan is announced

The people who know the old tools are still in their seats, and nobody outside the leadership team knows which tools are going. This is the cheapest moment to learn what each tool holds.

| Confirm | Owner | If skipped |
|---|---|---|
| Which tools in the plan hold three or more years of workflow history, by name and approximate record count | IT lead | History-rich tools get cut on cost alone, with no records decision |
| Who holds admin rights for each tool, and whether they are affected by staff reductions | IT lead, HR | The only person able to run a full export leaves in the first wave |
| The renewal date and notice period in each contract | Procurement | The company misses the window to give notice, or gives it before planning an export |
| Any legal hold, regulatory retention period or litigation that covers the tool's records | General counsel | Records under hold are deleted, which is a far bigger problem than a lost archive |
| Which tools already have their data exported elsewhere, such as a warehouse or backup | IT lead | Effort is spent on tools whose history is already safe |

Staff reductions and admin handover overlap heavily here; the [reduction-in-force IT checklist](/resources/reduction-in-force-it-checklist) covers access transfer in more depth.

## Milestone 2: before cutover and before notice takes effect

The plan is public, notices are going out and the replacement is being configured. Dates now become real, and each one needs a document behind it.

| Confirm | Owner | If skipped |
|---|---|---|
| The termination or non-renewal date stated in the notice actually sent | General counsel, procurement | The team works to a date nobody can show, in either direction |
| If the company is in a court case, whether the contract is on a rejection motion and whether the court has ruled | Debtor's counsel | A contract is assumed to end on a date the court has not set |
| What the vendor's own policy says about data after cancellation, for this account and plan | IT lead | The deletion window is guessed instead of read |
| Whether the contract changes that policy, and whether reactivation or a support request extends it | Procurement, general counsel | The company relies on a grace period its contract removed |
| A test export of one full year, checked for attachments, internal notes and timestamps | IT lead | The final export fails in the last week, with no time to fix it |
| Which entity owns the records and who could authorize a licensing discussion | General counsel, CEO | An introduction goes to someone who cannot say yes |

Vendor policies differ and change. As checked on 2026-10-18, Zendesk's Service Data Deletion Policy starts automated deletion 90 days after an account is canceled or terminated, and Atlassian keeps data for deactivated paid cloud sites for 60 days after the subscription period ends before deleting it permanently. Under 11 U.S.C. 365, rejecting an executory contract needs the court's approval, and in Chapter 7 a contract not assumed within 60 days after the order for relief is deemed rejected. These are examples of what to read, not dates to plan around; the [SaaS data export rights guide](/guides/saas-data-export-rights-contract) lists the contract clauses that matter.

## Milestone 3: before the old system is switched off

The replacement is live and the old tool is read-only or about to close. Anything not done now is usually not recoverable.

| Confirm | Owner | If skipped |
|---|---|---|
| The final export is complete: record counts match, attachments open, notes and timestamps are present | IT lead | Gaps are found after the vendor has deleted the source |
| The export sits in storage the company controls, with a named owner and a retention rule | IT lead, general counsel | The archive survives but nobody can find it or is allowed to keep it |
| Admin accounts are removed only after the export is verified | IT lead | Access disappears with a half-finished export |
| The date the vendor's deletion window closes is written down | Procurement | Nobody knows when a recovery request would still work |
| The owner has recorded a licensing decision: discuss now, revisit, or no | CEO or CRO | The question is never asked, or asked after the records are gone |

Email often follows a separate schedule; [email archive migration](/guides/email-archive-migration) covers its cutover dates.

## Illustrative countdown for one tool

Illustrative and fictional. A 640-person specialty distributor is retiring the field service tool of a business unit it is folding into the parent. The advisor's completed copy, in status words only:

| Milestone | Check | Status | Note |
|---|---|---|---|
| Before announcement | Tools with history listed | Done | Eight years of service jobs and technician notes |
| Before announcement | Admins and staff reductions | Done | One admin, kept on until switch-off |
| Before cutover | Notice date confirmed | Done | Date taken from the signed non-renewal letter |
| Before cutover | Vendor post-cancellation policy read | Not yet | IT lead to request it in writing |
| Before cutover | Test export | Late | Scheduled after go-live; moved earlier |
| Before cutover | Owner and approver named | Done | Parent company owns records; CEO approves |
| Before switch-off | Final export verified | Not applicable yet | Waits on the test export |
| Before switch-off | Owner's licensing decision | Revisit | CEO wants the export verified first |

Reading it: the date is real, the approver is known and the owner has not said no, so the conversation can continue. The open risk is the late test export, not the licensing question.

## When the checklist says the company may qualify

An introduction makes sense only when a binding date exists, the company owns the records and the owner has opted in. The baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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. Unknown until SourceX reviews it: buyer interest, the rights review result, de-identification and any offer. To raise the subject in a meeting, use the [30-minute agenda](/resources/system-cost-reduction-meeting-agenda); to write the introduction, use the [annotated email](/resources/system-cost-reduction-introduction-email). Interim finance leads may also find the [interim CFO turnaround checklist](/resources/interim-cfo-turnaround-checklist) useful alongside this one.

Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window.

## 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.

When a tool's countdown shows a confirmed date, a named approver and an owner who wants to talk, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before the switch-off milestone.

## Sources

- https://refer.sourcex.si/terms
- https://support.zendesk.com/hc/en-us/articles/4408883628954-Zendesk-Service-Data-Deletion-Policy
- https://www.atlassian.com/licensing/cloud
- https://www.law.cornell.edu/uscode/text/11/365
