Migrate from Manu Online to Dolibarr ERP

Manu Online Products (manufactured, resold, and purchased variants) map to Dolibarr Products. The product type in Manu Online (Stockable, Service, Non-Stock) maps to the Dolibarr type field. Unit of measure, description, and barcodes transfer directly. Manu Online cost layers (FIFO layers) require a costing-method decision during scoping: if Dolibarr's average cost is selected, we compute the weighted average from Manu Online's cost layers and apply it at migration time, flagging any product with a cost variance exceeding 10 percent for customer review.

Manu Online BOMs define the ingredient list and quantities per finished good. In Manu Online Enterprise Edition, BOMs can be multi-level (sub-assemblies within sub-assemblies). Dolibarr's BOM module supports single-level recipes; multi-level structures must be flattened into a single-level recipe or decomposed into separate BOMs with a parent assembly relationship. We audit the customer's BOM depth during scoping and either collapse multi-level BOMs into single-level recipes (using the top-level finished product as the recipe and rolling up all component quantities) or document the decomposition as a separate configuration step if the customer intends to license the MRP module.

Current on-hand quantities, allocated quantities, and ordered quantities per product per warehouse transfer to Dolibarr Stock. The warehouse concept maps directly if Manu Online uses single-warehouse (Mini Enterprise) or multi-warehouse (Enterprise). Serial and lot numbers transfer as stock movement records linked to the receiving stock transaction. We preserve the FIFO cost layer on hand by setting Dolibarr's unit cost to the weighted average from Manu Online's cost layers, and we flag any product with a negative stock position for customer reconciliation before migration.

Manu Online Customers (with address, contact, tax registration, and price list assignment) map to Dolibarr Third Parties with the third-party type set to Customer. Email, phone, address, VAT number, and payment terms transfer directly. Open sales orders and credit limits are stored on the customer record in Manu Online; we map credit limit to Dolibarr's local_info credit limit field and note that open sales order references transfer as linked order records rather than customer-level fields.

Manu Online Suppliers (with address, contact, lead-time, and preferred units of purchase) map to Dolibarr Third Parties with the type set to Supplier. Supplier product code and lead time transfer to Dolibarr's supplier info block. Purchase order history and outstanding POs transfer with the supplier as a linked parent rather than a field on the supplier record.

Open and historic sales orders map to Dolibarr Orders. The order status (Draft, Confirmed, Partially Dispatched, Completed, Cancelled) maps to Dolibarr's status workflow. Line items transfer with product reference, quantity, unit price, and discount. Partially dispatched lines in Manu Online require a status translation to Dolibarr's shipment-linked status; we map the most recent dispatch state and note any fully undispatched lines as pending fulfilment.

Open Purchase Orders link to the supplier Third Party and carry expected delivery dates and received-versus-ordered quantities. We map the receipt state so that partially received POs show the received quantity in Dolibarr and mark remaining quantities as outstanding. Fully received POs are mapped as closed. POs linked to Manu Online Works Orders (where the PO was raised to supply a production run) are flagged separately during scoping since Dolibarr's project or MRP module may need to be configured to receive stock directly against a production order.

Manu Online Works Orders drive production: they reference a BOM, allocate stock, and record labour time and completed quantities. In Dolibarr, production planning requires the MRP/BOM module. If the customer has not licensed this module, we map Works Orders to Dolibarr Projects with a production-oriented task structure (one task per production stage) and link the associated product and quantity as project-level metadata. Any unfinished work-in-progress at migration time is documented as an open project task requiring manual resolution or completion in the new system.

Posted invoices in Manu Online carry accounting implications, especially when Xero has already received the data. We coordinate a cutover date with the customer during scoping. Invoices with a status of Posted and a Xero-sync date before the cutover are excluded from migration or marked as historical in Dolibarr to prevent double-posting in Xero. Invoices with a status of Draft or Sent (not yet posted) transfer to Dolibarr as draft invoices for the customer's team to review and post in the new system. Credit notes map to Dolibarr credit notes linked to the original invoice.

Traceability records link serial or lot numbers to stock transactions, works orders, and delivery documents. This data is exportable via the DataWarehouse. We run a pre-migration data quality check that reports the percentage of stock lines with complete traceability (supplier lot recorded at goods receipt, lot linked to works order, lot linked to delivery). If the customer historically received stock without recording supplier lot numbers, the inbound traceability leg will be blank; we surface this gap before migration begins and allow the customer to decide whether to populate retrospectively or accept the gap in Dolibarr.

Manu Online user accounts carry login, email, and role-based permissions. Active users map to Dolibarr User records by email match. Roles in Manu Online do not map directly to Dolibarr permission groups; we flag any user with elevated admin privileges in Manu Online for explicit re-creation in Dolibarr's permission setup (Home - Setup - Users - Permissions). Inactive users are not migrated but are documented in the handoff inventory for the customer's admin to handle.

Manu Online supports custom fields on products, customers, and orders in some tiers. The DataWarehouse export may not include all custom field definitions or their current values. We inventory custom fields during scoping by reviewing the Manu Online UI alongside the DataWarehouse schema. For any custom field that appears in both, we map it to a Dolibarr Extra Field (Setup - Other Setup - Extra Fields). Fields that do not appear in the DataWarehouse are flagged as potentially incomplete and may require manual data entry or a separate data-capture step after migration.

Manu Online price lists assign specific unit prices per customer or customer group. Dolibarr handles this through the Customer Product Price module (available from the Products menu). We map Manu Online price list entries to Dolibarr customer-specific price rows, linking each to the correct Third Party and Product. If the customer uses a default price list only, we apply the standard product selling price in Dolibarr.

Manu Online product categories map to Dolibarr Categories. The category type in Dolibarr is set to Product. Category assignment on products transfers as Category lines linked to the product record. Categories used for reporting or filtering in Manu Online are preserved as Dolibarr Categories for equivalent reporting groupings.