---
title: "SYSPRO Lot & Serial Traceability Migration: A Technical Guide"
slug: syspro-lot-and-serial-traceability-migration
date: 2026-10-26
author: Rishabh Makhar
categories: [SYSPRO, ERP, Migration Guide]
excerpt: "How to migrate SYSPRO lot traceability and serial tracking data to a new ERP, including archived lots, purged serials, and genealogy chain validation."
tldr: "SYSPRO lot and serial migration requires extracting live tables, finding archived lot transactions, and validating upstream-downstream genealogy chains in the target ERP."
canonical: https://clonepartner.com/blog/syspro-lot-and-serial-traceability-migration
---

# SYSPRO Lot & Serial Traceability Migration: A Technical Guide


Migrating lot and serial traceability data out of SYSPRO is the highest-stakes data domain in a manufacturing ERP transition. Financial records can be reconciled after go-live. Customer and supplier masters can be corrected. But if a lot genealogy chain breaks during migration — if you lose the link between a raw material lot, the job that consumed it, and the finished goods it became — you cannot reconstruct it. A single missing lot transaction can break a product recall audit. A misaligned serial status can block inventory from being picked in the new system.

For manufacturers in regulated industries (medical devices, food, pharma, aerospace), a broken traceability chain is not only a data quality issue. It is a compliance problem that can fail an audit.

This guide covers what SYSPRO actually stores for lot and serial traceability, how to extract it completely — including archived and purged records most teams miss — how it maps to target ERPs, and the validation steps that prove your traceability chain survived the move.

