Migrate from Plex Smart Manufacturing Platform to Epicor Prophet 21

Plex Production Orders map to Epicor Kinetic Job records. The production order item, quantity, scheduled start, and end dates transfer to JobHead. The Production Order routing steps map to JobOper rows with operation sequence, work center, and labor estimates. We resolve the Part revision reference using Epicor's PartRev table and map the Plex production order status (Scheduled, Released, Complete) to Epicor Job status. Open production orders migrate last so that Part and BOM master data is fully settled first.

Plex Items (manufactured, purchased, and phantom subtypes) map to Epicor Part records. The Part number, description, uom, and type code (M, P, S) transfer directly. Manufactured parts carry a BOM reference in Plex that maps to Epicor Part-BOM after BOM migration. Plex item classification codes map to Epicor PartClass for grouping. Part-specific custom fields migrate to Epicor User-Defined Attributes (UDAs) on the Part table.

Plex BOMs are versioned and tied to Items. Multi-level BOMs with component yields and scrap factors require flattening or preservation depending on Epicor's BOMRev structure. We extract the Plex BOM version effective date and transfer it as an Epicor revision. Phantom items in Plex map to Phantom BOMs in Epicor. If Plex uses alternate BOMs per production order, we map these to Epicor alternate BOMs or flatten them into a single canonical BOM during the transformation pass.

Plex Work Orders derive from Production Orders and carry their own scheduling, labor allocations, material allocations, and linked non-conformance records. In Epicor Kinetic, the same Job record carries these attributes as JobOper and JobMtl rows. We map Work Order status, assigned employees, estimated labor hours, and material requirements to the corresponding Job record fields. Open Work Orders migrate last to avoid orphaned Job records.

Plex Quality Non-Conformance records are tightly linked to the production transaction that triggered them: lot, work order, item, and employee. We extract non-conformance disposition codes, corrective action descriptions, and associated inspection data. These map to Epicor QA Management NonConf records with the Epicor Job reference stored as a linked attribute. Disposition codes (Use As Is, Scrap, Rework, Return to Supplier) transfer directly with a mapping table for any Plex-specific disposition values.

Plex consolidates supplier and customer data under Accounts with a type field. We filter Plex Accounts where type = Supplier and map to Epicor Vendor records. Vendor name, address, payment terms, and approved supplier status transfer directly. Plex supplier-specific custom fields migrate to Vendor UDAs. We validate that the Epicor Vendor number sequence is set before import to avoid key conflicts.

Plex Accounts where type = Customer map to Epicor Customer records. Contact details, payment terms, and the Plex customer-specific fields migrate to Epicor Customer UDAs. Epicor Customer is created before any related Sales Order or Quote import so that the CustomerID reference is satisfied at insert time.

Plex Purchase Orders link to Accounts (Vendors) and Items, carrying expected dates, quantities, and pricing. We extract open and historical PO records preserving line-level detail. Plex PO status (Open, Closed, Cancelled) maps to Epicor PO status. Line-level item references resolve to Epicor Part numbers; any Plex line referencing an unmapped Part triggers a reconciliation step before the POLine inserts.

Lot traceability is a core Plex strength. Each lot carries parent-child genealogy across production and inventory transactions. We extract the full traceability tree and transfer it to Epicor PartLot records with lot number, expiration date, and lot attributes. Epicor's Job traveler traceability view pulls genealogy from the PartTran table, so we map Plex inventory transactions to PartTran with the correct LotNum and reference fields (PONum, JobNum, OrderNum). Multi-generational genealogy chains require a separate traversal pass and a lineage document for the customer's QA team.

Plex tracks inventory at site, warehouse, and bin level. We extract location assignments and current on-hand quantities per location. Plex plant and warehouse codes map to Epicor Warehse records; Plex bin codes map to Epicor WhseBin records with bin type and zone attributes. Multi-plant Plex setups map to Epicor Plant records with inter-plant transfer logic preserved as PartTran records. On-hand quantities migrate to PartBin after Part master data is loaded.

Plex supports Custom Fields on most objects, but the set and data types differ per customer implementation. We perform a discovery pass using Plex's API to enumerate every custom field across every object before building the migration mapping. Each Plex custom field name and value maps to an Epicor UDA on the equivalent standard table (Part, Job, NonConf, Vendor, Customer, POHeader). Epicor UDAs must be pre-created in the destination environment before data migration begins; the discovery pass determines the UDA creation workload.

Documents attached to Plex Items, Work Orders, or Quality records are stored in Plex's document management system. We export file references and binary content where API access permits and link them to the migrated Epicor record using Epicor's document attachment model. File attachment migration does not preserve Plex document versioning; we deliver the current revision of each document. Customers with heavy document dependencies should plan a document migration phase separate from the transactional migration.

Plex ERP includes core financials (GL, AP, AR). Transactional history, journal entries, and account balances require mapping to Epicor's chart of accounts structure, which is typically more granular than Plex's financial module. We extract open AP and AR records, map them to Epicor InvoiceHead and CashHead, and preserve GL account assignments. Epicor's fiscal calendar and period structure must be configured before financial migration so that posting dates map correctly. Historical closed periods migrate as read-only ledger entries.

Plex Shop Floor Control logs record labor entries, machine cycle counts, and production transactions against Work Orders and Production Orders. We extract these as Epicor Labor records (LaborDtl with JobNum and AssemblySeq) and PartTran entries that feed the cost roll-up. Labor transactions reference the Epicor Job created during the Work Order migration phase, requiring the JobNum to be resolved before the labor record inserts.