Manufacturing
Infor SyteLine (CloudSuite Industrial) data licensing guide
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A SyteLine data export can support a license when it holds the company's own operating history, such as orders, jobs, planning exceptions, engineering changes, quality and service records, and when customer designs, controlled items and personal details are cleared first. The decision rule: license records that link a decision to an outcome, and keep native keys in every export.
Key takeaways
- SyteLine records worth licensing link a trigger to an outcome, such as an MRP exception and the planner's response.
- Export routes differ for on-premises, hosted and multi-tenant cloud deployments, so read the subscription terms first.
- Each site may belong to a different legal entity, and the entity that holds the records approves any license.
- Items under export control are removed rather than redacted, because routings and service records can count as controlled technology.
Can you license Infor SyteLine data?#
Infor SyteLine data can often be licensed when the records are the company's own operating history, such as orders, jobs, routings, quality and service records, and when customer terms, controlled work and personal details are handled first. SyteLine, the ERP Infor has also marketed as CloudSuite Industrial (CSI), holds that history across the whole manufacturing cycle.
Many mid-sized makers of equipment, components and engineered products have run SyteLine for long periods, and many are now deciding whether to move to multi-tenant CloudSuite or another ERP. That decision is the moment to map what the old database holds, before anything is purged or left behind.
The decision rule is simple to state. License records that show a decision and an outcome, exclude anything that belongs to a customer or is controlled, and keep the export keyed so the records can be rejoined.
SyteLine record map#
The record map below lists the main areas of a typical SyteLine installation, what each shows about how the business runs and the rights flag to clear before any outside use. Coverage depends on which modules you licensed and configured.
| Area | Typical records | What it shows | Rights flag |
|---|---|---|---|
| Customer orders and estimates | Estimates, order lines, configured items, due dates, changes | How demand and promises shifted | Customer names and prices masked |
| Jobs and production | Jobs, routings, operations, labor and machine transactions | Planned against actual work | Employee names coded |
| Planning and scheduling | Planned orders, MRP exceptions, schedule changes | How planners reacted to shortages | Usually company-controlled |
| Purchasing and receiving | Purchase orders, receipts, supplier performance | Supply decisions and lead time changes | Supplier pricing may be under NDA |
| Engineering changes | Item revisions, BOM and routing changes, change notes | How products and processes evolved | Exclude customer-owned designs |
| Quality | Nonconformances, inspections, corrective actions | Problems and their resolution | Review customer complaint details |
| Service and field | Service orders, incidents, contracts, parts used | Field failures and repairs | Customer sites and contacts masked |
| Financials | Invoices, costs, variances | Margins and cost behavior | Usually excluded or aggregated |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Export routes by deployment#
The export route for SyteLine history depends on how the system is deployed: on premises, hosted for you by a partner, or in Infor's multi-tenant cloud. Each route has a different owner and a different contract to check.
In every case, keep native keys such as order, job, item and customer numbers. Summary reports lose them, which makes joining orders to jobs, quality and service records slow or impossible. User-defined fields and custom tables often carry important notes, so include them in the map.
Multi-site installations need one more step. Each site may belong to a different legal entity, and the entity that holds the records is the one whose authorized signer approves any license.
| Deployment | Typical export route | What to check |
|---|---|---|
| On-premises | Database backup or read-only copy, plus reports and saved queries | Who can interpret the schema and customizations |
| Hosted by a partner | Database copy or extracts arranged with the host | Hosting contract terms on data return and fees |
| Multi-tenant cloud | Vendor-provided export, integration and data tools | Subscription terms, export scope and access after termination |
| Retired instance | Restore of a backup to a supported environment | Whether a usable backup and the right to run it still exist |
Rights flags to clear first#
The rights flags to clear first are the ones that can remove whole groups of records, so they come before any preparation work. Most of them sit outside the ERP, in customer agreements, supplier NDAs, acquisition documents and export classifications.
- Customer designs and specifications attached to items or orders, including drawings and configured-product specifications.
- Customer agreements with confidentiality or data clauses that cover information about their orders.
- Supplier pricing and terms received under NDA.
- Employee names in labor transactions, approvals and notes, which become role codes.
- Export-controlled items and their production and service records.
- Records of a business unit bought or sold, whose ownership may have moved with the deal.
Why export control matters for equipment makers#
Export control matters for equipment makers because ERP records about controlled items can themselves be controlled. Under the EAR, technology means information necessary for the development, production, use, operation, installation, maintenance, repair, overhaul or refurbishing of an item, and routings, process notes and service records for controlled items may fall within that description.
Releasing controlled technology to a foreign person in the United States can count as an export to that person's most recent country of citizenship or permanent residency. Because a licensee's staff may include foreign persons, controlled items are removed from a package by item number rather than redacted, and the classification is confirmed with your export compliance lead.
Which SyteLine records hold the most value?#
The SyteLine records with the most value link a trigger to an outcome: an MRP exception and the planner's response, a nonconformance and its corrective action, a service incident and the repair, or an estimate and the job that followed. Each shows a decision made by experienced people under real constraints.
Service records often stand out for equipment makers, because they connect field failures to parts, revisions and fixes over long product lives. Engineering change history adds the reasons behind revisions, provided customer-owned designs are excluded.
Value falls when history was purged, when notes are blank or copied, or when a past migration broke links between orders and jobs. Document those gaps rather than hiding them.
Illustrative: an equipment maker maps SyteLine before a move#
Illustrative: Kestrelmoor Industrial is a fictional maker of industrial pumps and valves with plants in several states, each running as a site in one on-premises SyteLine installation. Its service team logs field incidents and repairs in the service module, and quality records sit in the same database.
Planning a move to a cloud ERP, the IT director built a record map with the controller and the quality manager, restored a full backup into a read-only environment and exported orders, jobs, engineering changes, nonconformances and service incidents with native keys.
Some sites belonged to a subsidiary acquired years earlier, so their records were set aside until counsel confirmed which entity owned them. Items under export control were flagged and removed. The remaining history went into a metadata-only fit check, and the old instance was retired only after the archive was verified.
How SourceX approaches SyteLine history#
SourceX approaches SyteLine history through the SourceX five-step transaction, starting with a fit check that uses only metadata: version, deployment, sites, modules in use, years of history and known restrictions. No exports are requested until the company decides to proceed.
Value is weighed with the SourceX Enterprise Data Value Framework, where linked outcomes, domain expertise, recency and rights raise value and preparation cost and privacy burden reduce net value. The supplier approves every step, the records are licensed rather than sold, and the company keeps ownership.
Frequently asked questions
Does moving to multi-tenant CloudSuite carry over all our history?
Not always. Migration projects often bring master data and open transactions and leave closed history behind or summarize it. Confirm the scope in writing, and keep a verified archive of the old database before the on-premises instance is retired.
Does our Infor agreement limit what we do with our own data?
Read the agreement. Software agreements usually treat the vendor's software and your data separately, and hosted or cloud terms add rules on export, retention and deletion. Confirm nothing restricts outside use of your records before planning a license, and have counsel review the terms.
Can we include data from sites we acquired?
Only after confirming which entity owns the records and whether the acquisition agreement or the seller's customer contracts restrict their use. Acquired sites often carry different customer terms, so they are reviewed separately and added later if cleared.
Who needs to approve a license of ERP data?
The authorized signer of the legal entity that holds the records, usually the CEO or another officer. Depending on financing and ownership, board, investor or lender consents may also apply, so check those documents early in the process.
Do custom fields and user notes need special handling?
Yes. User-defined fields and notes often hold the most useful context and the most sensitive details, including names, customer references and pricing. They are mapped in the data dictionary and reviewed during preparation before any record leaves the company.
Sources
- BIS describes EAR technology (15 CFR 772.1) as information necessary for the development, production, use, operation, installation, maintenance, repair, overhaul, or refurbishing of an item. Source
- Under 15 CFR 734.13, export includes the release or transfer of technology or source code to a foreign person in the United States, and any such release is a deemed export to the foreign person's most recent country of citizenship or permanent residency. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.