Before an inventory platform rollout: a retention timeline for backorder substitution history

Short answer

Before an inventory platform rollout, list each substitution record class, the years it covers, the system and team that hold it, what the migration plan says moves, and the real date read access to the old system ends. Then record the company's own retention rule for each class. A rollout usually migrates item masters, open orders and current balances. Closed orders, order change history, substitution cross-references and the CRM notes and emails tied to them are the parts most often left behind, and some go before the rollout starts.

Visual briefFull-size diagram
A horizontal timeline from rollout kickoff to old ERP shutdown, with five record bars, CRM field history, personal inbox approvals, order change history, closed orders and substitution cross-references, fading at their cutoffs; an inventory marker at month minus 9 comes before most of the losses.
Illustrative: a fictional rollout timetable. Bars fade where that history goes out of reach unless the company decides otherwise.

This timeline is part of the backorder substitution decisions guide. It is written for distribution ERP consultants who see a rollout plan months before cutover.

The rollout timeline, from kickoff to old system shutdown

Every rollout runs to a cutover date and an end of read access. The schedule below is Illustrative: a fictional 350-person building products distributor moving to a new inventory and order platform, not a real project.

WhenRollout eventWhat the consultant asks about
Cutover -12 monthsKickoff and system selectionWhich record classes exist and where
Cutover -9 monthsData migration scope draftedOpen orders only, or closed history too
Cutover -6 monthsMapping and test loadsWhether change history and cross-references map to the new platform
Cutover -1 monthFinal load rehearsalWhat stays on the old system
CutoverNew platform liveWho still has read access to the old system
Cutover +6 monthsOld ERP hosting or license endsNothing new; the inventory should exist

The best moment for the inventory is when migration scope is still a draft, around cutover -9 months. Ask for the scope document itself, not an opinion about it.

What is lost first, and why

Substitution history does not leave in one block. Some record classes go long before cutover. This order is a pattern to check, not a rule.

OrderRecord classWhy it tends to go earlyWhat remains if it is lost
1CRM field history on edited approvalsStandard history has a fixed retention windowThe current field value only
2Approvals and site feedback in personal inboxesMailboxes are removed when staff leaveNothing, unless forwarded to a shared mailbox
3ERP order change historyOften not migrated; only current order state movesShipped lines, with no record of what was canceled
4Closed orders and backorder linesRollouts load open orders firstInvoices and credits, held for tax
5Substitution cross-referencesRebuilt in the new item master, sometimes without historyToday's substitute list

The first row has a documented cause. Salesforce, for example, states that standard field history data is retained for 18 months in the user interface and is available for up to 24 months via the API, unless a longer-retention add-on is used. An approval edited three years ago may already have lost its earlier values, rollout or not.

How long each class is kept: the rules that pull in different directions

No single period applies to substitution records. Two kinds of rule pull in different directions, and the inventory records which one governs each class.

Tax and accounting records are kept at least as long as the law requires. In the U.S., the IRS says to keep records that support an item of income, deduction or credit until the period of limitations for that return runs out; the general period is three years, longer in specific situations, and at least four years for employment tax records. Invoices and credit memos tied to substituted orders usually sit here.

Personal data is kept no longer than needed. The UK regulator's storage limitation guidance says organizations should be able to justify retention by purpose and, where practical, set standard periods in a retention schedule. Customer contact names on approvals and call logs usually sit here.

Call logs, change history and site feedback often have no explicit rule at all, which is exactly why they are the classes most likely to be left behind. The inventory notes that; it does not invent a period.

The inventory checklist: metadata only

Ask for these facts per record class. Never ask for orders, emails or exports.

  1. Record class. Backorder lines, substitution cross-references, order change history, shipments, returns and credits; CRM call logs and tasks; approval and site feedback email.
  2. Time coverage. How many years of closed orders and change history the old system holds, and whether earlier years were archived elsewhere.
  3. Migration scope. What the scope document says moves.
  4. System owner. Who administers the ERP, the CRM and the shared mailboxes, and who in the business owns each class.
  5. Access deadline. The date read access ends, from the license or hosting contract. If no one can name it, record that.
  6. Volume, roughly. Substituted lines per year, from a report.
  7. Retention rule. The schedule that applies to the class, or "none written".

If the rollout follows an acquisition, the Day 1 readiness guide explains why the only early decision is a hold on irreversible shutdowns. An MCP connection may make the inventory faster; see MCP for ERP consulting. For mailboxes, the difference between an archive and a backup matters; see email archive versus backup.

Who approves keeping history the plan leaves out

Keeping anything beyond the migration plan is a decision for people with authority over the records, not for the project team. The ERP administrator can configure an archive; the sales operations director can recommend; counsel checks customer contracts and personal data; the COO or CFO approves, sometimes with the CEO. The partner's inventory is information for those people. Do not recommend keeping anything the company has no authority or reason to keep. The who-can-say-yes tree covers the licensing side, where the CEO authorizes a discussion and signs, and the system map shows which joins the inventory should protect.

The introduced company needs 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. Partners sign the Channel Partner Agreement before submitting introductions. Whether preserved history can be licensed and whether any buyer wants it stays unknown until SourceX reviews it. SAP partners can see the SAP partner referral page, and sector context is in wholesale distribution data.

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 inventory shows years of closed orders and substitution history with a documented end to old-system access, register as a partner, check the distributor on who qualifies and read the program terms before raising it with the sales operations director.

  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

Does a tax retention period mean the substitution history will be kept?

Not necessarily. Tax rules cover records that support figures on a return, such as invoices and credits. CRM call logs, approval emails and order change history may fall outside them, so the inventory should record each class's own rule rather than assume the longest one applies.

Is an email backup the same as keeping the approvals?

Not always. A backup restores systems after a failure; an archive keeps messages findable over time. Ask which one holds the shared mailbox, and see the explainer on email archive versus backup.

Sources

  1. refer.sourcex.si/terms
  2. trailhead.salesforce.com/content/learn/modules/field-audit-trail-basi…
  3. irs.gov/businesses/small-businesses-self-employed/ho…
  4. ico.org.uk/for-organisations/uk-gdpr-guidance-and-resou…

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