Migrate from Encompass Production Cloud to Dolibarr ERP

Encompass Batch records are the primary production unit containing the recipe, ingredient lots, production run details, and finished-goods inventory link. Dolibarr has no native batch-production-record object. We split Batches into two migration targets: the production run metadata (batch number, production date, batch status, assigned user) migrates to a Dolibarr Project with a custom product_batch extrafield set; the finished goods from the batch link to a Dolibarr Product record with stock movement entries. If the customer uses Encompass's batch-specific QC results, these attach to the Product as custom fields. The customer chooses the batch-as-project strategy during scoping.

Encompass BOMs define recipe formulations with ingredient quantities, unit-of-measure conversions, and cost allocations. Dolibarr has a BOM module that stores product recipes as component lines with quantities and unit-of-measure references. We extract all BOM versions from Encompass (active and historical reformulation variants), present them to the customer for a version strategy decision, and import the selected version(s) into Dolibarr BOM records keyed to the finished-product Product. BOM version metadata (effective date, reformulation reason, TTB variant) migrates as custom fields on the Dolibarr BOM.

Encompass Production Schedules capture planned run quantities, start and end times, and resource assignments. Dolibarr's Project module can represent production planning as tasks with dates and assigned users, and Dolibarr's Manufacturing Orders module captures planned production runs linked to BOMs. The mapping depends on whether the customer uses Dolibarr's MRP-style manufacturing workflow or a project-planning workflow. We extract schedule dates, quantities, and resource assignments and map them to the customer's chosen Dolibarr structure.

Encompass Inventory Lots track raw materials and finished goods with quantity, location, cost, and TTB-relevant attributes. Dolibarr's Stock Lots module stores lot numbers, expiry dates, and physical stock quantities. We migrate lot records with lot number, product reference, quantity, unit of measure, cost, and location. Lot-level traceability genealogy (ingredient lots feeding finished-goods lots) is not a native Dolibarr concept; we reconstruct it by creating Dolibarr Stock Movements linked to both the source ingredient lot and the destination finished-goods lot, producing a migration-derived backtrace circle that the customer validates in a sandbox before production cutover.

Encompass Production Variances capture planned vs. actual material usage, labour time, and yield discrepancies per batch run. Dolibarr has no native variance record object. We migrate variance records as custom fields attached to the Dolibarr Product (planned_cost, actual_cost, variance_amount, variance_percent) and as line items on the associated Project representing the batch. The customer reviews the variance mapping during scoping to confirm the reporting structure meets their finance and operations needs.

Encompass QC records include inspection checkpoints, pass/fail results, and corrective actions tied to specific batches or production runs. Dolibarr has no native QC module. We migrate QC data as custom fields on the Dolibarr Product record (qc_check_passed, qc_inspection_date, qc_disposition, qc_corrective_action) and attach inspection records as notes or tasks to the associated Project. For TTB-compliance-relevant QC data, we recommend a dedicated QC module configuration or a third-party Dolibarr QC add-on if the customer's compliance requirements demand a formal inspection workflow.

Encompass Sales Orders link to inventory allocation and production demand signals with order headers, line items, pricing, and fulfilment status. Dolibarr Customer Orders (Commande client) map directly. We extract order headers, line items, pricing, delivery addresses, and fulfilment status, and import them as Dolibarr Commandes clients. Partially shipped orders require careful status mapping: Encompass fulfilment status translates to Dolibarr shipping status fields, and any backordered line items attach as notes to the order record.

Encompass Purchase Orders with vendor assignments, line items, expected delivery dates, and received quantities map to Dolibarr Supplier Orders. We extract open and historical POs, map vendor records to Dolibarr Third-parties with the supplier flag set, and import PO line items as Dolibarr Commande fournisseur lines. Any PO-to-receiving linkage that was enforced in Encompass is reconstructed in Dolibarr through the receiving workflow and purchase order status fields.

Encompass Finance module accounts define the cost structure for COGS, labour, overhead, and revenue recognition. Dolibarr's Accounting module uses a French-style plan comptable (or a custom chart). We map account numbers from Encompass to the customer-supplied Dolibarr account codes via a crosswalk provided by the customer's accountant during discovery. Account number mismatches are the primary source of post-migration reconciliation issues; we require the crosswalk before committing to financial record migration scope.

Open payables and receivables carry customer and vendor IDs, invoice amounts, due dates, and payment terms. We map open invoices to Dolibarr Facture client (customer invoices) and Facture fournisseur (supplier invoices), resolving customer and vendor IDs against the migrated Third-party records. Any invoice-to-payment linkage from Encompass is preserved as Payment records in Dolibarr linked to the corresponding invoice. Open vs. closed status migrates as the invoice status field.

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 scope depends on the account crosswalk completeness, the fiscal year retention requirements, and whether the customer needs historical reporting in Dolibarr or will maintain historical reporting in a separate financial archive. We migrate historical entries as Dolibarr Accounting Entries with journal codes mapped from the customer's crosswalk.

Encompass Production Cloud user accounts map to roles and permissions controlling access to production, QC, and finance modules. Dolibarr user accounts have a permission-based access control model. We extract Encompass user assignments and role names, map them to Dolibarr permission groups (Admin, Production Manager, Sales, Finance, etc.), and provision Dolibarr user accounts with matching permissions. Any user records with no Encompass role attribution (common in per-user-licence-constrained environments where floor staff share accounts) are flagged in the data audit for manual resolution.