Migrate from MONITOR ERP to Dolibarr ERP

MONITOR ERP Customer records (address, contact, currency, payment terms) map to Dolibarr ThirdParty records with the ThirdParty category field set to customer. We extract via configured file-export paths, transform address fields into Dolibarr's address format, and load via Dolibarr REST API. Currency and payment terms map to Dolibarr's condreglement and modepayement foreign keys. The customer-supplier split (MONITOR ERP separates Customers and Suppliers; Dolibarr uses a single ThirdParty object with a category flag) is resolved at migration time based on the source record type.

MONITOR ERP Supplier records mirror the Customer structure and map to Dolibarr ThirdParty with category=supplier. Linked Purchase Orders and Accounts Payable positions are migrated as separate record types after the Supplier record is established. We preserve the supplier code from MONITOR ERP as the ref_supplier field in Dolibarr for cross-reference.

MONITOR ERP Items (BOM links, routing data, unit of measure, cost, inventory levels) map to Dolibarr Product records. BOM relationships are preserved as separate Product parent-child records with a custom field bom_parent_id__c linking to the parent Product. Routing data does not have a direct Dolibarr equivalent in core; we map routing steps to Dolibarr Project tasks and flag this as a configuration gap requiring post-migration review by the customer's production team.

MONITOR ERP Sales Orders (status, lines, delivery dates, pricing) map to Dolibarr Order. We extract the full order history via file export, map order status (draft, validated, shipped, invoiced, closed) to Dolibarr statuts (draft, validated, sent, delivered, closed) using the closest equivalent. Open orders require special handling to avoid duplicates: we flag any MONITOR ERP order with a status that implies an open fulfillment obligation for manual verification before load.

MONITOR ERP Purchase Orders (status, lines, expected delivery) map to Dolibarr SupplierOrder. The supplier reference from the linked Supplier record is resolved as the socid foreign key before Purchase Order import begins. Expected delivery dates map to date_livraison in Dolibarr. Any purchase order remaining open post-migration is flagged for the customer's admin to verify before re-opening in Dolibarr to avoid duplicate fulfillment obligations.

MONITOR ERP Production Orders carry embedded routing, work-centre assignments, and traceability links to lots that have no single Dolibarr equivalent. We decompose each Production Order into a Dolibarr Project (carrying the production order header and status) with linked Task records representing each routing step. Work-centre assignments map to a custom Task field work_centre__c. Lot and serial traceability is preserved in a custom lot_reference__c field on the Project and linked to any resulting inventory records. This decomposition is the most significant schema transformation in this migration pair and requires pre-migration validation with the customer's production team.

MONITOR ERP Accounts Receivable invoices map to Dolibarr Facture with type=customer. Invoice headers and lines export via configured file paths. We perform field-level mapping of line descriptions, quantities, unit prices, and tax rates. MONITOR ERP's VAT handling is preserved as the local tax rate equivalent in Dolibarr. Historical invoices migrate as closed (paid or outstanding based on MONITOR ERP payment status) to avoid triggering Dolibarr's accounting generation for closed periods.

MONITOR ERP Accounts Payable invoices map to Dolibarr Facture with type=supplier. The supplier reference is resolved as socid before AP invoice load. Payment terms, due dates, and outstanding amounts migrate to preserve the AP aging report in Dolibarr. We flag any AP invoice with a status suggesting a payment dispute for manual review before load.

MONITOR ERP General Ledger journal entries export in batches via file export without date-range filtering at the export level. We handle this by exporting to a working directory, performing in-house date filtering and chunking to avoid large file handling, then loading into Dolibarr's accounting module. Account codes map to Dolibarr's Plan de Compte (French accounting plan) structure, with MONITOR ERP account-numbering conventions preserved in the account code field and a description field carrying the original MONITOR ERP account name. Multi-year journal migration requires period-by-period validation to ensure each entry lands in the correct fiscal year in Dolibarr.

MONITOR ERP inventory positions (quantity by Item, Warehouse, Lot/Serial) export as stock reports. We map these to Dolibarr Product Stock records, preserving warehouse assignments as entrepot records in Dolibarr. Lot and serial number fields require dedicated handling: MONITOR ERP's lot traceability links are stored as properties on the Production Order rather than as standalone lot records, so we reconstruct lot numbers from the production order traceability data and assign them during the inventory load phase. Any inventory discrepancy (negative stock in MONITOR ERP) is flagged for physical count reconciliation before load.

MONITOR ERP account codes, descriptions, and account types export via file. We map these to Dolibarr's accounting chart (for EU companies, the PCMN or PCG structure is commonly used). MONITOR ERP's account-numbering conventions may conflict with Dolibarr's default account structure; we configure the chart of accounts in Dolibarr before any transactional data loads and flag any accounts that require custom numbering rules. This is a prerequisite for journal entry and invoice migration.

MONITOR ERP Bank accounts and cash accounts export via file paths. We map these to Dolibarr Bank Account records and reconcile opening balances against the latest trial balance exported from MONITOR ERP. Any bank account with a non-zero opening balance requires a manual balance verification step from the customer's finance team before we close the migration reconciliation.

MONITOR ERP User records include login, name, and role assignments. We map these to Dolibarr User records, preserving the role (login, password, group) where MONITOR ERP role names are extractable. Passwords do not migrate; we provision placeholder credentials for each migrated user and flag that the customer's admin should distribute new credentials post-migration. Department associations migrate to Dolibarr's hierarchical team structure where present in MONITOR ERP.

Documents attached to Customer Orders, Items, or Production Orders in MONITOR ERP are stored in the file store and are not accessible via the standard API query endpoint. File export configuration varies by installation and cannot be automated end-to-end. We flag this as a manual export step in our scoping report: structured transactional data migrates via API and file export, but binary attachments require each user to navigate MONITOR ERP and save files individually to a shared directory for re-upload into Dolibarr after migration. This is a partial-data limitation documented in the migration scope.