Migrate from Deacom ERP to Infor CloudSuite Corporate

Deacom dmprod with pr_id primary key maps to Infor CloudSuite Industrial MITMAS (Item Master). We export item records including UOM definitions, catch-weight settings, and facility restriction flags in a single pass. Infor MITBAL carries inventory balances per facility and must be populated after MITMAS is imported. Facility restriction flags from Deacom become Infor warehouse code restrictions on the item record. Item status (active/inactive) maps to the Infor Item Status field with any Deacom custom status codes remapped to Infor-valid values.

Deacom BOMs with versioned revisions per Item (default, lab-only, regulatory-only flags) map to Infor CloudSuite product structures. We export BOM records sorted by revision date and flag any Item with multiple active revisions so the destination consolidates to a single current BOM or preserves the revision history per customer configuration. Lab-only BOMs in Deacom map to Infor's formula management or R&D BOM types if the CloudSuite edition supports them; otherwise they are flagged for manual recreation. Routing steps and labor factors from Deacom production orders map to Infor work center definitions.

Deacom dmcust with cu_id primary key maps to Infor CloudSuite Industrial OCUST. We export customer hierarchies, credit terms, and customer-part associations. Customer-specific pricing sheets stored in dmcust cross-links are mapped to Infor's price list (OIPRD) and price break (OPRIORITY) tables. Multi-currency customer settings from Deacom map to Infor's currency assignment on the customer record. Sold-to and ship-to address roles are preserved as separate contact records linked to the customer.

Deacom vendor master records map to Infor CloudSuite Industrial APVENDOR. We export vendor records including purchasing lead times, preferred UOMs, and vendor-specific part cross-references. Vendor evaluation ratings from Deacom custom fields map to Infor's vendor rating fields if present in the target edition. Multi-currency vendor settings are preserved at the vendor level. Vendor part numbers mapped to Deacom items are documented as cross-reference records for the customer's purchasing team to re-enter in Infor.

Deacom production orders referencing Items (pr_id) and BOM revision map to Infor CloudSuite Industrial MWOOHEAD (Work Order Header) and MWODET (Work Order Detail). We export job costing, routing steps, and labor tracking entries per work order. Open production orders must be distinguished from completed ones; Deacom's job status field maps to Infor WO status codes. Material issues and labor postings linked to the production order are mapped to Infor's material and labor transaction tables. Closed work orders are imported as completed history for audit trails.

Deacom inventory movements (receipts, issues, adjustments, transfers) stored in dt-type tables linked to Items and lots are sequenced in timestamp order and mapped to Infor CloudSuite MICTTRANS. Lot references from Deacom map to Infor's lot number fields with shelf-life dates preserved. We exclude any records referencing lots that were not exported (lot genealogy completeness check). MICTTRANS populates current on-hand balances in MMINVT per facility. Transfers between facilities map to Infor's inter-warehouse transfer transactions.

Deacom lot numbers and shelf-life dates at the inventory transaction level map to Infor CloudSuite MLOT. We export lot genealogy records with parent-child lot relationships for co-manufactured or bulk-split scenarios. Serial number tracking maps to MSERIAL with lot-to-serial assignments preserved. Infor's lot traceability inquiry (from MLOT to MICTTRANS to MWO and OCUST) is validated post-migration. Any lot records without genealogy are flagged for manual review.

QC tests set up per Item/Revision with threshold values, test types, and pass/fail criteria map to Infor CloudSuite Industrial MQCTEST and MQCSAMP. The QC test schema varies by facility in Deacom and is preserved at the facility level in Infor. We export dmd3 pick-list UDF options alongside the QC test records and apply the guid remapping table so that QC UDF pick-lists are recreated with new IDs in Infor rather than imported blindly. Any QC test records referencing deleted items are excluded from the export.

Deacom real-time GL postings with drill-down to dt transaction level map to Infor CloudSuite Industrial GLMACC (Account Master), GLACCT (Account Combination), and GLJRNL (Journal Entry). We export account codes, journal line items, and source document references (AR/AP/inventory). Custom financial statements per company structure map to Infor's financial statement definitions. Multi-entity GL requires we export company codes and configure Infor's intercompany chart structure before journal import. Trial balance validation is performed before and after migration.

Deacom accounts payable and receivable modules linked to the GL map to Infor CloudSuite APINVH (AP Invoice Header) and ARINVH (AR Invoice Header). We export open invoices, payment applications, credit memos, and aging details. Multi-currency AR requires exchange rate records in Infor before invoice import. Customer payment terms from Deacom map to Infor's payment term codes (OTERMS). Open invoices are imported as current aging; closed invoices are imported as history for audit trails.

User-defined fields in Deacom referencing dmd3 pick-list options via d3_c2guid links to dxcaption2 are non-transferable. We export the human-readable labels alongside the guids, generate a remapping table that maps each Deacom _guid to the recreated Infor pick-list option, and apply the remapping during the data import phase. This ensures UDF pick-list values display correctly in Infor without orphaned references. The customer configures the Infor pick-list values before migration using the exported label list.

Deacom sales order headers and lines referencing Customers, Items, and pricing map to Infor CloudSuite Industrial SOSOHEAD and SOSOLINE. We export order status (open/fulfilled/invoiced) and handle drop-ship and DSD order patterns. Customer-specific pricing sheets from dmcust cross-links are resolved to Infor price list references during order import. Backorder and partial fulfillment flags are preserved. Invoiced orders are imported as closed history; open orders are imported as active records with available-to-promise recalculated post-migration.