Migrate from Plex Smart Manufacturing Platform to Microsoft Dynamics 365 Business Central

Plex Items (manufactured, purchased, and phantom subtypes) map to Dynamics 365 Released Products with the item number as the primary key. Plex's item type classification maps to Product Type (Item vs Service) in Supply Chain Management or Item Type in Business Central. We preserve the Plex item's default site, unit of measure, and costing model as manufacturing parameters in the destination. Phantom items require special handling: Plex phantom items map to bill of materials lines with a Phantom type in Dynamics 365 that are exploded at the time of production order creation rather than stored as separate inventory.

Plex BOMs are versioned and multi-level with component yields and scrap factors. Dynamics 365 Supply Chain Management supports BOM versions (multi-level, version-controlled) or Product Tree structures depending on the engineering policy configuration. We perform BOM flattening during the transform phase: top-level assemblies map to a BOM version, sub-assemblies with their own BOMs are resolved recursively, and scrap percentages are entered as line-level scrap allowances on the BOM version. Route dependencies (work centers, operation sequences) map from Plex routing definitions to Dynamics 365 Operations resources and Routes. Business Central requires single-level BOMs only, so multi-level Plex BOMs require engineering restructuring before migration.

Plex Production Orders map directly to Dynamics 365 Supply Chain Management Production Orders, with the production order number preserved as a custom identifier. Plex order status (Scheduled, In-Process, Completed, Closed) maps to Production Order status (Scheduled, Started, Reported, Ended, Completed). The Production Order BOM and Route are linked via the BOM version and Route reference. Open production orders migrate with their current step and quantity outstanding; closed production orders migrate as historical records with full lifecycle timestamps preserved.

Plex Work Orders derive from Production Orders and carry scheduling, labor allocation, and material assignments. In Dynamics 365 Supply Chain Management, Work Order equivalents are Production Order operations (job scheduling level) or the job card terminal for shop floor execution. We map the Plex Work Order number to the Production Order line reference, link assigned employees via the Work Center labor capacity, and preserve non-conformance linkage as quality order associations on the production order. Open Work Orders migrate with status Open, Released, or In Process depending on the Plex status at extraction time.

Plex tracks inventory at site, warehouse, and bin level. Dynamics 365 Supply Chain Management uses the same three-level hierarchy: Site > Warehouse > Location. We map Plex location codes directly to Dynamics 365 location IDs and preserve the current on-hand quantity per location as inventory transactions. Multi-plant Plex configurations map to multiple Sites in Dynamics 365. Location-specific lot numbers and serial numbers migrate as inventory dimensions linked to the on-hand quantity records.

Lot traceability is a core Plex strength where each lot carries parent-child genealogy across production and inventory transactions. Dynamics 365 does not have a native genealogy tree structure; lot tracking uses the InventDim (inventory dimension) model where lots are tracked as a dimension on inventory transactions. We preserve the full traceability tree from Plex by creating a custom LotTransitions table in Dynamics 365 linked to the standard inventory transaction log, with ParentLot and ChildLot fields that represent the genealogy chain. Lot attributes (expiry dates, supplier lot codes, custom properties) migrate to lot master attributes in Dynamics 365 Supply Chain Management.

Plex Quality Non-Conformances link to Work Orders, Production Orders, Items, and Lots with dispositions (Reject, Rework, Use-As-Is) and corrective actions. Dynamics 365 Supply Chain Management Quality Management uses Quality Orders linked to inventory transactions or quality tests. We map the Plex NC number to the Quality Order ID, the Plex disposition to Quality Order Disposition, and the corrective action text to the Quality Order Notes field. The link back to the source production or work order is preserved via the reference relationship on the Quality Order. If Quality Management is not configured in the destination, we flag this as a pre-migration configuration requirement.

Plex consolidates suppliers and customers under Accounts with a type field distinguishing them. We separate by type and map Plex Supplier records to Dynamics 365 Vendors with the account number as the primary key. Vendor payment terms, tax group, and approved supplier status migrate to the Vendor record. Address and contact information maps to the Dynamics 365 postal address and contact roles. The Plex supplier's lead-time and minimum-order-quantity settings migrate as purchase policy fields on the Vendor record.

Plex Customer accounts map directly to Dynamics 365 Customers. The Plex account number becomes the Customer Account number, and the Plex address and contact records map to the Customer postal address and contact roles. Credit limits, payment terms, and customer-specific pricing migrate to the Customer record. If the customer uses Plex EDI or electronic data interchange, we note this as an integration gap since EDI requires a separate middleware or Dynamics 365 EDI module configuration post-migration.

Plex Purchase Orders link to Vendor and Item with expected dates, quantities, and pricing. They map directly to Dynamics 365 Purchase Orders with line-level detail preserved. Open POs migrate with their current receipt status; closed POs migrate as historical records with a status flag. PO line pricing from Plex (unit price, discounts, charges) maps to the Dynamics 365 purchase price trade agreement or direct line pricing. Plex POs referencing item substitutions require re-mapping to the correct Released Product ID in Dynamics 365 during the transform phase.

Plex Shop Floor Control logs capture labor posting, machine time, material consumption, and scrap at the operation level. These map to Dynamics 365 Production Journal entries (for consumption and time) and Route Card Journal entries (for operation scheduling and labor). Each Plex log entry references a Work Order and operation step, which we resolve to the corresponding Production Order route operation in Dynamics 365. Historical logs migrate as posted journal entries; open logs migrate as draft journal entries awaiting final reporting.

Plex supports Custom Fields on most objects with customer-specific definitions that vary per implementation. Dynamics 365 supports custom fields via extensions (X++ in Supply Chain Management, AL extensions in Business Central) or via the OData extension properties model. We perform a pre-migration discovery pass via the Plex API to enumerate every custom field across every object, capturing field name, data type, and value. Each custom field is then created as a typed custom field in the Dynamics 365 destination before any data import, and the Plex custom field value maps to the Dynamics 365 extension field by name matching.

Plex documents attached to Items, Work Orders, or Quality records are stored in Plex's document management system. Dynamics 365 does not have a unified document store across all modules; documents are stored in SharePoint (connected via the SharePoint integration), Dataverse (Common Data Model attachments), or directly on the record via the Attachments note. We export Plex document references and binary content where API access permits, then determine the target storage location in Dynamics 365 based on the record type. Items typically target SharePoint Item document libraries; Work Orders target SharePoint Production libraries. We deliver a file-to-location mapping spreadsheet as part of the migration package.