Migrate from ManEx to Dolibarr ERP

ManEx Customer records (contact details, account assignments, address data) map to Dolibarr ThirdParty with Type=Customer. The flat customer schema in ManEx maps directly to llx_societe and llx_societe_address. We extract via direct DB query or UI export, validate address completeness against ManEx application records, and import into Dolibarr's thirdparty module. Multi-address records require splitting into separate ThirdParty addresses in Dolibarr.

ManEx Vendor master data is a distinct entity with PO history and RMA associations. We preserve vendor-supplier relationships separately during migration to avoid merging suppliers with customers, mapping to Dolibarr ThirdParty with Type=Supplier. Vendor code and payment terms from ManEx map to Dolibarr's code_ Fournisseur and cond_reglement fields. PO history links are preserved as notes or PDF attachments where the original ManEx PO records are documented.

ManEx GL accounts with standard types (asset, liability, equity, revenue, expense) map to Dolibarr's chart of accounts. We map each ManEx account code and type to the Dolibarr pcg_type and pcg_subtype columns, flagging inactive or suspended accounts for the customer's admin to review before activation. Historical trial balance data from ManEx is imported as opening entries in Dolibarr's accounting module.

ManEx PO records with line items, vendor assignments, and receiving status map to Dolibarr CommandeFournisseur (Supplier Order). Partially received POs require explicit status mapping: ManEx receiving status flags translate to Dolibarr ligne and reception objects. The PO-to-receiving linkage is preserved by importing orders first, then reception records with the order line references resolved at migration time.

ManEx Sales Order records with pricing, customer linkage, and fulfillment status map to Dolibarr Commande (Customer Order). Multi-price-list pricing on ManEx SOs requires value-mapping because price list IDs are not portable across ERP systems; we import price list definitions as Dolibarr price levels and recalculate SO totals against the destination price rules. Order status (Draft, Validated, Shipped, Closed) maps directly.

ManEx BOM records with multi-level component structures and routing data map to Dolibarr's Product BOM module. Complex multi-level BOMs with phantom assemblies require decomposition during migration; we flatten or preserve hierarchy based on the customer's Dolibarr configuration preference. The ManEx bom_type field is translated to Dolibarr's bom_type (M for manufacture, K for kit). Each BOM component row maps to llx_bom_bomline with quantity and unit of measure.

Real-time ManEx shop floor data (labor time, machine cycles, material consumption per work order) has no native Dolibarr equivalent at the MES level. We map this data to Dolibarr Project records with time tracking enabled and structured notes documenting the original ManEx shop floor fields. The customer's admin recreates detailed shop floor tracking using a third-party Dolibarr manufacturing module or external MES if required. We flag this gap in the migration inventory.

ManEx inventory quantities, locations, and lot/serial data from the materials management module map to Dolibarr Product records with stock enabled. Multiple warehouse locations map to Dolibarr warehouses (llx_entrepot), and lot traceability is preserved via llx_product_lot. On-hand quantities import into llx_product_stock with warehouse linkage. Serial number tracking uses llx_product_lot with serial number fields.

Open payables and receivables migrate with current status, aging buckets, and payment terms. Historical transactions require special handling because ManEx may store them in archived or compressed formats; we extract what is accessible from the UI export or direct DB and flag unrecoverable historical records. ManEx invoice status codes map to Dolibarr status values (Draft, Unpaid, Paid, Cancelled). Aged creditor/debtor balances import as opening entries in Dolibarr's accounting module.

Time entries from ManEx's optional Time and Attendance module are tied to employees and work orders. If Dolibarr's project module is activated, we map time entries to llx_projet_task_time with employee mapping resolved by email or employee ID. If the destination has no HR module, we flag time entries for manual recreation or third-party HR module installation. This module is often inactive in ManEx; we confirm status during scoping.

ManEx RMAs with return or repair states tied to original SOs or POs map to Dolibarr Intervention records. RMA status codes (open, in-progress, closed) require explicit value-mapping because the state machine differs between systems. We map RMA origin references to the linked Dolibarr Order or SupplierOrder and preserve RMA description, resolution notes, and timestamps in the Intervention's description and date fields.

ManEx stores custom fields in proprietary database columns without a standard naming convention. We identify all non-standard columns in the ManEx source tables during database audit, map them to Dolibarr extrafields using the extrafields module, and create the attribute codes (options_*) in the appropriate llx_extrafields tables before importing the corresponding data. Custom field types are inferred from ManEx column data types (varchar, int, date, decimal). This mapping is built per-customer during the discovery phase.