Migrate from Aptean Industrial Manufacturing ERP, WorkWise Edition to Microsoft Dynamics 365 Business Central

WorkWise Customer records carry contact details, accounts receivable balances, and backlog references that map directly to the Dynamics 365 Customer master. We map to the CustTable entity with thePartyId resolving to a DirPartyRecord. AR balance and credit limit fields transfer as-is; the customer-specific backlog view requires a Power BI report rebuild in Dynamics 365 because WorkWise backlog screens have no direct equivalent.

WorkWise Vendor master records include purchasing terms, AP balances, and lead times used in MRP calculations. We map to VendTable with the same DirParty resolution as Customer. Lead times transfer to the VendOnHand-lead time fields used in Dynamics 365 MRP. Supply-side open PO data requires recomputation in Dynamics 365 because WorkWise holds vendor commitments differently from the Dynamics 365 purchase-agreement model.

WorkWise Items carry stocking policies, stocking UOM vs. purchasing UOM, cost layers, revision control, and ECN-effective date fields. We map ItemId to the Dynamics 365 itemNumber, preserve UOM conversion rules, and set the tracking dimension group to match the WorkWise revision control settings. ECN-effective dates on Items require a decision during scoping: migrate current-effective revision only or preserve the full revision history with Valid From/Valid To date ranges.

WorkWise Sales Orders reference Customers and forward to Work Orders, with line-level pricing, promised dates, and order status. Open orders transfer with current statuses preserved in the SalesOrderHeader and SalesOrderLine entities. Historical closed orders can be migrated as invoiced records or archived based on customer scope. WorkWise order-specific custom fields migrate to Sales Order extension fields in Dynamics 365.

Open WorkWise POs carry vendor commitments and expected receipt dates. We map line items to PurchTable and PurchLine with VendorId and DeliveryDate preserved. Destination-side receipt records must be reopened against the imported PO identifiers. WorkWise blanket PO structures map to Dynamics 365 Purchase Agreements with the Agreement type set to Blanket Order.

WorkWise Work Orders tie to BOMs, Routings, and Work Centers, tracking planned vs. actual cost and completion status. We map WorkOrderId to ProdTable.ProdId and preserve the as-reported planned-vs-actual cost in ProdJournalTable records posted at migration time. Open Work Orders with status Released or Scheduled transfer as equivalent ProductionOrderStatus values; Completed and Closed orders transfer as historical records with their final costing layer.

WorkWise multi-level BOMs with revision control and ECN affectivity dates must be exploded and validated before migration. We map BOMId to BOMTable with BOMId resolved per ECN-effective date scope. Parent-component relationships require careful sequencing because Dynamics 365 enforces referential integrity at insert time. Multi-level BOMs (Work Order with sub-assemblies) map to a BOM explosion in ProdBOM with line-level quantities and scrap percentages preserved.

WorkWise Routings define the sequence of operations, Work Centers, and standard times used in scheduling. We map to RouteTable with OperationId sequences preserved. Work Center assignments from WorkWise map to WrkCtrTable references. Standard times transfer to RouteJob or ProdRouteOperation depending on the Dynamics 365 version. Scheduling direction (forward/backward) and infinite/finite scheduling flags carry over as Route properties.

WorkWise Work Centers carry capacity, calendars, and cost rates used in CRP calculations. We map WorkCenterId to WrkCtrTable or the OperationsResource entity in Dynamics 365 Manufacturing. Calendar schedules transfer to WrkCtrTable.WorkingTimeTemplateId. Capacity parameters (efficiency, queue time) map to the resource capacity journal entries. CRP capacity recomputation runs post-migration as a Dynamics 365 batch job.

WorkWise supports unlimited locations and bins with on-hand quantities, negative-on-hand flags, and consignment indicators. We map SiteId/LocationId to the InventLocation/WMSLocation hierarchy in Dynamics 365. On-hand quantities transfer to InventSum with InventOnHand calculated post-migration. Consignment flags map to the InventOwnerId field set to the vendor party. Available-to-promise recomputes after migration based on updated inventory parameters.

The WorkWise GL structure includes department cost centers, fixed/variable cost flags, and inter-company segment codes used in job costing. We map LedgerAccount to MainAccount with financial dimensions preserved as DimensionHierarchy structures in Dynamics 365. Custom account assignments from WorkWise MODs transfer to user-defined dimension segments that the Dynamics 365 admin configures post-migration.

WorkWise Employee records include payroll integration references, labor rates, and Work Center assignments. We map HcmWorker with DirPerson and DirPartyAddress records. Labor rates transfer to HcmWorkerRate or InventProdRouteJournal cost posting depending on the job cost model in use. Payroll integration requires re-establishment with the destination payroll provider; we flag the payroll system reference field for admin action.

WorkWise Job Cost tracks planned vs. actual at Employee, Work Center, Department, Labor/Operation, and Component Material levels. We transfer as-reported cost values to ProdRouteJob or ProdBOMCostRecord entities. Planned-vs-actual variance fields carry over but are static at migration time because Dynamics 365 recalculates variance at posting. We advise customers that destination-side job cost reports reflect the moment-in-time values from WorkWise, not live recalculations.

WorkWise Quality management stores inspection results, compliance alerts, and traceability links to lots and Work Orders. We map to the InventQualityMgmt* entities with inspection results preserved as InventQualityJournal records. Traceability links transfer to InventTraceTag and InventTraceRef. Destination-specific inspection plans and quality test groups must be configured in Dynamics 365 based on the customer's compliance requirements.

WorkWise ECN affectivity dates control when BOM and Routing revisions go live. A single Item can have multiple BOM revisions effective at different dates. We present two paths during scoping: migrate the current-effective revision only (simpler, suitable for audit-focused migrations) or preserve the full revision history with Valid From/Valid To date ranges on Dynamics 365 BOMVersion and RouteVersion records. The chosen path determines the transform logic applied during import.

WorkWise MODs extend the base table schema with custom fields not present in the standard product. We flag every non-standard column found during the database audit and map each to a Dynamics 365 extension field (FieldExtension or DirPartyModule fields) or a custom field where no equivalent exists. MODs that reference custom tables require pre-creation of corresponding custom tables in Dynamics 365 before data loads begin.