For extraction across all SYSPRO data domains, see the [SYSPRO SQL table map for data migration](https://clonepartner.com/blog/blog/syspro-sql-table-map-for-migration). If your migration is driven by the licensing change, read [SYSPRO Licence Change 2026: Deadlines Explained](https://clonepartner.com/blog/blog/syspro-licence-change-2026-deadlines-explained) first.

> [!WARNING]
> **SYSPRO licensing deadline:** SYSPRO is ending its Initial License Fee and Annual License Fee model. Existing licences expire on **31 October 2026** (outside the US) or **31 December 2026** (US). After your expiry date "you will no longer be able to access Syspro" unless you sign a new subscription. The notice confirms the right to export your data on cessation of your licence, and asks you to raise it with your account manager before the expiry date ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)). For the full list of tasks, see the [SYSPRO exit checklist](https://clonepartner.com/blog/blog/syspro-exit-checklist-before-licence-expiry).

## Why lot and serial data is the hardest domain to migrate

Lot and serial traceability data is structurally different from every other data domain in an ERP migration. A customer record is a flat row. A sales order is a header-detail pair. But a lot traceability chain is a **directed graph**: raw material lots flow into jobs, jobs produce finished goods lots, those lots ship against sales orders to specific customers, and inspection records attach at multiple points along the way.

"SYSPRO's Lot Traceability system lets you track an item through the manufacturing process, providing full traceability at transactional level" ([help.syspro.com](https://help.syspro.com/syspro-8-2021-r2/topics/distribution/lots/lots-ovr.htm)). "SYSPRO's Serial Tracking system lets you capture and maintain serial numbers for existing stock items held in the Inventory system" ([help.syspro.com](https://help.syspro.com/syspro-8-2021-r2/topics/distribution/serials/serials-ovr.htm)). These two systems interact — a stock code can be both lot traceable and serialised — and the migration must preserve every link.

SYSPRO's traceability query has a Search Up function, which "lets you establish what was used to manufacture the lot from the raw material", and a Search Down function, which "lets you establish where the lot number was used" ([help.syspro.com](https://help.syspro.com/syspro-8-2020-r2/topics/distribution/lots/lots-ovr.htm)). Your target ERP must reproduce this capability. If you simply export `InvMaster` and `InvWarehouse`, you migrate stock codes and total quantities but abandon the traceability. A compliant migration carries the exact lot numbers, lot dates, serial statuses, and the transaction chains tied to on-hand quantities.

## What does SYSPRO store for lot traceability?

SYSPRO 8 stores its data in Microsoft SQL Server. "Each SYSPRO 8 company database contains approximately 1000 tables", and the system-wide database "contains over 100 tables" ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/syspro-8-database-architecture-technical-guide.pdf)). Traceability data lives in the company database.

**Lot traceability in SYSPRO** is anchored to the `LotDetail` table, which holds lot detail for lot traceable items ([help.syspro.com](https://help.syspro.com/syspro-8-2024/g_programs/imp/impbla/impbla.htm)). The Lot Maintenance program ties a lot number to a stock code, warehouse and bin, and captures an expiry date, manufacturing date, dispatch date and best before date. SYSPRO uses the `OrigQtyReceived` column of `LotDetail` "as a control when receipting lot traceable items", so you can't return more than was originally received (same source). Migrate that value with the lot, or returns against migrated lots will behave differently in the new system.

The lot transaction history — the receipts, issues, sales and inspections behind each lot — is what powers the traceability query. SYSPRO's Traceability Query shows "details of lots and associated transactions including inspection and sales order details" ([help.syspro.com](https://help.syspro.com/syspro-7-update-1/lotpen.htm), SYSPRO 7 Update 1 help). Extract that transaction history alongside the lot headers, not just the headers.

Configuration matters. You can reuse the same lot number for different stock codes if the **Use same lot on multiple stock codes** setup option is enabled ([help.syspro.com](https://help.syspro.com/syspro-8-2024/g_programs/imp/impbla/impbla.htm)). If your source system uses this, every target mapping must treat the stock code as part of the lot's key, not the lot number alone.

## What does SYSPRO store for serial tracking?

**Serial tracking in SYSPRO** centres on the `InvSerialHead` table. SYSPRO's Serial Number Maintenance program maintains each serial's stock code, warehouse, serial type, expiry and scrap dates, and hold status. The `Hold` column of `InvSerialHead` shows an `H` for a serial on hold, and the `Prod-recall` column shows a `Y` for a serial that is part of a product recall ([help.syspro.com](https://help.syspro.com/syspro-8-2023/g_programs/inv/invpse/invpse.htm)). Serial transactions sit in a separate table, `InvSerialTrn` ([help.syspro.com](https://help.syspro.com/syspro-8-2026-r1/i-installation/sys-8-sql-updates-by-release/sys-8-sql-updates-by-release.htm)).

SYSPRO distinguishes between two serial types. "Manual serial indicates that each serial number represents an individual item. Batch serial indicates that a group of items have the same serial number" ([help.syspro.com](https://help.syspro.com/syspro-7-update-1/invpst.htm), SYSPRO 7 Update 1 help). This distinction matters during migration because the target ERP may not accept one serial number for several units. If your SYSPRO instance uses batch serials, check how your target handles them and decide how to represent grouped items. Make that decision during scoping, not during the data load.

In SYSPRO, "you cannot use the same manual serial number in two different warehouses" ([help.syspro.com](https://help.syspro.com/syspro-7-update-1/imp01s.htm), SYSPRO 7 Update 1 help). Check the target ERP's own uniqueness rule for serial numbers before you load, and test with serials that have moved between warehouses.

## The archived lot problem most teams miss

This is where most SYSPRO lot migrations go wrong. SYSPRO's lot **Purge and Archive** program copies "lot transactions and inspection records to an archive file as well as purge transaction details for lots that are complete". "The header record is never deleted from the lot master table; only the lot transactions are deleted and archived" ([help.syspro.com](https://help.syspro.com/syspro-8-2024/g_programs/lot/lotp01/lotp01.htm)).

In practice: if your operations team has run Purge and Archive at any point, your live `LotDetail` table has lot headers whose transactions are no longer in the live tables. The transaction history sits in archive files. In SYSPRO 7, that archive "is stored in C-ISAM format in the data directory, regardless of the company database format" ([help.syspro.com](https://help.syspro.com/syspro-7-update-1/imptrc.htm), SYSPRO 7 Update 1 help). SYSPRO 8's Archiving Migration program converts archived data, including the lot archive, "from SYSPRO 7 format to SQL in SYSPRO 8". SYSPRO also warns that "archived data will not be available in SYSPRO 8 until it has been converted using this program" ([help.syspro.com](https://help.syspro.com/syspro-8-2019-r1/resources/pdfs/syspro-8-archiving-migration-reference-guide.pdf)).

SYSPRO 8 2018 added SQL tables for lot archives, among them `LotArcTransact` ("Archived Lot Traceability Transactions") and `LotArcSerDet` ("Lot Archive Serial Detail") ([help.syspro.com](https://help.syspro.com/syspro-8-2026-r1/i-installation/sys-8-sql-updates-by-release/sys-8-sql-updates-by-release.htm)). Check whether these tables hold rows in your company database before you plan the extraction.

> [!CAUTION]
> **Check for archived lots before you start extraction.** If your team has ever purged completed lots, the transaction history for those lots is not in the live lot tables. Look for archive files and lot archive tables. The Purge and Archive program's **Restore Lot** option "re-establishes all the files that were previously archived for a lot", but SYSPRO notes "you cannot restore a lot that contains any serialized items" ([help.syspro.com](https://help.syspro.com/syspro-8-2024/g_programs/lot/lotp01/lotp01.htm)). If you skip this step, you will migrate lot headers with no history, and your traceability chain will have gaps.

SYSPRO's general archiving covers "Sales orders, Jobs, ECC bill of materials", and "No 'additional' attached information (such as custom forms, multimedia, notes, etc) is archived" ([help.syspro.com](https://help.syspro.com/syspro-7-update-1/ovr-archiving.htm), SYSPRO 7 Update 1 help). If lot-level custom form fields carry regulatory data (inspection results, certificate numbers, concession codes), do not assume that data is in any archive. Read it from the plus tables while SYSPRO is still live. For how to keep that history usable after go-live, see [how to archive SYSPRO history before switching ERP](https://clonepartner.com/blog/blog/how-to-archive-syspro-history-before-switching-erp).

A separate **Serial File Purge** program deletes serial numbers or serial transactions. For traceable items, SYSPRO says this program "deletes serial numbers and transactions for traceable items only once the lot has been archived". When a serialised lot is archived, its serial transactions for issues and sales are archived too, so "transaction records are retained even if the serial is deleted by the Serial File Purge program" ([help.syspro.com](https://help.syspro.com/syspro-8-2024/g_programs/lot/lotp01/lotp01.htm)). For serials that are not lot traceable, SYSPRO's help describes no such archive. Document what has been purged before you start, so stakeholders know the scope of what can and cannot be migrated.

## How to extract lot and serial data from SYSPRO

**For lot and serial data, we recommend a one-off, read-only SQL extract against a restored copy of the company database.** SYSPRO 8 stores each company's data in its own SQL Server database. Use a read-only SQL login against a backup, not the production database.

SYSPRO's own best-practice guide says: "Connecting to the SYSPRO databases directly using SQL drivers is not advised" ([help.syspro.com](https://help.syspro.com/syspro-8-2023/resources/pdfs/2023-release/technical/syspro-8-best-practices-for-connecting-to-syspro.pdf)). That warning is about live integrations. A one-off, read-only extract from a restored copy writes nothing to SYSPRO, and it reaches every table, including custom form fields stored in the plus tables.

The key tables for extraction:

| Table | What it holds | Migration role |
|---|---|---|
| `InvMaster` | Inventory master (stock codes) | Shows which stock codes are lot traceable or serialised |
| `InvWarehouse` | Inventory per warehouse | Warehouse-level balances for validation |
| `LotDetail` | Lot detail for lot traceable items | Core lot master data |
| `InvSerialHead` | Serial numbers | Core serial master data |
| `InvSerialTrn` | Serial transaction detail | Serial history |
| `InvMovements` | Inventory movements | Movement history to reconcile against lots and serials |
| `LotArcTransact` | Archived lot traceability transactions | Purged lot history, where archives are in SQL |

Sources: [SYSPRO 8 database architecture guide](https://help.syspro.com/syspro-8-2024/resources/pdfs/syspro-8-database-architecture-technical-guide.pdf), [SQL updates by release](https://help.syspro.com/syspro-8-2026-r1/i-installation/sys-8-sql-updates-by-release/sys-8-sql-updates-by-release.htm), [Lot Maintenance](https://help.syspro.com/syspro-8-2024/g_programs/imp/impbla/impbla.htm).

Profile each table on your own restored copy before you write any mapping. Column names and which columns are populated vary with release and with the setup options in use.

### Alternative extraction methods

**Syspro OData Service** is read-only. It "lets you connect securely to SYSPRO data without direct SQL access" ([help.syspro.com](https://help.syspro.com/syspro-8-2024/topics/syspro-services/syspro-odata-service/syspro-odata-service.htm)), and it is the only route in Syspro Cloud ERP ([help.syspro.com](https://help.syspro.com/syspro-8-2025/topics/insights-and-reporting/syspro-odata/syspro-odata.htm)). SYSPRO's 2021 R2 help says it limits results "to 5000 rows" per call, with paging through `$top` and `$skip` ([help.syspro.com](https://help.syspro.com/syspro-8-2021-r2/topics/insights-and-reporting/syspro-odata/syspro-odata.htm)). For a manufacturer with a large lot transaction history, that paging adds extraction time and complexity that a SQL extract avoids.

**Business Activity Queries (BAQs)** are SQL views created in the company database, and "any SQL user with db_datareader permissions can retrieve data using the views" ([help.syspro.com](https://help.syspro.com/syspro-8-2024/resources/pdfs/2022-release/topics/syspro-8-business-activity-queries-reference-guide.pdf)). SYSPRO documents no row limit for BAQs. The Business Activity Query Export program only moves query definitions between environments. It does not export data, so you still need an external tool to query the view.

**SYSPRO e.net business objects** like `INVQRY` (Inventory Query) return XML for a single record or a filtered set. They suit integration, not bulk extraction. Pulling a complete historical lot ledger through `INVQRY` is not a practical migration route. For the trade-off in detail, see [e.net business objects or direct SQL for extraction](https://clonepartner.com/blog/blog/syspro-enet-business-objects-or-direct-sql-extraction).

For a comparison of all extraction methods, see [How to Export Data from SYSPRO](https://clonepartner.com/blog/blog/how-to-export-data-from-syspro-methods-api-limits-portability).

## How does lot and serial data map to target ERPs?

The structural mismatch between SYSPRO's traceability model and the target ERP's model is where migrations break. Each target system stores and enforces lot and serial tracking differently.

### Open balances vs. historical transactions

Split the dataset into two streams:

**On-hand balances (active inventory):** The target ERP needs an opening inventory load, usually through an inventory journal or a dedicated import routine. The payload must include the stock code, warehouse, bin, quantity, lot number, serial number, and unit cost. If the unit cost loaded does not match SYSPRO's valuation, the opening inventory value will not reconcile.

**Historical transactions:** Loading years of past movements as live transactions in the new ERP would re-post them and change inventory valuation. Historical lot data — from SYSPRO's lot tables and the lot archives — usually goes into a read-only reference store or data warehouse instead. That keeps it available for compliance and reporting without touching the new system's live valuation. See [read-only access to SYSPRO history after migration](https://clonepartner.com/blog/blog/read-only-access-to-syspro-history-after-migration).

### Load order

Do not write directly to the target ERP's database. Pass translated data through the target ERP's API or import tool, so its business logic, costing and referential checks run.

Order the load strictly: **stock codes first, warehouses second, lot and serial definitions third, on-hand balances last.** If you load a serial number for an item that is not set up for serial tracking in the target, the load will fail. Lot traceable items often appear in bills of materials and jobs too, so align this with [migrating SYSPRO BOMs and routings](https://clonepartner.com/blog/blog/migrating-syspro-boms-and-routings) and [SYSPRO WIP and job history](https://clonepartner.com/blog/blog/syspro-wip-and-job-history-migrate-or-archive).

### Dynamics 365 Business Central

In Business Central, "an item tracking code reflects the different considerations regarding the use of serial and lot numbers for items moving through the inventory" ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/inventory-how-setup-item-tracking)). You track items on the Item Tracking Lines page, opened from inbound or outbound documents ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/inventory-how-work-item-tracking)). The Item Tracing page traces items Usage->Origin and Origin->Usage, which is the equivalent of SYSPRO's Search Up and Search Down ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/inventory-how-to-trace-item-tracked-items)).

Key mapping issues from SYSPRO to Business Central:

- **Opening balances** for tracked items can be loaded through the Item Journal with the **Item Tracking on Lines** toggle turned on. Where Directed Put-away and Pick is on, Microsoft points to the Warehouse Physical Inventory Journal instead. For bulk imports, Microsoft suggests configuration packages that import data to the journals ([learn.microsoft.com](https://learn.microsoft.com/en-us/dynamics365/business-central/inventory-how-work-item-tracking)).
- **SYSPRO's batch serial type** needs a decision. Test how Business Central handles a serial number with a quantity above one before you choose between lot numbers and individual serials.
- **Historical traceability** is harder. Business Central's posted item tracking entries come from posted documents. To preserve SYSPRO's full lot genealogy, you either replay transactions in sequence (expensive and error-prone) or keep the history in a reference archive alongside Business Central.

For the full mapping, see the [SYSPRO to Dynamics 365 Business Central migration guide](https://clonepartner.com/blog/blog/syspro-to-dynamics-365-business-central-migration-guide) and our [SYSPRO to Business Central migration service](https://clonepartner.com/blog/migrate/syspro-to-microsoft-dynamics-365-business-central).

### Epicor Kinetic and SAP Business One

The same SYSPRO-side checks apply to every target. Confirm each one against the target vendor's own documentation and your implementation partner:

- **Shared lot numbers.** If SYSPRO's **Use same lot on multiple stock codes** option is on, find out whether the target allows one lot number on several items. If not, plan a lot number transformation, such as prefixing the stock code.
- **Batch serials.** Find out whether the target accepts one serial number for a group of items.
- **Serial status.** Load historical serials with a status the target recognises, or they can block operations after go-live.
- **Lot attributes.** Map SYSPRO's lot dates and any lot custom form fields (certificates, concessions, inspection results) to fields the target supports.

For full mappings, see the [SYSPRO to Epicor Kinetic migration guide](https://clonepartner.com/blog/blog/syspro-to-epicor-kinetic-migration-technical-guide) and the [SYSPRO to SAP Business One migration guide](https://clonepartner.com/blog/blog/syspro-to-sap-business-one-migration-technical-guide). For the data move itself, see [SYSPRO to Epicor Kinetic](https://clonepartner.com/blog/migrate/syspro-to-epicor-kinetic) and [SYSPRO to SAP Business One](https://clonepartner.com/blog/migrate/syspro-to-sap-business-one).

## Why regulatory compliance raises the stakes

For manufacturers in regulated industries, lot and serial traceability is an obligation set by regulators, customers and quality standards. Medical device, food, pharmaceutical and aerospace manufacturers all face traceability requirements.

How long you must keep traceability records is set by your quality, legal or audit team, and the period runs from the transaction date. Ask them before you decide which closed lots to migrate and which to archive. Your migration must carry the full historical chain for every lot and serial still inside that period.

The implication for migration is simple: **if you lose traceability data during the move, you lose compliance**. A gap in the lot genealogy chain is not something you can explain away in an audit.

## How to validate lot and serial traceability after migration

Validation for traceability data goes beyond record-count parity. You need to prove the relationships survived, not just that the right number of rows arrived.

**Step 1: Record-count parity.** Compare row counts for lot headers, serial headers, and transaction records between SYSPRO and the target. This catches bulk failures — dropped tables, failed imports, truncated loads.

**Step 2: Lot header field-level comparison.** For a sample of lots, compare every mapped field between source and target: stock code, warehouse, expiry date, manufacturing date, original quantity received, hold status.

**Step 3: Upstream-downstream trace test.** Select a set of lots that span the full traceability chain — raw material receipt through production through shipment. In the target ERP, run the equivalent of SYSPRO's Search Up and Search Down. Confirm that every transaction in the chain is present and linked correctly. This is the test that catches broken genealogy links.

**Step 4: Serial-lot cross-reference.** For items that are both lot traceable and serialised, confirm that the serial-to-lot association survived the migration. The target may store this link differently from SYSPRO.

**Step 5: Archived lot verification.** If you extracted archived lot transactions, confirm they loaded into the target's historical or reference store. Run a traceability query on a lot you know was archived in SYSPRO.

**Step 6: Financial reconciliation.** The total value of the lot-tracked and serialised inventory loaded into the new ERP must match the inventory valuation report from SYSPRO taken immediately before extraction. A mismatch here means costing errors from day one.

> [!TIP]
> **Mock recall test.** SYSPRO describes a mock recall as "an exercise that involves imitating all procedures for an actual product recall", which "tests the traceability of products" ([help.syspro.com](https://help.syspro.com/syspro-8-2023/g_programs/inv/invpse/invpse.htm)). Run one against the migrated data before go-live. Pick a raw material lot, identify all affected finished goods, and produce the customer list. If the result matches what SYSPRO produces, your traceability chain is intact.

## How long does a SYSPRO lot traceability migration take?

The data migration itself — extracting lot and serial traceability data from SYSPRO and loading it into a target ERP — usually completes within **1–5 business days**, depending on data volume, complexity, and API rate limits. Datasets under 10,000 records can finish in under 24 hours. Projects with large lot transaction histories, archived lots and multi-level genealogy chains run toward the longer end of that range.

Keep two clocks separate: the data migration timeline and the ERP implementation timeline. ClonePartner runs the data migration. The customer's ERP implementation — selecting the software, configuring manufacturing workflows, training staff — takes months and is handled by the customer's implementation partner or the vendor. See [ERP Data Migration vs Implementation](https://clonepartner.com/blog/blog/erp-data-migration-vs-implementation-whats-the-difference) for more on this distinction.

To prevent disruption, the bulk load runs in the days before go-live while SYSPRO stays live. Go live on a Monday, never a Friday. SYSPRO freezes before Monday's working day starts, and a final delta of changed records only takes about 30 minutes. If you are leaving SYSPRO because of the licensing change, plan the extraction before your expiry date: 31 October 2026 outside the US, 31 December 2026 in the US ([syspro.com](https://www.syspro.com/formal-notice-change-to-syspro-licensing/)).

## Decision framework: migrate, archive, or both?

Not all lot and serial data needs to land in the target ERP's live tables. The right strategy depends on how the data will be used after go-live.

| Data category | Migrate live | Archive read-only | Rationale |
|---|---|---|---|
| Open lots (qty on hand > 0) | Yes | — | Active inventory must be fully traceable in the new system |
| Closed lots within your retention period | Depends | Yes | If your target ERP can store historical traceability, migrate. If not, archive to a queryable read-only store |
| Closed lots beyond your retention period | No | Optional | No retention requirement, but may have business value |
| Active serial numbers (in stock) | Yes | — | Must be available for sales, service, and warranty |
| Shipped serial numbers within warranty | Depends | Yes | Service and recall capability required |
| Inspection records linked to lots | Yes (if target supports) | Yes | Regulatory record, must be accessible |

The practical choice for regulated manufacturers is usually both: migrate current and recent lot and serial data into the target ERP's live tables, and archive full historical traceability to a read-only store (a SQL database, a BI layer, or a purpose-built archive) that stays accessible for the full retention period.

For the archive-or-migrate decision across all data domains, see [How to Archive SYSPRO History Before Switching ERP](https://clonepartner.com/blog/blog/how-to-archive-syspro-history-before-switching-erp).

## Migrating with ClonePartner

ClonePartner is a vendor-neutral, engineer-led data migration service. We do not resell any ERP and we are not a SYSPRO partner. We extract lot and serial traceability data from SYSPRO's SQL Server database — including archived lot transactions — and load it into whichever target system you choose.

We run unlimited sample migrations before the full run, and validate with record-count parity, field-level checks, and traceability chain checks. One fixed price per project, starting at $500, with no hourly billing and no per-record metering. The price scales with data volume, custom fields, attachment size, and the platforms involved.

ClonePartner is SOC 2 Type II and ISO 27001 certified. Staging data is purged within 30 days of project close.

> Book a free 30-minute scoping call. We'll assess your lot and serial data volume, identify archived lots that need recovering, and give you a fixed-price proposal — no hourly billing.
>
> [Talk to us](https://clonepartner.com/talk-to-us?duration=30&utm_source=blog&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click)

## Frequently asked questions

### What SYSPRO tables store lot traceability and serial tracking data?

Lot data centres on the LotDetail table, which holds lot detail for lot traceable items. Serial headers are in InvSerialHead, and serial transaction detail is in InvSerialTrn. Stock codes live in InvMaster, and each stock code's lot traceability and serial tracking settings decide which items carry traceability. Archived lot transactions can sit in separate lot archive tables such as LotArcTransact.

### What happens to lot data when SYSPRO's Purge and Archive runs?

SYSPRO's lot Purge and Archive program copies lot transactions and inspection records to an archive file and purges transaction details for lots that are complete. The lot header record is never deleted, only the transactions. In SYSPRO 7 the archive is stored in C-ISAM format. SYSPRO 8's Archiving Migration program converts those lot archives to SQL, and archived data is not available in SYSPRO 8 until someone runs it.

### How do I validate lot traceability after migrating from SYSPRO?

Start with record-count parity for lot headers, serial headers, and transactions. Then run upstream-downstream trace tests on a set of representative lots in the target ERP and confirm that every transaction in the genealogy chain is present. For regulated industries, run a mock recall: trace a raw material lot forward to all affected finished goods and customers.

### Can SYSPRO batch serial numbers migrate directly to other ERPs?

Check before you assume they can. In SYSPRO a batch serial means a group of items share one serial number, while a manual serial means each serial number is one item. Confirm in the target ERP's documentation how it treats a serial number with a quantity above one. If it cannot, convert batch serials during migration, either to lot numbers or to individual serial numbers.

### What happens to SYSPRO lot data after the 2026 licence expiry?

SYSPRO's formal notice gives an expiry date of 31 October 2026 for customers outside the US and 31 December 2026 for US customers. After that date you "will no longer be able to access Syspro" without a new subscription. The notice confirms the right to export your data on cessation of your licence, and asks you to raise the export with your account manager ahead of the expiry date.