Systems and records
Retiring a legacy WMS: which history to keep
By SourceX Editorial · Updated
Short answer
When retiring a legacy WMS, keep the history that explains inventory and service outcomes: orders and shipments, picks, receipts, inventory adjustments with reason codes, exceptions and labor records. Give each a named reason, such as client billing, claims, audits or analysis. Drop system logs, print queues and temporary tables, which explain nothing once the system is gone.
Key takeaways
- Keep orders, picks, receipts, adjustments, exceptions, returns, labor and billing events; drop logs, print queues and staging tables.
- Every record family on the keep list needs a written retention reason and a named owner.
- Export order numbers, license plates, lots, locations, reason codes, client IDs and user IDs so the archive still joins.
- In 3PL warehouses, client contracts can decide who owns inventory and order records at the end of the relationship.
- Exception records with supervisor notes are the most useful history and the most likely to contain personal details.
Which WMS history should you keep?#
Keep the legacy WMS history that explains what happened to inventory and to customers: orders and shipments, picks, receipts, adjustments, exceptions and labor. Each of those record families answers questions that keep coming after cutover, from client billing disputes to inventory audits, and each one needs a named reason for being kept.
Keep transaction-level detail rather than summary snapshots. A monthly accuracy figure cannot be traced back to the picks behind it, while the picks can always be summarized again.
| Record family | What it holds | Why keep it |
|---|---|---|
| Orders and shipments | Order lines, ship confirmations, carriers, tracking, ship dates | Customer disputes, chargebacks, service history |
| Picks | Pick tasks, short picks, substitutions, pick locations | Accuracy analysis, slotting, mis-ship investigations |
| Receipts and putaway | Advance ship notice versus received quantities, damages, putaway locations | Supplier claims, receiving accuracy, lot tracing |
| Inventory adjustments and counts | Reason codes, user, approver, cycle count results | Shrink analysis, financial audit, inventory valuation support |
| Exceptions and holds | Damages, quality holds, mis-picks, refused deliveries, supervisor notes | Root cause work and the clearest record of how problems were solved |
| Returns | Return authorizations, inspection results, disposition | Credit disputes, vendor returns, product quality trends |
| Labor and tasks | Task times, zones, equipment, user IDs | Labor standards, staffing models, safety reviews |
| Billing events | Storage, handling and value-added service charges by client | Client invoice disputes in 3PL operations |
What you can safely drop#
System noise is what you can safely drop when a WMS retires: records that describe how the software ran rather than what the warehouse did. Dropping them makes the archive smaller, cheaper to store and easier to query.
Be careful with the last item on the list below. Teams often assume the ERP holds shipment detail, then discover it kept only invoice-level totals while line-level picks, lots and serial numbers lived in the WMS.
- Interface and error logs, once reconciliation for the final period is complete.
- Label and document print queues.
- Staging and temporary tables used during wave planning or allocation.
- User session and screen-access logs, unless security or HR has a reason to keep them.
- Duplicates of records held completely in the ERP, after confirming the ERP copy really is complete.
Name a retention reason and an owner for every record family#
A retention reason is what protects a record family from deletion at the next budget review, so write one down for each item on the keep list along with the person who owns it. Without a reason and an owner, archives get trimmed by whoever pays for storage.
Reasons usually fall into a few groups: client and customer contracts, financial audit and tax support for inventory, claims and disputes, labor and safety, and operational analysis. Your accountant, counsel and client contracts set the minimums; operations decides whether more history is worth keeping for slotting, labor standards and network planning.
For third-party logistics operations, client contracts come first. Some agreements treat inventory and order records as the client's data and require return or deletion when the relationship ends, while your own labor and process records may be treated differently. Read those clauses before archiving or reusing anything.
Keep the keys that join WMS records together#
The keys that join WMS records together matter more than any single table, because an archive of orders, picks and receipts that no longer link cannot answer the questions it was kept for.
Export code lists and masters with effective dates as well. Reason codes, location names and item numbers change over the life of a WMS, and an adjustment coded with a reason that no longer exists is just a number.
| Key | What it connects | What breaks without it |
|---|---|---|
| Order and line number | Order to picks, shipments and returns | Tracing a mis-ship back to the pick |
| License plate number | Pallet or carton through receipt, putaway, moves and pick | Following a damaged pallet's path |
| Lot and serial number | Received goods to shipped goods | Recalls and quality holds |
| Location ID | Inventory to physical slots | Slotting history and count variances |
| Reason code | Adjustments and exceptions to their cause | Any root cause analysis |
| Client ID | Every record to the 3PL client it belongs to | Contract-by-contract handling |
| User ID | Tasks to the person or device that did them | Labor analysis and investigations |
WMS cutover checklist for historical data#
The WMS cutover checklist for history runs alongside the conversion plan, not after it, because the people who understand old reason codes and custom tables are easiest to reach before go-live pulls them onto the floor.
- Inventory every table, interface and custom report the legacy WMS uses.
- Mark each record family keep, archive or drop, with a reason and an owner.
- Freeze masters and code lists at cutover and export them with effective dates.
- Export closed transactions to open formats, keeping the original keys.
- Reconcile record counts and on-hand balances across the legacy system, the archive and the new WMS.
- Trace sample units from receipt to putaway, pick, shipment and return in the archive.
- Confirm client-data handling for each 3PL client contract.
- Store export logs and sign-offs with the archive.
- Set a shutdown date for the legacy system tied to a milestone, such as a clean physical count.
Illustrative: an electrical supply wholesaler retires an unsupported WMS#
Illustrative: a fictional electrical supply wholesaler runs two warehouses on an on-premises WMS whose vendor has ended support. The VP of operations is moving to a cloud WMS, and the integrator's plan converts only open orders, items, locations and on-hand balances.
Using the keep list, the team archives closed orders, picks, receipts, adjustments with reason codes, exceptions with supervisor notes and labor tasks. Labor records carry user IDs, with the mapping to employee names held by HR. Interface logs and print queues are dropped after the final reconciliation.
After go-live, a supplier disputes a run of shortage claims. Receiving history in the archive shows advance ship notice quantities against counted quantities for every affected receipt, and the dispute closes on the record. The slotting team later uses archived pick history to redesign fast-mover locations.
How SourceX looks at retired WMS history#
Retired WMS history is most useful outside the warehouse when it links exceptions to the decisions that resolved them: a short pick, the supervisor's note and the adjustment that followed. AI developers working on logistics operations look for that kind of human-generated, outcome-linked record, and generic transaction feeds rarely contain it.
SourceX starts with a fit check built on metadata alone and then follows the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Client-owned records are excluded unless the contracts allow use, employee and customer details are removed during preparation, and the company approves each step. The warehouse operator licenses the records and keeps ownership, and large archives stay in its own storage or ship on encrypted drives.
Frequently asked questions
Should we migrate WMS history into the new system instead of archiving it?
Usually only a short recent window, if any. A new WMS is built around current inventory and open work, and loading years of closed transactions adds conversion effort and testing. Most teams convert open orders, masters and on-hand balances, then archive closed history where reporting tools can query it.
How should we handle labor records that identify employees?
Treat them as personnel data. Keep them for the reasons HR, safety and payroll name, restrict access, and consider replacing names with stable user IDs in the analytical copy while HR holds the mapping. Employment and privacy laws may apply, so confirm handling with HR and counsel.
What format should a WMS archive use?
Open, queryable formats: delimited text or Parquet files, or a read-only reporting database, with a data dictionary and code lists. Avoid an archive that can only be read by restoring the legacy application, because the server, licenses and know-how needed to do that fade quickly after cutover.
How long should the legacy WMS keep running after go-live?
Only until the archive is verified and the first post-cutover period closes cleanly. Running two systems costs licenses, servers and attention, and the fallback rarely gets used. Tie the shutdown to a milestone, such as a completed physical count or period-end close, rather than leaving it open-ended.
Do exception notes written by supervisors need special handling?
Yes. Free-text notes are the most useful part of exception history and the most likely to contain names, phone numbers or remarks about customers and employees. Keep them in the archive, restrict access, and plan for review or redaction before any reuse outside daily operations.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.