First 100-day plan archive context checklist: what to confirm before announcement, cutover and switch-off

Short answer

The integration lead, the IT lead, the controller, the general counsel and the CEO can between them identify which records an acquired company holds and authorize a review, but only while the old systems and the people who ran them are still there. This checklist sets out what each must confirm at three points: before the integration is announced, before cutover and before the old system is switched off. Each item names an owner and what is lost if it is skipped. No deadline here is invented: the dates come from the company's contracts and the vendor's documentation.

Visual briefFull-size diagram
A countdown timeline with three milestones, announcement, cutover and switch-off, where checklist items tick off in turn before the old system's switch-off point.
Illustrative sequence. The company's own contract end date and vendor window set the real deadline.

This checklist belongs with the comparison of a value creation plan and a 100-day plan. The 30-minute records meeting agenda is where the CEO's decision in phase 2 is usually taken.

Phase 1: before the integration is announced

Once an announcement goes out, people who know the old systems start to leave, and admin knowledge leaves with them. Capture the context while it is still in the building.

ConfirmOwnerIf skipped
The list of systems the plan will retire, each with its contract end date taken from the contractIntegration leadDates are guessed from renewal emails and the real window is missed
Who holds admin rights to each system, with a named backupIT leadThe one admin resigns and nobody can run a full export
First year of data held in each systemControllerThe oldest years are not noticed until they are gone
Field definitions, custom fields and picklist values documentedSystem owners, coordinated by the IT leadExported records are codes nobody can decode
Which teams created the records and still use themIntegration leadThe people who can explain exceptions are not asked

The archive context item is the one most plans leave out. A CRM export without its picklist values, or a ticketing export without its workflow states and team mapping, keeps the data but loses the meaning.

Phase 2: before cutover

Cutover is when the business stops writing to the old system. Everything after it is preservation.

ConfirmOwnerIf skipped
The vendor's post-termination window, read from the vendor's own documentationIT leadThe window is assumed and turns out shorter
The export method and format, including attachmentsIT leadAttachments or history are left behind
Contract limits on the records flaggedGeneral counselLater use is planned on records the company may not be free to use
CEO decision recorded: export, then review in the value creation plan, park or closeCEOPreservation happens by accident or not at all
A test export opened and checked against the context documentsIT lead with a system ownerProblems surface only after switch-off

The decision row is usually taken in a short meeting; see the records meeting agenda. The post-merger integration checklist and Day 1 readiness cover the wider workstreams around it.

Phase 3: before the old system is switched off

The last phase is short and unforgiving: after switch-off and the vendor window, there is nothing to recover.

ConfirmOwnerIf skipped
Full export complete and verified by someone who can read itIT leadA partial export is discovered too late
Context package stored with the export: definitions, mappings, workflow statesIT leadThe archive cannot be interpreted later
Storage location and access owner for the archive recordedControllerThe archive exists but nobody can find it
Line in the 100-day plan close-out stating what was keptIntegration leadThe value creation plan review has nothing to start from
Cancellation notice sentControllerSent too early, it starts the vendor clock before the export is safe

The cancellation notice is last on purpose. Atlassian's retention period, for example, runs from cancellation, so the notice, not the internal decision, starts the clock. The 100-day plan template has a close-out section for the record line.

Vendor windows that set the real deadline

Three published defaults, checked on 2026-10-18, show how much windows vary. They are examples, not the company's terms; enterprise agreements can differ.

VendorPublished window after the contract endsWhat happens after
SalesforceData return may be requested within 30 days of termination, as CSV with attachments in native formatData held inactive, then deleted
Atlassian cloudPaid sites retained 60 days after cancellation (15 days for trial sites)Permanently deleted, no recovery
Microsoft 365Limited-function account for 90 days so data can be extractedAccount disabled and data deleted, no more than 180 days after expiry

Work backward from the shortest relevant window. For Jira and Confluence specifically, see exporting Jira and Confluence before canceling.

Where a licensing conversation fits, if at all

The checklist protects records; it does not decide what happens to them. If the CEO later wants to explore licensing, an operating partner with a SourceX referral relationship discloses it first and introduces the CEO only on an opt-in. Introduced companies need 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. Only metadata is shared: record types, years, systems and owners. What stays unknown until SourceX reviews the company: buyer interest, the rights review result and any offer.

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 preserves an archive the CEO wants assessed, register as a partner before introducing anyone, confirm the company against who qualifies, and share the program terms as part of your disclosure.

  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

What is archive context, and why is it separate from the export?

It is everything needed to read the records later: field definitions, picklist values, user and team mappings, workflow rules and how attachments link to records. An export without it is a pile of codes nobody can interpret once the old system and its admins are gone.

Are the vendor windows on this page the deadline?

No. They are published defaults checked on 2026-10-18. The company's own contract can differ, so the IT lead confirms the window in the actual agreement.

Does completing the checklist commit the company to licensing anything?

No. It preserves records and their meaning. Whether to explore licensing is a separate CEO decision, and an introduction happens only if the CEO opts in.

Sources

  1. salesforce.com/en-us/wp-content/uploads/sites/4/documents/l…
  2. atlassian.com/licensing/cloud
  3. learn.microsoft.com/en-us/compliance/assurance/assurance-data-re…
  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