# 100-day plan archive context checklist | SourceX

Canonical: https://refer.sourcex.si/resources/first-100-day-plan-archive-context-checklist
Last updated: 2026-11-04

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.

This checklist belongs with the comparison of a [value creation plan and a 100-day plan](/compare/value-creation-plan-vs-100-day-plan). The [30-minute records meeting agenda](/resources/first-100-day-plan-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.

| Confirm | Owner | If skipped |
|---|---|---|
| The list of systems the plan will retire, each with its contract end date taken from the contract | Integration lead | Dates are guessed from renewal emails and the real window is missed |
| Who holds admin rights to each system, with a named backup | IT lead | The one admin resigns and nobody can run a full export |
| First year of data held in each system | Controller | The oldest years are not noticed until they are gone |
| Field definitions, custom fields and picklist values documented | System owners, coordinated by the IT lead | Exported records are codes nobody can decode |
| Which teams created the records and still use them | Integration lead | The 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.

| Confirm | Owner | If skipped |
|---|---|---|
| The vendor's post-termination window, read from the vendor's own documentation | IT lead | The window is assumed and turns out shorter |
| The export method and format, including attachments | IT lead | Attachments or history are left behind |
| Contract limits on the records flagged | General counsel | Later 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 close | CEO | Preservation happens by accident or not at all |
| A test export opened and checked against the context documents | IT lead with a system owner | Problems surface only after switch-off |

The decision row is usually taken in a short meeting; see the [records meeting agenda](/resources/first-100-day-plan-meeting-agenda). The [post-merger integration checklist](/resources/post-merger-integration-checklist) and [Day 1 readiness](/guides/day-1-readiness-m) 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.

| Confirm | Owner | If skipped |
|---|---|---|
| Full export complete and verified by someone who can read it | IT lead | A partial export is discovered too late |
| Context package stored with the export: definitions, mappings, workflow states | IT lead | The archive cannot be interpreted later |
| Storage location and access owner for the archive recorded | Controller | The archive exists but nobody can find it |
| Line in the 100-day plan close-out stating what was kept | Integration lead | The value creation plan review has nothing to start from |
| Cancellation notice sent | Controller | Sent 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](/resources/100-day-plan-template-private-equity) 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.

| Vendor | Published window after the contract ends | What happens after |
|---|---|---|
| Salesforce | Data return may be requested within 30 days of termination, as CSV with attachments in native format | Data held inactive, then deleted |
| Atlassian cloud | Paid sites retained 60 days after cancellation (15 days for trial sites) | Permanently deleted, no recovery |
| Microsoft 365 | Limited-function account for 90 days so data can be extracted | Account 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](/systems/export-jira-and-confluence-before-cancelling).

## 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](/register) before introducing anyone, confirm the company against [who qualifies](/who-qualifies), and share the [program terms](/terms) as part of your disclosure.

## Sources

- https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/misc/salesforce-security-privacy-and-architecture.pdf
- https://www.atlassian.com/licensing/cloud
- https://learn.microsoft.com/en-us/compliance/assurance/assurance-data-retention-deletion-and-destruction-overview
- https://refer.sourcex.si/terms
