Migrate from Aptean Industrial Manufacturing ERP, WorkWise Edition to Dolibarr ERP

WorkWise Customer records carry contact details, accounts-receivable balances, and backlog references. We map these directly to Dolibarr Third-Party records using the Customer category. Address fields, phone, email, and AR balance migrate as-is. Customer-specific pricing tables in WorkWise (a pain point noted in reviews) migrate to Dolibarr as price-suppression or customer-specific price rules in the product module if the feature is enabled; otherwise they are archived with a reference document.

WorkWise Vendor master records include purchasing terms, AP balances, and lead times used in MRP calculations. We map these to Dolibarr Third-Party records using the Supplier category. Vendor lead times migrate to the product-supplier price module if installed. Open PO commitments in WorkWise require a separate PO import step in Dolibarr after the vendor record is live.

WorkWise Items carry stocking policies, stocking UOM vs. purchasing UOM, cost layers, revision control, and ECN-effective date fields. We map Items to Dolibarr Product records with type (stockable, service, assembly). UOM conversions are computed during the transform step. The ECN-effective date field requires a scoping decision: we either migrate the current-effective revision only or preserve a revision history note on the Product record, depending on what the customer chooses during discovery.

WorkWise Sales Orders reference back to Customers and forward to Work Orders, with line-level pricing, promised dates, and status. Open orders transfer with current statuses; historical closed orders migrate as read-only records or remain in the WorkWise archive for audit. Dolibarr Order lines reference the Product records created during the item migration phase, and the customer/third-party lookup resolves to the imported Customer.

Open POs carry vendor commitments and expected receipt dates. We map line items to Dolibarr Supplier Order structure. Receipt records in Dolibarr must be reopened against the imported PO identifiers post-migration if the customer wants to track incoming materials against the transferred orders.

WorkWise Work Orders tie to BOMs, Routings, and Work Centers, tracking planned vs. actual cost and completion. We transfer open Work Orders with their costing layers into Dolibarr Manufacturing Orders. Routing operations from WorkWise map to Dolibarr BOM operation lines, but destination-specific scheduling features are limited compared to WorkWise's CRP and MPS engine. We flag this gap in the migration handoff document so the customer's operations team can assess whether external planning tools are needed.

Multi-level BOMs with revision control and ECN affectivity dates must be exploded and validated in Dolibarr. Parent-component relationships require careful sequencing to avoid orphan components — we load parent BOMs first, then child sub-assemblies, then the top-level product. ECN-effective BOM revisions require a scoping decision during discovery: current-effective only or full revision history preserved as notes. Dolibarr's BOM module supports assembly and manufacturing types.

WorkWise Routings define the sequence of operations, work centers, and standard times used in scheduling. We map routing operations to Dolibarr BOM operation lines. Work center capacity and calendar data migrate as work station definitions in Dolibarr's BOM module, but CRP capacity recomputation must run post-migration as a manual validation step.

WorkWise supports unlimited locations and bins. We preserve the full location/bin hierarchy in Dolibarr's multi-warehouse structure, and on-hand quantities migrate including any negative-on-hand or consignment flags. We recalculate available-to-promise during the post-migration inventory validation step.

The WorkWise GL structure includes department cost centers, fixed/variable cost flags, and inter-company segment codes used in job costing. We map accounts by segment code but flag any custom account assignments that do not have a clear Dolibarr GL account equivalent. Dolibarr uses a standard chart of accounts structure that may require chart-of-accounts configuration before posting.

Employee records include payroll integration references, labor rates, and work-center assignments. We migrate the employee master and labor rates into Dolibarr User records or Contact records depending on whether the employee is a system user or a human resource record only. Payroll integration requires re-establishment with the customer's HRIS or payroll provider post-migration.

Work Centers carry capacity, calendars, and cost rates used in CRP calculations. We transfer work-center definitions and their calendar schedules to Dolibarr BOM Work Station records. Capacity-based CRP scheduling is limited in Dolibarr's standard manufacturing module and is flagged as a post-migration planning gap.

WorkWise Job Cost tracks planned vs. actual at Employee, Work Center, Department, Labor/Operation, and Component Material levels. Multi-level Work Orders with sub-jobs aggregate cost across the full tree in WorkWise. We transfer the cost ledger entries as historical moment-in-time values into Dolibarr's product cost history or stock movement records, but Dolibarr does not have an equivalent multi-level job cost engine. The planned-vs-actual comparison capability is lost and must be reconstructed manually in Dolibarr's reporting tools.

WorkWise Quality management stores inspection results, compliance alerts, and traceability links to lots and Work Orders. We map inspection records and preserve the traceability chain as Lot/Serial number metadata on Dolibarr Product records. Destination-specific quality management features (if required) may need a community module or custom development.

The WorkWise mobile app stores real-time shop floor transactions — time approvals, dispatch sequencing, group sequencing — in a separate partition or sync queue. Standard database exports do not automatically capture these records. We explicitly query the mobile sync tables during discovery to determine if time approvals and dispatch data have migration value. If so, we load them as read-only historical notes against the relevant Work Order or Employee records; otherwise they are archived.