Migrate from Encompass Production Cloud to Microsoft Dynamics 365 Business Central

Encompass Batch records map to Dynamics 365 Production Order headers. Each Batch links to a BOM version, a production schedule, ingredient lot assignments, and finished-goods inventory output. We extract batch records from in-app production reports (no public API available), resolve the BOM version reference and ingredient lot IDs at migration time, and create Production Orders with status set to Scheduled or Started depending on the customer's cutover window. Because Encompass has no bulk-export API, we validate the extraction completeness against inventory movement records and QC checkpoint records before committing to import scope.

Encompass BOMs define recipe formulations with ingredient quantities, unit-of-measure conversions, and cost allocations. Multiple active BOM versions in Encompass represent reformulations, seasonal substitutions, or TTB-mandated changes. We extract all BOM versions and present a versioning strategy decision to the customer during scoping: migrate the current active version only, or include historical recipe variants for audit traceability. Dynamics 365 BOM tables store version and effective date ranges natively, so each Encompass BOM version becomes a separate Dynamics BOM Version record linked to the parent BOM.

Production Schedules capture planned run quantities, start/end times, and assigned production resources. We map schedule lines to Dynamics Job Card or Route operations depending on the destination tier. The resource-linkage model differs between platforms: Encompass assigns production staff directly to a batch run, while Dynamics 365 assigns routes to Work Centres. We extract the resource assignments from Encompass schedules and map them to configured Work Centres during the production-line configuration phase.

Encompass Inventory Lots track raw materials and finished goods with quantity, location, cost, and TTB-relevant attributes. Dynamics 365 requires explicit lot and serial number dimension groups to be configured in the Item master before lot-tracked inventory can be migrated. We include a pre-flight check to confirm that the customer's destination environment has lot tracking enabled for the relevant item categories (raw ingredients, packaging materials, finished goods). Lot genealogy chains must be reconstructed separately from the lot record migration.

Encompass Batch Backtrace stores lot genealogy chains (ingredient lot to finished-goods lot) as linked records rather than a flat table. Standard in-app exports do not include the full chain. We extract genealogy as a separate data extraction step, reconstruct the parent-child lot relationships, and write them into Dynamics 365 as Item Tracking entries. The genealogy chain must be complete and validated before production batch records are imported because Dynamics 365 validates that ingredient lot references exist at the time of production order confirmation.

Encompass Production Variance records capture planned vs. actual consumption for each batch run: material usage, labour time, and yield discrepancies. We export variance records keyed to their parent Batch ID, map variance types to Dynamics 365 production journal line categories (Consumption, Output, Scrap), and write variance amounts to the appropriate cost ledger accounts. Variance records are imported after BOM and Batch records are confirmed complete because the variance amount calculation references the BOM cost structure.

QC records include inspection checkpoints, pass/fail results, and corrective actions tied to specific batches or production runs. The QC schema varies between Encompass tiers and add-on configurations. We extract QC field values from batch-linked inspection records, map them to Dynamics 365 Quality Association entries (which attach to production orders), and flag any QC fields with no Dynamics 365 equivalent for customer review. QC records without a matching Dynamics 365 Quality Order type are included in the written inventory for manual post-migration setup.

Encompass Sales Orders link to inventory allocation and production demand signals. We map order headers, line items, pricing, and fulfilment status to Microsoft Dynamics 365 Sales Order records. Orders that are partially shipped require careful status mapping: Encompass's partial-fulfilment flag maps to Microsoft Dynamics 365 Sales Order with partially shippable line statuses. Encompass distributor-specific fields (route codes, delivery windows) have no direct Dynamics 365 equivalent and are flagged for customer review during scoping.

Open and historical purchase orders with vendor assignments, line items, expected delivery dates, and received quantities are extracted from Encompass. We map vendor records to Dynamics 365 Vendors (created before Purchase Order import to satisfy the VendorId lookup). PO-to-receiving linkage is preserved where the receiving record exists in the source; open PO lines without corresponding receiving records are imported as unfulfilled Purchase Orders with expected receipt dates carried forward.

Encompass finance module accounts define the cost structure for COGS, labour, overhead, and revenue recognition tied to production batches. Account numbers and segment structures vary by company, so we extract all Encompass accounts and require a customer-supplied mapping spreadsheet before import. COGS accounts linked to Encompass BOM cost allocations require particular attention because Dynamics 365 posts production costs through different journal structures. The Chart of Accounts migration is the most manual object in scope and is sequenced after BOM import so that inventory valuation accounts are confirmed before GL mapping is finalised.

Open payables and receivables carry vendor/customer IDs, invoice amounts, due dates, and payment terms. We extract open AP and AR records and map them to Dynamics 365 vendor and customer ledger entries. Invoice numbers are preserved as references but Dynamics 365 assigns its own entry numbers; we document the mapping between source invoice IDs and destination entry IDs in the reconciliation report. AP/AR import is sequenced after Vendors and Customers are confirmed complete to satisfy the account lookups.

Closed GL entries, cost-of-goods postings, and inventory adjustment transactions constitute the financial history. Migration scope for historical transactions is negotiated with the customer: we typically migrate the current and prior fiscal year only, keeping older periods in a read-only archive because Dynamics 365 performance degrades with very large GL entry volumes and older closed periods are rarely needed for day-one operations. Historical transaction import requires the Chart of Accounts mapping to be complete and validated first.