Migrate from Deacom ERP to Microsoft Dynamics 365 Business Central

Deacom Item Master records (dmprod, pr_id integer primary key) map to Microsoft Dynamics 365 Released Products. We export all item records including UOM definitions, catch-weight settings, and facility restriction flags. Catch-weight inventory in Deacom maps to the Catch Weight product type in Dynamics 365 Supply Chain. Item costing methods (standard, average, FIFO) translate to Costing version configuration in Dynamics. Site and warehouse assignments export as InventSite and Warehouse records that map to the product's site coverage.

Deacom BOMs are versioned per Item with flags for default, lab-only, and regulatory-only. We export BOM records sorted by revision date and flag any Item with multiple active revisions. Default BOMs migrate as active BOM versions in Dynamics 365 Manufacturing. Lab-only and regulatory-only BOMs migrate as inactive BOM versions with a custom field bom_variant_type__c (lab/regulatory/default) for audit trail. If the customer requires full revision history, we map each revision to a separate BOM version with effective date set to the original Deacom revision date.

Deacom Customer records (dmcust, cu_id primary key) map to Dynamics 365 CustTable with DirParty for party-based data. We export customer hierarchies, credit terms, and customer-part associations. Multi-currency customer pricing sheets stored in dmcust cross-links map to Trade Agreements (PriceDiscTable) in Dynamics 365. Customer address records migrate as LogisticsPostalAddress with address purposes (invoice, delivery, primary). Address validation against Dynamics postal address standards is applied during transform.

Deacom Vendor master records use a naming convention consistent with dm-type maintenance tables. We export vendor records including purchasing lead times, preferred UOMs, and vendor-specific part cross-references. Vendors migrate to VendTable with DirParty for party data. Vendor address and contact records migrate as LogisticsPostalAddress and LogisticsElectronicAddress respectively. Purchasing lead times map to the vendor's delivery date calculation on the Vendor master in Dynamics.

Production orders are dt-type transaction records that reference the Item (pr_id) and BOM revision. We export job costing, routing steps, and labor tracking entries. Open production orders are flagged and mapped to ProdStatus of Scheduled or Started. Routing operations map to ProdRoute records with work center assignments. Closed production orders migrate as historical records with estimated and actual costs. We exclude any production order records that reference lots no longer present in the export scope.

QC tests are set up per Item/Revision with cross-references to dmd3 pick-list UDF options. The QC test schema (threshold values, test types, pass/fail criteria) varies by facility. We map test definitions to Dynamics 365 Quality Management Quality Test Groups and Quality Associations that attach to item or inbound warehouse receipt processes. Threshold values and UDF pick-list options are recreated in Dynamics as pick-list or free-text test result fields. The dmd3 pick-list guid references are not transferred; labels are extracted and remapped to new Dynamics option set values.

Deacom stores lot numbers and shelf-life dates at the inventory transaction level. We export lot genealogy records with parent-child lot relationships for co-manufactured or bulk-split scenarios. Lot numbers migrate to InventLotTable with shelf-life expiry dates and lot attributes as custom fields. Parent-child lot genealogy migrates as InventBatchRelation records linking the child lot to its parent lot. For co-manufactured lots, we create a manufacturing BOM lot link that traces the input lots to the output lot. Serial number traceability migrates to InventSerialTable with a one-to-one lot-to-serial relationship.

All inventory movements live in Deacom's dt-type tables linked to Items and lots. We sequence these in timestamp order and exclude any records that reference lots not included in the migration scope. Movements map to InventTrans records with warehouse, site, and location assignments resolved from the Inventory Dimensions (InventDim) table. Receipt, issue, transfer, and adjustment transaction types map to corresponding InventTransType values. Cost amounts migrate to the InventValue layer for cost rollup reporting.

Deacom GL postings are real-time and drill-down to dt transaction level. We export account codes, journal line items, and source document references (AR/AP/inventory). Custom financial statements per company structure migrate to Dynamics 365 Finance financial report designer. Multi-currency journal entries export with the original transaction currency, exchange rate, and reporting currency amounts. Financial dimensions from Deacom's cost center and department structures map to Dynamics 365 Financial Dimensions with custom dimension values per legal entity.

Accounts payable and receivable modules in Deacom integrate directly with the GL. We export open invoices, payment applications, credit memos, and aging details. Multi-currency AR requires we also export exchange rate tables and original-currency amounts. Open AP invoices migrate to VendInvoiceJour; open AR invoices migrate to CustInvoiceJour with invoice posting profiles matching the Deacom document type. Payment terms and due date calculations are recalculated in Dynamics from the payment terms master.

Sales order headers and lines are dt-type records referencing Customers, Items, and pricing. We export order status (open/fulfilled/invoiced) and handle drop-ship and DSD (Direct Store Delivery) order types. Open sales orders migrate to SalesTable with corresponding SalesLine records. Line item pricing is resolved via Trade Agreements at migration time if the customer has configured those in Dynamics. Order statuses map to SalesStatus values (Backorder, Invoiced, Cancelled). Historical invoiced orders migrate to SalesInvoiceJour.

User-defined fields in Deacom reference pick-list options via d3_c2guid links to the dxcaption2 table's system-generated uniqueidentifier. These _guid values are non-transferable — importing them into Dynamics 365 creates orphaned references with no validation error. We export the human-readable labels alongside the guids and create a remapping table. UDF pick-lists are recreated as custom option set fields in Dynamics 365 with new values and labels. The remapping table is delivered as a CSV for the customer's Dynamics admin to verify against the recreated pick-list options before production load.