Migrate from Deacom ERP to Epicor Prophet 21

Deacom Items (dmprod) using pr_id as sequential integer primary key map to Epicor Kinetic Part records. The PartClass defines the part type (Item, Service, etc.), and Part-specific attributes (catch-weight settings, shelf-life days, lot traceability flags) are configured in Epicor's Part master after import. Facility restrictions on Items migrate as Site-specific Part records or Site-restricted PartClass assignments. UOM definitions (dmprod.unit_of_measure) map to Epicor's UOMClass and UOM system, with catch-weight UOMs requiring explicit weight-per-unit setup in the Part's UOMClass definition.

Deacom BOMs store multiple active revisions per Item (default, lab-only, regulatory-only) with revision-date ordering. We export BOM records sorted by revision date and flag any Item with more than one active revision. The customer chooses between consolidating to the current default BOM or preserving multiple Epicor Kinetic BOM revisions with appropriate revision type flags. Epicor's Engineering Workbench revision model supports effective dates but does not have native lab-only and regulatory-only BOM variants — these require a custom revision type field or naming convention established during configuration.

Deacom Customer records (dmcust) using cu_id as primary key map to Epicor Kinetic Customer records. Customer hierarchies, credit terms, and customer-part associations (dmcust cross-links) map to Customer and CustomerGroup. Customer-specific pricing sheets stored in Deacom migrate as Part's Price List entries scoped to the Customer or CustomerGroup in Epicor. Ship-to addresses and contact records require separate mapping to Epicor's CustCnt and ShipTo tables.

Deacom Vendor master data maps to Epicor Kinetic Supplier records. Purchasing lead times, preferred UOMs, and vendor-specific part cross-references migrate to Supplier and SupplierPart tables. Vendor contracts and terms map to Epicor's Terms and Conditions system linked to the Supplier.

Deacom sales order headers and lines (dt-type records referencing dmcust and dmprod) map to Epicor Kinetic SalesOrder and OrderDtl. Order status (open, fulfilled, invoiced) maps to the OrderHed.OrderStatus and OrderDtl.OrderLine fields. Drop-ship and DSD order types require Epicor's drop-ship and multi-site configuration. Pricing sourced from Deacom customer-specific pricing sheets migrates as PriceLdn entries linked to the Part and Customer during order import.

Deacom production orders (dt-type transaction records referencing dmprod Item and BOM revision) map to Epicor Kinetic Job records. Job status migrates as the Epicor Job status (open, complete, closed), with job costing, routing steps, and labor tracking entries mapped to JobMtl and JobOper. Open production orders in Deacom require a status decision before migration — either create Epicor Jobs as open with the same status so Epicor picks them up, or close them in Deacom and create them as closed historical records. Job close tolerance and the production order reference number field are preserved for audit continuity.

Deacom QC tests set up per Item/Revision with threshold values, test types, and pass/fail criteria map to Epicor Kinetic QC Spec records. We create QC SpecType and QC SpecMtl linkages before Part import so that quality specifications are in place when production orders are created. Facility-specific QC test variations stored in Deacom map to Epicor Site-specific QC Spec overrides. Test type labels and d3_c2guid UDF pick-list options require GUID remapping using the dxcaption2 label extraction approach described in the gotchas section.

Deacom stores lot numbers and shelf-life dates at the inventory transaction level. Lot genealogy with parent-child relationships for co-manufactured or bulk-split scenarios maps to Epicor Kinetic Lot records with LotMtl references linking parent and child lots. Shelf-life expiration dates migrate to Lot.LotExpirationDate. Serial number tracking migrates to Lot records with the serial number flag set per Part's tracking requirement. The lot genealogy graph is reconstructed from Deacom's lot_parent_id and lot_child_id relationship records.

All Deacom inventory movements — receipts, issues, adjustments, and transfers — in dt-type tables linked to Items and lots map to Epicor Kinetic PartTran records. Transactions are sequenced in timestamp order and exclude any records referencing lots that were purged or flagged as invalid during the export phase. PartTran references are resolved to the imported Lot records and the imported Part records using pre-built lookup tables generated during the master data import phase.

Deacom real-time GL postings with drill-down to dt transaction level map to Epicor Kinetic GLJrnDtl records within a GL Journal batch. Account codes from Deacom's chart of accounts map to Epicor GL Account segments. Multi-currency journals migrate with exchange rate references, but we recommend that the customer's Epicor implementation team verify currency revaluation rules for the destination fiscal year setup. Custom financial statements per company structure migrate as Epicor Financial Report Designer configurations. Historical transaction amounts are imported as posted journals — Epicor requires that the fiscal periods are open for the date range of any imported journal entries.

Deacom AP and AR modules integrate with the GL. Open invoices, payment applications, credit memos, and aging details map to Epicor AP InvoiceHed/InvoiceDtl and AR InvoiceHed/InvoiceDtl records. Multi-currency AR with exchange rate details migrates with the invoice records. Customer and supplier payment terms from Deacom map to Epicor's Terms system linked to the Customer and Supplier records. Open invoices are imported with their current aging status; closed invoices migrate as historical records without triggering aging recalculation.

Deacom UDF pick-list options reference d3_c2guid links to the dxcaption2 table's system-generated uniqueidentifier values that are non-transferable across databases. We extract the human-readable label and its associated d3_c2guid value during export, build a remapping table, and recreate the pick-list options in Epicor Kinetic as UD Codes (if using Epicor's UD01-UD10 convention) or as custom pick-list fields with the correct option values. The old _guid values are not imported; only the labels migrate and are assigned new Epicor-native IDs. This step must complete before any UDF values are imported for QC tests, Items, or Customers.

Deacom's iOS and Android mobile apps for sales and warehouse use cached local data that is not persisted to exportable database tables. Mobile-specific notes and offline entries are not independently retrievable and cannot be migrated. We document this gap in the migration inventory with a recommendation for the customer to review mobile app data manually and re-enter any critical records in Epicor Kinetic post go-live.