Migrate from Tranquil ERP to Dolibarr ERP

Tranquil ERP account hierarchy (Assets, Liabilities, Equity, Revenue, Expenses with sub-accounts) maps to Dolibarr's Accounting module plan comptable. We extract the full account tree including inactive flags and account codes, then create matching account records in Dolibarr using the Accounting::addAccount API endpoint or direct SQL INSERT into llx_accounting_account. Account type mapping (compte de tiers, compte collectif, compte racine) is assigned based on Tranquil's account classification. Duplicate account codes are flagged in a pre-flight report for the customer's finance admin to resolve before import.

Tranquil ERP Customer records (contact details, payment terms, transaction history) map to Dolibarr ThirdParty with Type=Customer. The Tranquil customer code becomes the ref_int or code_client field in Dolibarr. Open AR balances are preserved by linking migrated invoice records to the corresponding ThirdParty ID after import. Customer address, email, phone, and payment term code migrate directly; any Tranquil custom fields on Customer migrate to Dolibarr CustomFields entries.

Tranquil ERP Vendor master records (contact information, bank details, purchasing history) map to Dolibarr ThirdParty with Type=Supplier. The Tranquil vendor code becomes the code_fournisseur field. Open AP balances link to migrated purchase order and invoice records. Bank details from Tranquil (account number, SWIFT/BIC, bank name) migrate to Dolibarr's Rib (bank account) records attached to the ThirdParty. Vendor naming inconsistencies and duplicate vendors are deduplicated during the pre-flight data audit.

Tranquil ERP Items with serial/batch numbers, expiry dates, and multi-UoM configurations map to Dolibarr Product records. The product type (stockable, service, assembly for BOM) is set based on Tranquil's item type classification. Multi-UoM conversions migrate to Dolibarr's unit-of-measure associations on the Product record. Serial and batch tracking attributes migrate to the Stock module's lot/serial number fields, and expiry dates populate the dlc (use-by date) field in the stock lot table. Barcode (UPC/EAN) from Tranquil maps to the barcode field on Product.

Tranquil ERP Purchase Orders with line items, quantities, supplier links, and status flags migrate to Dolibarr Commande Fournisseur. The vendor link resolves to the migrated ThirdParty ID; line items resolve to migrated Product IDs. Open POs retain status=draft or status=validated depending on Tranquil's status flag; closed POs migrate with status=closed and are flagged as historical records. PO totals and taxes recalculate against Dolibarr's price calculation engine to verify alignment with the source total.

Tranquil ERP Sales Orders with customer references, line items, pricing, and fulfillment status migrate to Dolibarr Commande Client. Customer references resolve to migrated ThirdParty IDs; line items resolve to migrated Product IDs. Open orders migrate in full with their current fulfillment state; completed orders migrate with status=closed and final shipment tracking preserved. Pricing including discounts and tax rates migrates as-is, and Dolibarr's price calculation validates the order total against the source.

Tranquil ERP stock levels across warehouses map to Dolibarr Stock with one warehouse per Tranquil warehouse location. We extract current quantities, warehouse assignments, reorder thresholds, and serial/batch assignments. Dolibarr warehouse configuration (llx_entrepot) is created before stock import, and stock movements (llx_stock_mouvement) are logged with the original transaction timestamp. Reorder point from Tranquil maps to Dolibarr's pmp (average purchase price) and reorder threshold fields on the Product-Warehouse relationship.

Tranquil ERP manufacturing items with BOM routing migrate to Dolibarr's BOM module if the customer uses Tranquil's manufacturing capabilities. The BOM structure (parent product, component products, quantities per assembly) maps to llx_bom_bom and llx_bom_bomline tables. Workstation and labor routing data from Tranquil's production module migrates to Dolibarr's product batch production capabilities if the production module is activated.

Tranquil ERP Employee records with personal data, roles, and compensation history migrate to Dolibarr's Employee module (llx_establishment or llx_holiday). The HR module must be activated in Dolibarr before import. Effective-dated compensation fields migrate to salary records in the HR module, but advanced payroll tax calculation is not included; the customer reviews and re-enters payroll configurations appropriate to their jurisdiction. Employee status (active/inactive) from Tranquil maps to Dolibarr's status field on the establishment record.

Tranquil ERP projects and associated tasks migrate to Dolibarr's Project (llx_projet) and Task (llx_projet_task) tables. Project status, dates, budget, and description migrate directly. Task hierarchy (parent task, subtasks), time tracking (hours logged), and task assignments to employees migrate to Dolibarr Task records with time allocation fields. Project contacts (internal team members, external contacts) migrate as Project contacts linked to migrated ThirdParty or User records.

Tranquil ERP custom field definitions on business objects migrate to Dolibarr's CustomFields module configuration. We detect custom field names, data types, and picklist values during discovery, then pre-create the matching CustomFields entries in Dolibarr before importing any records that populate them. Tranquil custom fields with complex data types (date ranges, conditional visibility) are documented in the handoff report with recommended Dolibarr configuration equivalents. Custom field values on records migrate in the standard field mapping pass.

Tranquil ERP file attachments associated with records (invoices, POs, items, employee records) migrate to Dolibarr's ecm module with folder structure matching the source object. We extract binary files from Tranquil's document storage, create matching directories in Dolibarr's documents directory, and attach them to the corresponding record via the document management API. Large attachments (>10MB) are flagged for separate transfer to avoid API chunking issues.