Migrate from Encompass Production Cloud to Infor CloudSuite Corporate

Encompass Batch records map to Infor CloudSuite Industrial Work Orders. Each Encompass batch links to a BOM version, a production schedule, ingredient lot assignments, and finished-goods inventory. We extract batch_id, batch_status, planned_start/end dates, planned_quantity, actual_quantity, production_segment, and TTB-relevant attributes (target ABV, SRM, IBU, volume packaged). We create parallel Infor Work Orders and populate a custom field enf_batch_id__c to preserve the original Encompass reference. Batch Backtrace genealogy chains are stored as linked records in Encompass; we build a parallel traceability table in Infor linked to the Work Order's finished-goods lot number and resolve the genealogy chain as a closed backtrace circle before sign-off.

Encompass BOM records define recipe formulations with ingredient quantities, unit-of-measure conversions, and cost allocations across multiple active versions. Infor CloudSuite Industrial stores BOMs at the item level with version control. We extract all BOM versions from Encompass and present them to the customer for a versioning strategy decision: migrate the active version only, or include historical recipe variants for audit traceability. Each BOM version migrates as a separate Infor BOM revision linked to the target item. Encompass TTB attributes (ABV targets, colour specifications, hop profiles) migrate to Infor user-defined fields on the BOM item.

Encompass production schedules capture planned run quantities, start/end times, and assigned production-line resources. Infor CloudSuite Industrial's scheduling lives within the Work Order header and the SFC_ResourceSchedule table. We map Encompass production_line_id and scheduled_start/end to Infor Work Order Operation StartDate and DueDate, with resource assignments resolved against Infor Work Center definitions. Scheduling granularity differences between Encompass and Infor are resolved during the BOM-and-schedule workshop before migration.

Encompass inventory lots track raw materials and finished goods with quantity, location, cost, and TTB-relevant attributes. We migrate lot records keyed by Encompass lot_number, preserving the lot creation date, expiration date, location assignment, unit cost, and quantity on hand. Each Encompass lot becomes an Infor lot-controlled item record under MME_LotMaster. Lot genealogy chains from Batch Backtrace are stored as linked ingredient-to-finished-goods relationships; we validate the genealogy chain is closed (all ingredient lots resolve to the finished-goods lot) before marking the lot migration complete.

Encompass production variance records capture planned vs. actual consumption per batch: material usage variance, labour time variance, and yield discrepancy. We export variance records keyed to the parent batch_id and populate Infor CST_WorkOrderCostDetail with estimated vs. actual cost components. Variance percentage and the underlying Encompass variance reason code migrate to a custom field enf_variance_reason__c on the Infor work order for finance-team review post-migration.

Encompass QC records include inspection checkpoints, pass/fail results, and corrective actions tied to specific batches or production runs. The schema for QC fields varies by Encompass tier and add-on configuration. We extract QC records by batch_id, mapping pass/fail status, corrective action descriptions, and measurement values (gravity, pH, dissolved oxygen) to Infor QM inspection records linked to the work order's finished-goods lot. Any QC checkpoints without a mapping are flagged in the QC gap report for the customer's quality team to review.

Encompass sales orders link to inventory allocation and production demand signals. We map order headers, line items (product, quantity, unit of measure), pricing, and fulfilment status. Orders that are partially shipped require careful status mapping to Infor SLS_SalesOrderHdr order status and SLS_SalesOrderLine status fields. Keg-deposit and case-deposit line items from Encompass migrate as separate line types in Infor Sales Order.

Open and historical purchase orders with vendor assignments, line items, expected delivery dates, and received quantities are extracted from Encompass. We map POP_PurchaseOrderHdr and POP_PurchaseOrderLine, preserving vendor item numbers and lead times. Any PO-to-receiving linkage that depends on Encompass-specific inventory receiving workflow is flagged for Infor receiving configuration post-migration.

Encompass finance module accounts define the cost structure for COGS, labour, overhead, and revenue recognition. Account numbers and segment structures vary by company configuration. We map Encompass account IDs to Infor FIN_AccountMaster account codes, flagging any account segments (cost centre, region, division) that require Infor account structure reconfiguration. Account mapping requires a customer-supplied crosswalk document during the finance-scope workshop.

Open payables and receivables carry vendor/customer IDs, invoice amounts, due dates, and payment terms. These require careful reconciliation against the vendor and customer master records migrated from Encompass. We extract open AP and AR by vendor_id and customer_id, map to Infor FIN_APInvoiceHdr and FIN_ARInvoiceHdr, and flag any payables where the vendor master is missing from the Encompass export as a gap requiring manual resolution before AP import.

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 because the account structure must be confirmed and the transaction volume reviewed before scope commitment. We extract closed GL entries by fiscal period and map them to Infor FIN_GeneralLedgerJournal, flagging any entries referencing Encompass accounts that have not yet been mapped to Infor account codes.

Encompass Production Cloud user accounts map to roles and permissions controlling access to production, QC, and finance modules. Per-user pricing may have resulted in floor-staff entries made under shared accounts, which limits owner attribution on historical production records. We extract user assignments and map them to Infor SEC_User roles. Owner attribution gaps are flagged in the data audit report, and the customer's admin may need to assign responsible users before historical batch records are imported.