What happens to decades of order history when an IBM i (AS/400) is retired?
When an IBM i (AS/400) is retired, closed-order and exception history often stays behind unless someone exports it. ERP consultants should ask about years held, exportability and rights before cutover, preserve a tested copy, and introduce qualifying companies to SourceX for a licensing screen.
What is at stake when an IBM i (AS/400) system is retired?
The platform often holds the longest unbroken record of how a distributor or manufacturer took orders, shipped goods, handled exceptions and billed customers, sometimes spanning decades. When replacement is approved, the project plan usually migrates master data and open transactions. Closed-order history, exception notes and the reasoning behind overrides are frequently left on the old machine, and the old machine is then powered down.
This page is a trigger playbook for ERP consultants. It shows when to ask about that history, who to ask, what the company should preserve, and how to introduce a qualifying company to SourceX without touching its data. Nothing here assumes you work on IBM i yourself; the same questions apply whatever platform you are replacing.
What does an IBM i system usually hold?
The system names and library layouts differ by company, so ask rather than assume. Common contents in distribution and manufacturing:
| Area | Typical records | Why they may be useful to AI buyers |
|---|---|---|
| Order entry and fulfillment | Orders, changes, backorders, ship dates, returns | Long sequences of requests, changes and outcomes |
| Inventory and purchasing | Receipts, adjustments, reorder decisions, vendor delays | Planning decisions measured against results |
| Pricing and customer terms | Price changes, special quotes, credit holds | Commercial decisions with reasons |
| Accounts receivable and payable | Invoices, disputes, write-offs | Exception handling over time |
| Custom green-screen programs and notes | Business rules written into code and comments | Process logic, though often hard to export |
| Spooled reports and print files | Historical reports and statements | Snapshots of how the business was reported |
Decades of history help, but only when the data is intact and exportable. Old character encodings, custom file layouts and missing documentation are common. Ask the in-house or contract developer who knows the system whether a full export is practical.
What should a consultant ask before retirement?
Work through these in discovery, and again at cutover planning.
- Span: the first and last date of transactions in the system, and any years already purged.
- Neighbors: the other systems that explain the transactions, such as email, a CRM, a warehouse system, EDI logs or a finance package.
- Exportability: whether someone can produce a full export, in what form, and how long it would take.
- Knowledge risk: who understands the file layouts, and whether that person is retiring.
- Rights: whether the records are the company's own, or include customer-supplied data restricted by contract.
- Decision owner: the owner, CEO or CFO who can decide what happens to the old system's data.
- Shutdown date: the planned power-off, and whether a read-only copy will survive it.
The shutdown timeline
| Point in the project | What to do | Who decides |
|---|---|---|
| Replacement approved | Ask what history will not migrate | CFO or owner |
| Vendor selected, scoping | Add an "archive or preserve" line to the plan | Project sponsor |
| Mid-build | Confirm a full export has been tested and stored under company control | IT lead |
| Two to three months before cutover | Raise licensing if the history is deep and rights look clear | Owner or CEO |
| Cutover | Keep the machine and export untouched until the decision is made | IT lead |
| Post go-live | Release hardware only after written approval | Owner |
Move the licensing conversation early enough to avoid being the reason for a delay; it should never hold up a go-live. The same pattern works for a manufacturing ERP migration, an email archive cancellation and an office move.
Which companies on this platform are worth a screen?
Look for the following combination, which the who qualifies page summarizes:
- 50+ full-time employees at peak (contractors excluded).
- Several years of documented operations, ideally ten or more on the platform.
- Records in many systems, not just the order system.
- A company-owned dataset rather than data held on behalf of customers.
- An authorized sponsor willing to consider a one-time payment for an exclusive AI-training license for an agreed term.
The company fit checker provides a preliminary, non-binding screen with no contact details required. For the conversation about wider records, the referral opportunities for ERP consultants page explains where this fits in your practice.
What to say to the CFO or owner
The introduction email builder can turn that into an owner-approved introduction.
How the introduction and reward work
You introduce the company through the referral form or your referral link. SourceX qualifies it, the company completes a data inventory with its own staff, terms are agreed, buyers review, and the deal closes only if the company signs. You never export, upload or describe confidential records.
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It is a share of SourceX's fee and is never deducted from what the company receives. Check your consulting agreements for any disclosure duty, and read the program terms.
Limits and red flags
- The company has fewer than 50 full-time employees at peak.
- Data is mostly consumer personal information or customer-owned.
- The system has already been shut down and the data cannot be exported.
- The records were already licensed for AI training.
- A court, trustee or assignee controls the assets and has not been involved. See winding down a company without losing its records.
Next step
Add an "archive or preserve" line to your next replacement plan. If the history is deep and the sponsor is open, register as a partner and introduce the company, or send the sponsor to sourcex.si/apply with your referral link.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Is IBM i data too old or unusual to be useful?
Age and format do not rule it out, but exportability matters. Old encodings and custom layouts add work, and the data must be readable by someone. Decades of consistent order and exception history can be valuable if it can be exported and its rights are clear. The company's inventory records what is feasible.
Should the machine be kept running after cutover?
Until the company decides what to do with the history, keep the system or a tested full export intact. Powering off without a verified export can make recovery costly or impossible. The retention decision belongs to the owner, and hardware should be released only after written approval.
Who should ERP consultants talk to about this?
The owner, CEO or CFO, since they decide what happens to company records and can authorize a license. Your day-to-day contact, often an IT or operations lead, can supply the facts, such as years on the platform and who can export, but cannot normally sponsor the opportunity.
Can customer-specific data on the system be licensed?
Only if the company has the right. Customer-supplied data, special pricing under confidentiality terms and regulated information may be restricted. SourceX performs a rights review with the company, and counsel should confirm. The company's own operational history is the cleaner core of an opportunity.
Does raising licensing risk delaying the replacement project?
It should not. The conversation can run in parallel and needs little from the project team beyond preserving an export. If the sponsor wants to focus on go-live, wait until after cutover, as long as the old system and export are not discarded.
Related pages
- Referral opportunities for ERP consultants
- How to wind down a company: an orderly plan that keeps the records
- Manufacturing ERP migration: which legacy job and quality records are worth a screen?
- Office relocation IT checklist: decide what to do with old data before the move
- What happens to your email archive when you cancel the service?
- Check Company Fit for Data Licensing
Free resources
- Profit margin calculator — Profit and margin across three scenarios.
- Client opportunity brief generator — An editable intro email, summary and checklist.
- Days sales outstanding calculator — How many days customers take to pay.
- All free tools · MCP resource center
By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09
Know a US company with valuable proprietary data?
Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.
Refer a company →I own a business
Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.
Start an assessment