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.
| When | Rollout event | What the consultant asks about |
|---|---|---|
| Cutover -12 months | Kickoff and system selection | Which record classes exist and where |
| Cutover -9 months | Data migration scope drafted | Open orders only, or closed history too |
| Cutover -6 months | Mapping and test loads | Whether change history and cross-references map to the new platform |
| Cutover -1 month | Final load rehearsal | What stays on the old system |
| Cutover | New platform live | Who still has read access to the old system |
| Cutover +6 months | Old ERP hosting or license ends | Nothing 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.
| Order | Record class | Why it tends to go early | What remains if it is lost |
|---|---|---|---|
| 1 | CRM field history on edited approvals | Standard history has a fixed retention window | The current field value only |
| 2 | Approvals and site feedback in personal inboxes | Mailboxes are removed when staff leave | Nothing, unless forwarded to a shared mailbox |
| 3 | ERP order change history | Often not migrated; only current order state moves | Shipped lines, with no record of what was canceled |
| 4 | Closed orders and backorder lines | Rollouts load open orders first | Invoices and credits, held for tax |
| 5 | Substitution cross-references | Rebuilt in the new item master, sometimes without history | Today'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.
- Record class. Backorder lines, substitution cross-references, order change history, shipments, returns and credits; CRM call logs and tasks; approval and site feedback email.
- Time coverage. How many years of closed orders and change history the old system holds, and whether earlier years were archived elsewhere.
- Migration scope. What the scope document says moves.
- System owner. Who administers the ERP, the CRM and the shared mailboxes, and who in the business owns each class.
- Access deadline. The date read access ends, from the license or hosting contract. If no one can name it, record that.
- Volume, roughly. Substituted lines per year, from a report.
- 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.