Migrate from etEngine to Dolibarr ERP

etEngine account codes, names, and types (asset, liability, equity, revenue, expense) map to Dolibarr's accounting plan (plan_comptable by default for French locales, or a custom account model). Currency assignments and department codes map to Dolibarr's multi-currency and project associations. We flag any etEngine account segments with no Dolibarr equivalent for custom account model configuration before migration.

etEngine Customer records (contact details, billing address, payment terms) map to Dolibarr Third Party records with the Customer checkbox active and Supplier left unchecked. The etEngine payment_terms field maps to Dolibarr's cond_reglement code. We resolve duplicate third parties (same legal entity appearing as both customer and vendor in etEngine) into a single Dolibarr societe record with both flags set.

etEngine Vendor master records map to Dolibarr Third Party records with the Supplier checkbox active. Contact details, payment terms, and bank information transfer as-is. Historical purchase transactions are migrated separately and linked to the vendor third-party record through purchase order and supplier invoice objects.

etEngine Item masters — SKUs, descriptions, unit prices, cost records, and variants — map to Dolibarr Product records (produit). Item type (stockable, service, inventory) maps to the Dolibarr type field. Custom attributes on items map to Dolibarr Extra Fields (extrafields) configured per product during migration. Price lists migrate to Dolibarr Customer Product Prices.

Outstanding etEngine invoices and credit memos migrate with original dates, amounts, and aging status to preserve the AP/AR trail. We flag any reconciled records in etEngine that should not be carried forward. Dolibarr's accounting module must be enabled to handle invoice/journal linking; if not yet configured, we document the required journal code assignments for the customer's admin to complete before open items are imported.

Past journal entries and transaction history from etEngine are chunked by fiscal period and sequenced in chronological order during migration. Each entry maps to a Dolibarr EcritureComptable record within the appropriate accounting journal (ACHAT, VENTE, BANK, or CASH). We validate that the fiscal period is open in Dolibarr before inserting historical entries to avoid locked-period rejection.

etEngine user accounts map to Dolibarr User records with role and permission assignments. We preserve active versus inactive status and validate that the migration user has permission to create users and assign groups. Dolibarr's permission model is tag-based (read/write/delete per module) rather than profile-based; we document the closest Dolibarr permission group for each etEngine role during scoping.

Attached files and linked documents exported from etEngine are written to Dolibarr's document directory and re-linked to their corresponding records (Third Party, Product, Invoice, Project) via Dolibarr's document management module. File naming follows Dolibarr's directory convention (ref/entity/documents) to ensure the document index remains consistent.

If etEngine contains project or job records, these map to Dolibarr Project objects with task hierarchies preserved. Dolibarr's project-to-invoice linking allows billable project tasks to generate customer invoices, which etEngine may handle differently; we flag this discrepancy during scoping and document the recommended Dolibarr configuration.

Any etEngine custom fields identified during scoping have no automatic export path and must be matched manually to Dolibarr's Extra Fields system (extrafields on llx_societe, llx_product, llx_facture, etc.). We document each etEngine custom field's name, data type, and current values, then configure the equivalent Dolibarr Extra Field before migration so that data can be loaded in the same pass as the parent record.

etEngine contact persons attached to Customer or Vendor records map to Dolibarr Contact records linked to the parent Third Party via the srowid (fk_soc) foreign key. Multiple contacts per third party are supported. Email, phone, and role fields transfer; Dolibarr's contact roles (commercial, accounting, technical) are matched to etEngine role values during mapping.

Open and historical purchase orders from etEngine map to Dolibarr Supplier Orders with status preserved (draft, validated, sent, received). Line items map to commande_fournisseurdet records with product reference and quantity resolved. Closed purchase orders migrate as historical records with status set to closed to avoid triggering Dolibarr's receiving workflow.