# Vendor selection archive context checklist | SourceX

Canonical: https://refer.sourcex.si/resources/vendor-selection-archive-context-checklist
Last updated: 2026-11-04

The decisions that vanish are the ones written on closed transactions: overrides, credit-hold releases, accepted variances, out-of-policy returns and write-offs, each with a reason and an approver. A clean-data scope leaves them in the legacy ERP. This checklist places that history on a countdown with three milestones: before the vendor decision is announced, before cutover, and before the old ERP is switched off. Each item says what to confirm, who confirms it, and what happens if nobody does.

It supports the [ERP vendor selection playbook](/guides/moment-vendor-selection-erp-selection-advisors). The owner conversation that starts it is the [30-minute vendor selection meeting](/resources/vendor-selection-meeting-agenda); this page is what you keep working from afterward.

## How the countdown is built

The checklist runs backward from one event: the day the legacy ERP stops being available, whether that is a decommission date, the end of a hosting contract or the end of a read-only period. Some selections never reach that day because the old system stays readable. When that is the case, the checklist is short.

Every row is metadata. It records exception types, rough volumes, years held, the system and the person who can speak for it. No row asks for a report extract, a sample transaction or a login.

Three columns repeat at each milestone:

- **Confirm:** one fact, in a line.
- **Owner:** the person at the company who can state or decide it.
- **If skipped:** the default outcome when nobody acts. For exception history, the default is that it stays in the old system and is retired with it.

## Milestone one: before the vendor decision is announced

Once a vendor is chosen, the project moves fast toward implementation, and scope documents get written by people focused on day-one operations. Confirm the shape of the history while the selection team still sees the whole landscape.

| Confirm | Owner | If skipped |
|---|---|---|
| The date or event driving the selection | CEO or CFO | Nobody knows whether the old ERP will be switched off or left running |
| The proposed migration scope, in one sentence | Controller | Exclusions are discovered at data load |
| Which exception types carry a reason code, note or approver | Controller with process owners | Exception history is treated as ordinary closed data |
| Years held for each exception type | Controller | The size of what is left behind is unknown |
| Who can speak for each type | Controller | Rows without owners stay undecided |

Dated platform events are the most common drivers. Microsoft has announced the end of support for Dynamics GP, with security updates available until April 30, 2031. SAP lists mainstream maintenance for SAP ERP 6.0 enhancement packages 6 to 8 through the end of 2027, with optional extended maintenance until the end of 2030 at a premium. Write down the event the company names, and its date, at this milestone.

## Milestone two: before cutover

Cutover is when the new ERP becomes the system of record. By then the migration scope is signed and the data loads are rehearsed. Confirm what the scope actually leaves behind, using the company's own words.

| Confirm | Owner | If skipped |
|---|---|---|
| Final scope, compared with the milestone-one sentence | Controller | A late scope cut removes more history than anyone agreed |
| Exception types fully excluded, partly carried or summarized | Controller | "Summary balances only" hides years of reasons and approvers |
| Satellite tools that hold approvals outside the ERP | IT lead | Approvals in email or workflow tools are forgotten entirely |
| Whether customer or supplier contracts limit reuse of transaction records | General counsel | Rights questions surface only after an owner decision |
| The person who decides where exception history goes | CEO or CFO | The decommission date decides instead |

Illustrative. For a 310-person industrial distributor with a scope of "clean data plus two years of closed invoices", this milestone recorded five exception types left behind: price overrides (11 years), credit-hold releases (9 years), accepted three-way-match variances (11 years, only two carried), out-of-policy returns (8 years) and bad-debt write-offs (11 years, summary balances only). The CFO was named as decision-maker.

This is also where the optional referral question fits, if the [meeting agenda](/resources/vendor-selection-meeting-agenda) has not already covered it. Disclose first: you are a SourceX referral partner and may receive a reward if a qualifying license completes; SourceX funds it separately and it never reduces the company's payment. Then ask whether the owner wants an introduction.

## Milestone three: before the old ERP is switched off

The last milestone confirms that a decision was made and acted on while the old system was still reachable.

| Confirm | Owner | If skipped |
|---|---|---|
| The read-only period and the decommission date | IT lead | The hosting contract ends and access goes with it |
| The archive approach chosen for exception history, if any | Controller | History is assumed archived when it was not |
| Statutory retention covered separately from exception history | Controller with counsel | Legal minimums are mistaken for the full scope |
| A recorded owner decision: keep, delete or review for licensing | CEO or CFO | The switch-off makes the decision |
| Where the decision record is filed | CFO's office | Nobody can later show who decided and when |

### Why statutory retention is its own row

Retention rules set a floor, not a scope. The IRS generally suggests keeping records for three years and employment tax records for at least four. A company may hold eleven years of exception history and be under no duty to keep most of it, so legal retention never answers the question of what happens to the rest. For archiving options, see [legacy ERP data archiving](/guides/legacy-erp-data-archiving).

### The only flag to raise

If the decommission date is close and the owner-decision row is blank, say so plainly. That urgency comes from the company's own verified date, never from anything SourceX sets.

## Reading the finished checklist

A complete checklist gives the owner one line per exception type: years held, whether it is carried, who speaks for it, and when the old system goes dark. It does not say whether the history is worth anything to anyone. Only a SourceX review can assess that.

If the owner opts in, confirm the baseline: 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. The [vendor selection introduction email](/resources/vendor-selection-introduction-email) is the next step.

Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application. Unknown until SourceX reviews it: dataset fit, the rights review result and any offer. The [software selection consultant page](/for/software-selection-consultant), the [NetSuite implementation checklist](/resources/netsuite-implementation-checklist) and the [CRM migration handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-crm-migration) cover neighboring stages.

## 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 years of exception history and the owner opts in before the old ERP is switched off, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the decision-maker.

## Sources

- https://www.microsoft.com/en-us/dynamics-365/blog/it-professional/2024/09/25/announcing-end-of-support-for-dynamics-gp/
- https://support.sap.com/en/offerings-programs/strategy.html
- https://www.irs.gov/businesses/small-businesses-self-employed/how-long-should-i-keep-records
- https://refer.sourcex.si/terms
