Migrate from Open-Prod to Dolibarr ERP

Open-Prod customer and account records map to Dolibarr Third Parties (table llx_societe). We extract customer name, address fields, phone, email, and VAT number and map them to Dolibarr's corresponding fields. Third Party type in Dolibarr (Customer, Supplier, or Both) is set based on Open-Prod's account classification. Customer code from Open-Prod becomes the ref_client field in Dolibarr for cross-system reconciliation.

Open-Prod item records map to Dolibarr Product records (table llx_product). The Open-Prod product type (finished good, raw material, service) determines Dolibarr's fk_product_type (0 for stockable, 1 for service). Product code from Open-Prod becomes the ref field in Dolibarr. Pricing tiers from Open-Prod map to Dolibarr's price levels if the Multiprice module is activated.

Open-Prod inventory positions map to Dolibarr Stock (table llx_product_stock) and Stock Movement records (llx_stock_mouvement). Current quantity, warehouse location, and last movement date transfer to Dolibarr. We flag that Dolibarr requires the Stock module to be activated; if it is not, we configure it before inventory import. Open-Prod warehouse identification maps to Dolibarr's entrepot records (llx_entrepot).

Open-Prod sales orders and invoices map to Dolibarr Proposal (llx_propal) and Order (llx_commande) records. Order status from Open-Prod maps to Dolibarr's statut field values (draft, validated, closed). Line item data transfers to llx_commandedet with product reference, quantity, unit price, and VAT rate resolved from the product mapping. Historical invoice totals must reconcile against Open-Prod's accounting module export.

Open-Prod purchase orders to suppliers map to Dolibarr Supplier Orders (llx_commande_fournisseur). Supplier identification resolves via the Third Party mapping. Line items with product reference, quantity, and cost price transfer to llx_commande_fournisseurdet. Status mapping follows the same pattern as customer orders. We note that Open-Prod's supplier invoice matching (three-way match) is not a standard Dolibarr AP feature without the Purchase workflow module.

Open-Prod accounting module invoices map to Dolibarr Facture records (llx_facture for customers, llx_facture_fourn for suppliers). Invoice header data (customer ref, date, due date, payment terms) transfers directly. Line items map to llx_facturedet. VAT amounts must reconcile against Open-Prod's tax accounting output. We flag that Open-Prod may store invoice PDFs in a proprietary format that requires conversion before upload to Dolibarr's document management.

Open-Prod project records map to Dolibarr Project (llx_projet). Project name, description, start and end dates, status, and budget transfer. Open-Prod tasks and milestones map to Dolibarr Task (llx_projet_task) and TaskTime records. Task dependencies from Open-Prod are noted as an attribute we capture but cannot enforce in Dolibarr's task model without manual configuration. We deliver a task-dependency map as a written artifact for the customer's admin.

Open-Prod after-sales service records map to Dolibarr Interventions (table llx_fichinter) if the Interventions module is activated. Ticket status, priority, assigned technician, and resolution notes transfer. Open-Prod's service record type classification maps to Dolibarr intervention type. If the customer uses Dolibarr's Ticket module (separate module), service records can alternatively map to Ticket records; the choice depends on whether the customer wants service-as-intervention or service-as-ticket workflow.

Open-Prod production work orders map to Dolibarr MRP Production records if the MRP module is active in the destination. Bill of Materials from Open-Prod maps to Dolibarr llx_mrp_production. This mapping requires the MRP module to be licensed and activated in Dolibarr, which is an add-on cost. If the MRP module is not activated, we flag production orders as out of scope and deliver a written BOM and work-order inventory for the customer to configure manually.

Open-Prod user and owner records map to Dolibarr User accounts (llx_user). We match by email address. Open-Prod user roles (admin, operator, viewer) map to Dolibarr's permission groups. Active status is preserved. Users without a matching email in the destination go to a reconciliation queue for the customer's admin to provision before record import.

Open-Prod custom fields are not migratable by default because the schema is not publicly documented. During scoping, we request access to the customer's Open-Prod configuration to extract custom field definitions. If we can retrieve the custom field metadata, we pre-create matching Extra Fields in Dolibarr using the CustomFields module before data import. Without schema access, we document the custom field gap in the migration inventory and recommend manual data re-entry for critical custom attributes.

Open-Prod attachment export is not confirmed via a documented API or export mechanism. We cannot automatically migrate attachments. During scoping, we ask the customer to confirm whether Open-Prod attachments are stored in a file system accessible via FTP or direct database query. If accessible, we extract them and upload to Dolibarr's document directory (/documents/) linked to the relevant record. If not accessible, we flag attachments as out of scope and deliver a written inventory of document locations in Open-Prod for manual handoff.