Migrate from Perfecto ERP to Dolibarr ERP

Perfecto ERP Chart of Accounts with multi-level hierarchical account structures map to Dolibarr's accounting chart. We preserve parent-child relationships using the pcg_version and account_number fields, mapping each account level so that account grouping and totals carry forward correctly. Where Dolibarr uses a flat account list with category tags, we reconstruct the hierarchy as parent-account assignments in Dolibarr's llx_accounting_account table.

General Ledger journal entries from Perfecto ERP map to Dolibarr's llx_accounting_bookkeeping table. We preserve journal entry numbering sequences, transaction dates, account references, debit/credit amounts, and the general_ledger_code description field. Where Perfecto ERP uses sub-ledger postings for cost centres, we tag these as project assignments in Dolibarr since Dolibarr lacks native cost centre fields.

Perfecto ERP Customer records map to Dolibarr Third Parties with the customer flag enabled. Name, contact, address, payment terms, and tax registration fields migrate 1:1. Any End-User Customization Studio custom fields on the Customer object are flagged during discovery and added to the Dolibarr import template as extended columns before extraction.

Vendor records follow the same structure as Customer records in Perfecto ERP and map to Dolibarr Third Parties with the supplier flag enabled. Vendor-specific fields including tax registration number, payment terms, and bank details transfer to the Dolibarr llx_societe table. We preserve the vendor-specific codes used in Perfecto ERP's supply chain module as Dolibarr's supplier code field.

Items including finished goods, raw materials, and services map to Dolibarr llx_product. We preserve SKU from Perfecto ERP as ref in Dolibarr, unit of measure, price fields, and stock levels. BOM relationships require a separate migration pass after the base Item records are loaded, as component references must resolve to existing product IDs in Dolibarr.

Perfecto ERP BOM structures with parent items and component quantities map to Dolibarr's BOM module (llx_bom and llx_bomline). We sequence BOM migration as a separate pass after base Items are committed, so that parent product IDs are available for lookup at import time. Component quantities, wastage percentages, and BOM cost prices transfer to Dolibarr's bomline table. If the customer's Perfecto ERP BOM uses multi-level nesting, we flatten to single-level BOMs in Dolibarr and document the hierarchy for manual reconstruction if needed.

Employee profiles including name, job title, department, and employment status map to Dolibarr llx_societe (as contacts with employee type) or the dedicated HR module if the customer activates it. We extract employee records alongside their assigned Roles and Permissions to reconstruct user access levels in Dolibarr. Active employee status maps to Dolibarr's employee flag on the contact record.

Perfecto ERP role-based security assignments extract from the role-permission matrix and map to Dolibarr's permission system. Perfecto ERP's module-level and field-level access control has no direct Dolibarr equivalent, so we map the nearest Dolibarr permission (read/write/delete per module) and document the granular field-level restrictions that require manual configuration in Dolibarr's user permission panel post-migration.

Perfecto ERP file attachments stored as file references linked to records are exported to a neutral file store (S3-compatible or local directory) during migration. We map the original attachment paths to Dolibarr's document directory structure and recreate the record-level links post-import so that attached invoices, images, and documents remain accessible from the correct Dolibarr record. File paths are not portable between systems; we handle relinking as part of the post-import phase.

Purchase orders from Perfecto ERP's Supply Chain Package map to Dolibarr llx_commande_fournisseur. We preserve order date, supplier reference, line items with quantities and unit prices, and order status. The supplier reference on the Dolibarr order resolves to the Third Party record migrated from the Vendor object.

Sales orders map to Dolibarr llx_commande. Order date, customer reference, line items, quantities, and order status transfer directly. Customer reference resolves to the Third Party customer record. Dolibarr's order workflow status values (draft, validated, shipped, closed) map from Perfecto ERP's corresponding order lifecycle stages.

Perfecto ERP Approval Workflows define custom approval chains tied to specific transaction types. Dolibarr has no built-in approval workflow engine; this is a gap that Dolistore modules address. We extract workflow definitions as a written configuration document describing the trigger, approver chain, and conditions for each workflow, and advise the customer to evaluate and install a suitable Dolistore approval module post-migration.