Migrate from Masterplan to Dolibarr ERP

Masterplan Customers map directly to Dolibarr Third Parties with the Third Party type set to Customer. We preserve full billing and shipping addresses, payment terms, credit limits, and currency settings from Masterplan. Dolibarr stores these in llx_societe (the main third-party table) with address data in llx_societe_address. We use Dolibarr's built-in CSV import for Third Parties or direct database insertion depending on record count and custom field density.

Masterplan Vendors map to Dolibarr Third Parties with type set to Supplier. W-9 data and 1099 eligibility flags from Masterplan have no direct Dolibarr equivalent, so we map these to custom fields in llx_societe_extrafields. Vendor payment terms and address data migrate 1:1 into the corresponding Dolibarr fields.

Masterplan Items with item types Finished Goods, Raw Materials, and Components map to Dolibarr Product records. Item costing method (FIFO, Average, Standard) from Masterplan maps to Dolibarr's cost price field. Masterplan's product type classification maps to Dolibarr's product_type field (0=Product, 1=Service). We extract the item type and costing configuration to preserve the cost structure in Dolibarr's price management.

Masterplan Service items map to Dolibarr Product records with product_type=1. Unit of measure, description, and default billing price migrate directly. Dolibarr's service-specific fields (duration, unit of time) are populated where Masterplan provides service duration data.

Masterplan GL accounts map to Dolibarr accounting Account records (llx_accounting_account). We preserve account numbers, names, types (Asset, Liability, Equity, Revenue, Expense), and optional department or cost-center rollups. Dolibarr's accounting module is simpler than Masterplan's; cost-center rollups that exceed Dolibarr's basic accounting structure are flagged for manual account mapping post-migration.

Outstanding payables from Masterplan map to Dolibarr Supplier Invoices with status=draft or unpaid depending on approval state. Invoice number, amount, due date, and aging bucket migrate directly. Masterplan aging bucket configurations vary by customer; we normalize them to standard 30/60/90/120-day buckets in Dolibarr. Vendor lookup resolves via the Third Party (Supplier) mapping from object order 2.

Outstanding receivables map to Dolibarr Customer Invoices with status=draft or unpaid. Invoice number, amount, due date, and aging bucket normalize to standard 30/60/90/120-day buckets. Customer lookup resolves via the Third Party (Customer) mapping from object order 1. Historical invoices older than Masterplan's configurable archive cutoff are excluded and noted as out-of-scope.

Open Sales Orders from Masterplan map to Dolibarr Customer Orders (llx_commande). Line items, quantities, unit prices, and fulfillment status migrate. We flag partially shipped orders explicitly so that Dolibarr's shipment handling (Dolibarr's Expedition module) processes them correctly. Sales Order status maps to Dolibarr order status (draft, validated, approved, shipped, delivered).

Open Purchase Orders map to Dolibarr Supplier Orders (llx_commande_fournisseur). Line items, quantities, unit prices, and receipt status migrate. Partially received orders are flagged for manual receipt processing in Dolibarr's supplier order reception workflow.

On-hand quantities per warehouse location and bin in Masterplan map to Dolibarr product-stock records (llx_product_stock). We extract stock levels per location and reassign to Dolibarr warehouse structures, which often differ in naming and hierarchy. Multi-bin Masterplan configurations require flattening to Dolibarr's single-level warehouse model.

Multi-level BOMs with component quantities, scrap factors, and phantom assemblies require either flattening or preservation depending on Dolibarr's BOM module activation. Dolibarr's BOM module (part of the MRP module) supports multi-level BOMs but with less manufacturing depth than Masterplan's routing configuration. We extract the full BOM tree from Masterplan, discuss the target structure with the customer, and map accordingly. Phantom assemblies map as BOMs with type=1 (kit) in Dolibarr.

Work orders track status (Released, In Process, Complete, Closed), routing steps, labor hours, and material allocations in Masterplan. Dolibarr's MRP module supports Manufacturing Orders (MO) but with simpler routing than Masterplan's discrete manufacturing routing. We map Work Order status to MO status, preserve material allocations from Masterplan's BOM association, and flag any routing steps that exceed Dolibarr's simple routing model as requiring manual scheduling post-migration. If the customer does not activate the MRP module, Work Orders map to Projects as a workaround.