Migrate from Plex Smart Manufacturing Platform to Infor CloudSuite Corporate

Plex Production Orders map to Infor Manufacturing Orders or SFC (Shop Floor Control) Shop Orders depending on which Infor Cloudsuite suite is in use. Each Plex Production Order carries status, item reference, quantity, bill of materials revision, routing, and expected completion date. We map production order status (Released, In Process, Complete, Closed) to the Infor equivalent, preserving the BOM revision reference and the production start and end timestamps as audit trail. Open production orders migrate last so that all BOM revisions and item definitions are already in place at the destination.

Plex Items map to Infor Item Master records. Plex distinguishes manufactured, purchased, and phantom item types, each carrying a Bill of Materials and routing definition. We map item type, unit of measure, lot control settings, and stocking location codes. Multi-plant setups in Plex (site, warehouse, bin) map to Infor's site and warehouse structure, with bin-level inventory tracked if the destination Infor edition includes warehouse management. Alternate BOMs and alternate routings preserve as Infor Engineering Change Orders or revision-linked BOMs per the target configuration.

Plex BOMs are versioned and tied to Items with multi-level component hierarchies, yield factors, and scrap percentages. We extract every active and historical BOM revision, preserving the revision effective date and the component yield. Multi-level BOMs require either flattening or preservation of the parent-component structure depending on whether Infor's BOM module supports multi-level display. We map the component scrap factor to Infor's scrap percentage field and the component yield to the quantity-per field. Any BOMs still referenced by open Production Orders migrate with the production order so that the production record has a complete historical view.

Plex Work Orders derive from Production Orders and carry their own scheduling, labor allocations, and material allocations. Each Work Order references a Production Order, an Item, and a Bill of Materials. We map work order status, assigned employees (resolved via User lookup), scheduled start and end dates, and any linked non-conformance records. Open Work Orders migrate last in the production sequence so that parent Production Orders and BOMs are already loaded. Work order history migrates as transactional records attached to the work order entity in Infor.

Quality Non-Conformances in Plex are tightly linked to the production transaction that triggered them, including lot, work order, item, and production order references. We extract non-conformance disposition codes, corrective action descriptions, associated inspection data, and the triggering transaction link. In Infor Cloudsuite, quality records live in the QMS or quality management layer, which is available on specific industry suites. We map the Plex disposition type (Return to Vendor, Scrap, Rework, Use-As-Is) to the Infor QMS equivalent and preserve the corrective action text as an Infor CAPA record linked to the non-conformance. Lot and serial genealogy from the non-conformance record transfers to Infor's traceability module.

Plex consolidates supplier and customer data under a single Accounts object with a type field distinguishing them. We extract supplier records separately, mapping payment terms, approved supplier status, and contact information. Supplier part numbers and approved manufacturer lists (AMLs) associated with the supplier account migrate to Infor as supplier-linked part records. Address and contact details map to Infor's party and contact structures.

Customer records extract from Plex Accounts with type set to Customer, preserving the customer name, billing and shipping addresses, payment terms, and credit limit. Sales contact information maps to Infor's party contact records. Any customer-specific pricing or discount schedules stored as Plex custom fields on the Account record migrate to Infor's customer price group or price list assignments.

Plex Purchase Orders link to Accounts (suppliers) and Items with line-level detail including expected dates, quantities, pricing, and receipt status. We extract all open and historical POs with line-level granularity. Open POs migrate last so that supplier accounts and item master records are already established in Infor. PO status (Open, Released, Closed) maps to Infor PO status, and any line-level receiving transactions migrate as receiving history against the PO in Infor.

Lot traceability is a core Plex capability; each lot carries parent-child genealogy across production and inventory transactions. We extract the full traceability tree as a set of linked lot genealogy records. In Infor Cloudsuite, lot and serial number control is configured at the item master level, and traceability is maintained through the SFC and quality management layers. We map each Plex lot to an Infor lot number, preserving the lot creation transaction, the originating production order, and the parent lot relationship. Multi-level genealogy chains require recursive traversal during extraction and are inserted as a series of lot relationship records in Infor.

Plex supports Custom Fields on most objects with customer-specific field definitions that vary per implementation. We perform a discovery pass against Plex's API to enumerate every custom field, its data type, and the objects it attaches to before building the migration mapping. Custom field values migrate to Infor as either native custom fields (if the Infor edition supports them on that object) or as extension table records linked via a foreign key. This discovery step adds time to the project plan but is required to prevent custom field value loss, which is a common migration gap identified during scoping.

Plex ERP includes core financials (GL, AP, AR). Transactional history, journal entries, and account balances require mapping to Infor's chart of accounts structure, which is defined during Infor implementation. Historical AP and AR open items migrate as open records in Infor, and GL journal entry history migrates to the Infor GL module with account code mapping resolved against the customer's Infor COA. Financial data migration is typically scoped separately from manufacturing data because it requires Infor's financial structure to be finalized first, and it often requires coordination with the customer's Infor finance consultant.