Vendor selection archive context checklist: confirming exception history before the old ERP is switched off

Short answer

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.

Visual briefFull-size diagram
A vertical countdown from vendor decision to cutover to legacy ERP off, with checklist items ticking green beside each milestone and one unowned item turning orange just before the old system is switched off.
Illustrative milestones and items. The company's own selection plan, contracts and support dates set the real timeline.

It supports the ERP vendor selection playbook. The owner conversation that starts it is the 30-minute vendor selection meeting; 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.

ConfirmOwnerIf skipped
The date or event driving the selectionCEO or CFONobody knows whether the old ERP will be switched off or left running
The proposed migration scope, in one sentenceControllerExclusions are discovered at data load
Which exception types carry a reason code, note or approverController with process ownersException history is treated as ordinary closed data
Years held for each exception typeControllerThe size of what is left behind is unknown
Who can speak for each typeControllerRows 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.

ConfirmOwnerIf skipped
Final scope, compared with the milestone-one sentenceControllerA late scope cut removes more history than anyone agreed
Exception types fully excluded, partly carried or summarizedController"Summary balances only" hides years of reasons and approvers
Satellite tools that hold approvals outside the ERPIT leadApprovals in email or workflow tools are forgotten entirely
Whether customer or supplier contracts limit reuse of transaction recordsGeneral counselRights questions surface only after an owner decision
The person who decides where exception history goesCEO or CFOThe 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 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.

ConfirmOwnerIf skipped
The read-only period and the decommission dateIT leadThe hosting contract ends and access goes with it
The archive approach chosen for exception history, if anyControllerHistory is assumed archived when it was not
Statutory retention covered separately from exception historyController with counselLegal minimums are mistaken for the full scope
A recorded owner decision: keep, delete or review for licensingCEO or CFOThe switch-off makes the decision
Where the decision record is filedCFO's officeNobody 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.

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 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, the NetSuite implementation checklist and the CRM migration handoff checklist 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, confirm the company on who qualifies, and read the program terms before you introduce the decision-maker.

  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

Is this checklist a substitute for a data migration plan?

No. The migration plan decides what moves. This checklist only makes sure the company has decided, on purpose and with a named owner, what happens to the exception history the plan leaves behind.

Do statutory retention rules tell us what to keep?

They set a floor, not a scope. The IRS generally suggests keeping records for three years and employment tax records for at least four, but a company may hold a decade of exception history it is under no duty to keep. The checklist asks who decides about the rest.

Who fills in the checklist?

The selection advisor keeps it, and the company supplies every answer. Each row names the person at the company who confirms it.

Sources

  1. microsoft.com/en-us/dynamics-365/blog/it-professional/2024…
  2. support.sap.com/en/offerings-programs/strategy.html
  3. irs.gov/businesses/small-businesses-self-employed/ho…
  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