Manufacturing
SYSPRO data licensing guide for manufacturers
By SourceX Editorial · Updated
Short answer
A SYSPRO data export for licensing starts with a record map: which modules your site runs, how many years of orders, jobs, inventory and quality records survive, and where the explanatory notes live. History linking an order to a job, a shortage and a shipment matters far more than a dump of master tables.
Key takeaways
- Map SYSPRO records by module and by years of surviving history before exporting anything.
- Transaction history and notes carry the decisions; customer, supplier and stock code masters only supply context.
- Run every extract against a restored backup or replica with a read-only account, never the live company database.
- Export full history before a SYSPRO upgrade or ERP migration, since cutovers often carry only open orders and balances.
- Customer-owned designs, export-controlled jobs and personal contact details stay out of any licensed package.
What does SYSPRO hold that an AI developer might license?#
SYSPRO holds the quote-to-cash and plan-to-produce history of a manufacturer, and the parts an AI developer might license are the transactions that show work moving through the plant. Which records exist depends on the modules your site bought and actually used, so the first job is a record map.
Build the map from what your team already knows: the module list, the year you went live, any purges or archive runs, and the custom forms people fill in. The table shows the record families most manufacturers check first.
| Record family | Typical SYSPRO source | What makes it useful | Watch for |
|---|---|---|---|
| Quotes and sales orders | Quotation and sales order history, order notes | Requested, promised and shipped dates side by side | Customer names, pricing, contact details |
| Jobs and work in progress | Job headers, operations, material issues, labor postings | How jobs actually ran against plan | Employee names in labor postings |
| Bills of materials and routings | Structures, routings, engineering change history where used | How products are built and how designs changed | Customer-owned designs and drawings |
| Inventory and traceability | Stock movements, lot and serial history, warehouse transfers | Shortages, substitutions and traceability decisions | Supplier and customer identifiers |
| Purchasing and receiving | Purchase orders, receipts, supplier delivery history | Supply exceptions and how buyers responded | Supplier pricing and contract terms |
| Quality and returns | Inspection, nonconformance and return records where used, or a separate QMS | Problems, root causes and dispositions | Records kept outside SYSPRO |
| Notes and custom fields | Free-text notes, custom form fields, attached documents | The reasoning behind decisions | Personal details and pasted emails |
Master data or transaction history: which matters more?#
Transaction history matters more than master data in a SYSPRO export, because transactions record what people decided and what happened next. Stock codes, customer and supplier masters and work center definitions give that history meaning, but on their own they describe a catalog, not work.
The strongest packages join a sales order to the jobs it created, the material issued and any shortage, the operations and labor posted, and the shipment. Notes at each step explain why a job was split or a supplier changed. Check whether past purge or archive runs removed closed jobs or old transactions, since many ERP sites trim history to keep the database lean.
How to run a SYSPRO data export without touching production#
A SYSPRO data export for licensing should run against a copy of the company database, not the live system the plant depends on. On-premises SYSPRO sites usually sit on a SQL Server database, so a recent backup restored to a separate server is the simplest safe source; partner-hosted and cloud sites need a conversation with the provider first.
- Confirm the SYSPRO version, the hosting model and every company database in scope, including closed or merged companies.
- Restore a recent backup to a separate server and create a read-only account for the extract.
- Write one extract query per record family and keep it, so each run can be repeated and checked.
- Export to plain formats such as CSV or Parquet, with a data dictionary for every table and custom field.
- Record the date range, row counts and any filters applied in an extract log.
- Spot-check totals against standard SYSPRO reports exported to Excel for the same period.
Why SYSPRO reports export is not the same as a history extract#
SYSPRO reports export is useful for checking an extract but poor as the extract itself. Report output is formatted for people: it summarizes, drops fields and rarely carries the keys needed to join orders, jobs and shipments across years.
Use reports to confirm that row counts and totals in the extract match what finance and operations already trust. If a monthly shipment report and the extracted shipment lines disagree, resolve the gap before anything moves to preparation, because a buyer will find it later.
SYSPRO migration: export history before the old database is retired#
A SYSPRO migration is the moment history is most likely to be lost. Moves to a newer version, a hosted deployment or a different ERP often bring across open orders, balances and current masters, while closed jobs, old notes and retired companies stay behind on a server someone plans to switch off.
Take a full backup and a documented extract before cutover, and record who holds the old server and its credentials. Keeping a restorable copy costs little compared with rebuilding years of job history later from paper travelers and inboxes.
Rights and privacy checks for SYSPRO records#
Rights and privacy checks for SYSPRO records cover three sources of restriction: your software agreements, your customer and supplier contracts, and the personal details stored in the data. Review the SYSPRO license and any hosting or support agreement for terms on data access and extraction, and check customer contracts and NDAs for confidentiality clauses that reach order and delivery information.
Privacy laws may apply to contact and employee details depending on who the people are and where they live, and that question is assessed deal by deal with counsel. The table shows how common fields are usually handled.
| Field or record | Issue | Typical handling |
|---|---|---|
| Customer and supplier names and addresses | Reveal commercial relationships | Replaced with consistent codes |
| Contact names, emails and phone numbers | Personal information | Removed |
| Prices, discounts and costs | Commercially sensitive | Removed, or kept in broad bands with approval |
| Labor postings with employee names | Personal information | Replaced with roles or pseudonymous IDs |
| Jobs built to customer drawings | Customer-owned design | Excluded with their notes and attachments |
| Export-controlled or defense work | Regulatory restriction | Excluded by customer, program or product code |
Illustrative: a valve maker before its ERP cutover#
Illustrative: a fictional industrial valve manufacturer has run SYSPRO on premises for many years and plans to move to a cloud ERP. The migration plan carries over open orders, inventory balances and current bills of materials, while closed jobs, purchase history and years of order notes would stay on the old server.
The IT director restores a backup to a separate machine and maps record families. Nonconformances turn out to live in a spreadsheet and an old desktop database, linked to SYSPRO only by job number. Jobs for a defense customer carry their own product codes, which makes them simple to exclude.
The company extracts full history before cutover. Order-to-job-to-shipment histories with notes are scoped for review, customer names become codes, and the nonconformance spreadsheet is joined by job number. The old server is retired only after the extract log and row counts are checked against the backup.
How SourceX works with SYSPRO sites#
SourceX works with SYSPRO sites through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The Supply step needs only metadata, such as version, modules in use, company databases, years of history and where quality records live; no database or file is shared during the initial assessment.
If a package proceeds, the extract queries, date ranges, row counts and removals become part of the SourceX Evidence Packet, alongside provenance, licensing rights, permitted use, the privacy record and release authorization. Large extracts stay in the manufacturer's own storage or ship on encrypted drives.
Frequently asked questions
Can we export our own data from SYSPRO?
In most cases a company can access the data it enters into its own ERP, but the details sit in your SYSPRO license and any hosting or support agreement. Check those terms for limits on direct database access or third-party tools, and ask your SYSPRO partner how extracts are usually done for your deployment.
Do we need our SYSPRO partner involved?
Not always. An in-house team with database access and a restored backup can run the extract. Partners help when the site is hosted, heavily customized or on an older version, and they often know which custom tables hold the fields your staff rely on.
Can custom forms and user-defined fields be included?
Yes, and they are often the most informative fields because they capture what the standard screens did not. Document each one in the data dictionary with its meaning and how consistently it was filled in, and review free-text custom fields for personal details before they are included.
What if we run several SYSPRO companies?
Treat each company database as its own source with its own date range and rights review. Companies set up for acquired businesses may carry legacy customer contracts, and closed companies are easy to overlook even though they can hold the longest history.
Which file format should the extract use?
Plain, documented formats such as CSV or Parquet work best, with one file per table or record family and a data dictionary. Avoid formatted report output and raw database backups as the delivery format, because the recipient needs keys and field definitions to join records, not page layouts.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.