Migrate your Encompass Production Cloud data

Batches are the primary production record in Encompass Production Cloud. Each batch links to a Bill of Materials, production schedule, ingredient lot assignments, and finished-goods inventory records. We map batch headers and line-item components 1:1 and preserve the lot-to-batch parent-child relationship during migration.

Bills of Materials define recipe formulations with ingredient quantities, unit-of-measure conversions, and cost allocations. We extract BOM versions and map them to destination recipe records, flagging any versioned or superseded BOMs that require a selection decision from the customer.

Production schedules capture planned run quantities, start/end times, and assigned resources. The scheduling granularity and resource-linkage model varies between source and destination platforms, so we map schedule headers and flag line-level resource assignments for manual review.

Inventory lots track raw materials and finished goods with quantity, location, cost, and TTB-relevant attributes. We migrate lot records with full genealogy chains and preserve lot-level traceability links used by Batch Backtrace.

Variance records capture planned vs. actual consumption for each batch run, including material usage, labour time, and yield discrepancies. We export variance records keyed to their parent batch ID so the cost-of-goods story is preserved at the line level.

QC records include inspection checkpoints, pass/fail results, and corrective actions tied to specific batches or production runs. The schema for QC fields varies between tiers and add-on configurations, so we map standard QC data and flag custom inspection fields.

Sales orders link to inventory allocation and production demand signals. We map order headers, line items, pricing, and fulfilment status. Orders that are partially shipped require careful status mapping at the destination.

Open and historical purchase orders with vendor assignments, line items, expected delivery dates, and received quantities are extracted. We flag any PO-to-receiving linkage that may break if inventory transactions reference PO IDs not yet migrated.

Finance module accounts define the cost structure for COGS, labour, overhead, and revenue recognition. Account numbers and segment structures vary by company, so we map account IDs and require a customer-supplied mapping table for the destination chart.

Open payables and receivables carry customer/vendor IDs, invoice amounts, due dates, and payment terms. These require careful reconciliation against the customer/vendor master records already migrated, and we flag any invoices with unresolved reference IDs.

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 volume can be large and the accounting period requirements vary by compliance need.

User accounts map to roles and permissions that control access to production, QC, and finance modules. Role schemas differ between Encompass tiers, so we extract user assignments and map them to destination role profiles.