System cost reduction archive context checklist: what to confirm before the announcement, the cutover and the switch-off

Short answer

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.

Visual briefFull-size diagram
A countdown timeline with three milestones, announcement, cutover and switch-off, where checklist items tick off in turn: tools and admins listed, renewal terms read, notice date confirmed, deletion window read, export tested, final export verified and owner decision recorded.
Illustrative countdown for one tool. Milestone dates come from the company's own documents, never from an assumed schedule.

This checklist belongs to the software rationalization and cost reduction guide, 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.

ConfirmOwnerIf skipped
Which tools in the plan hold three or more years of workflow history, by name and approximate record countIT leadHistory-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 reductionsIT lead, HRThe only person able to run a full export leaves in the first wave
The renewal date and notice period in each contractProcurementThe 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 recordsGeneral counselRecords 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 backupIT leadEffort is spent on tools whose history is already safe

Staff reductions and admin handover overlap heavily here; the 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.

ConfirmOwnerIf skipped
The termination or non-renewal date stated in the notice actually sentGeneral counsel, procurementThe 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 ruledDebtor's counselA 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 planIT leadThe deletion window is guessed instead of read
Whether the contract changes that policy, and whether reactivation or a support request extends itProcurement, general counselThe company relies on a grace period its contract removed
A test export of one full year, checked for attachments, internal notes and timestampsIT leadThe final export fails in the last week, with no time to fix it
Which entity owns the records and who could authorize a licensing discussionGeneral counsel, CEOAn 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 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.

ConfirmOwnerIf skipped
The final export is complete: record counts match, attachments open, notes and timestamps are presentIT leadGaps are found after the vendor has deleted the source
The export sits in storage the company controls, with a named owner and a retention ruleIT lead, general counselThe archive survives but nobody can find it or is allowed to keep it
Admin accounts are removed only after the export is verifiedIT leadAccess disappears with a half-finished export
The date the vendor's deletion window closes is written downProcurementNobody knows when a recovery request would still work
The owner has recorded a licensing decision: discuss now, revisit, or noCEO or CROThe question is never asked, or asked after the records are gone

Email often follows a separate schedule; 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:

MilestoneCheckStatusNote
Before announcementTools with history listedDoneEight years of service jobs and technician notes
Before announcementAdmins and staff reductionsDoneOne admin, kept on until switch-off
Before cutoverNotice date confirmedDoneDate taken from the signed non-renewal letter
Before cutoverVendor post-cancellation policy readNot yetIT lead to request it in writing
Before cutoverTest exportLateScheduled after go-live; moved earlier
Before cutoverOwner and approver namedDoneParent company owns records; CEO approves
Before switch-offFinal export verifiedNot applicable yetWaits on the test export
Before switch-offOwner's licensing decisionRevisitCEO 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; to write the introduction, use the annotated email. Interim finance leads may also find the 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, check who qualifies and read the program terms before the switch-off milestone.

  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

Can I use this checklist if the company is not in a restructuring?

Yes. Any cost program that retires software has the same three milestones. The court-related checks simply drop out when there is no case.

Who should hold the completed checklist?

The company: usually the CFO's office or the program lead. The advisor keeps only the status words and dates the company chose to share, never files or credentials.

What if the company skips the first milestone because the plan is already public?

Start at the cutover checks and record the first-milestone items as 'late'. Most can still be done; the one that cannot is keeping an admin who has already left.

Sources

  1. refer.sourcex.si/terms
  2. support.zendesk.com/hc/en-us/articles/4408883628954-Zendesk-Serv…
  3. atlassian.com/licensing/cloud
  4. law.cornell.edu/uscode/text/11/365

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