Migrate from iXERP Standard to Dolibarr ERP

iXERP Customer records map to Dolibarr Third Party with third_party_type set to Customer. The customer code, name, address, phone, email, website, and payment terms migrate as standard Third Party fields. Each iXERP Customer may have multiple Contacts (persons within the company); these become separate Contact records linked via the socpeople table with fk_soc pointing to the parent Third Party. We resolve the Third Party insert before importing Contacts so that the foreign-key reference is satisfied at load time.

iXERP Vendor records map to Dolibarr Third Party with third_party_type set to Supplier. Supplier code, name, address, payment terms, and accounts payable balance migrate. Vendors may also have Contact records for procurement contacts, which we map to the same socpeople table with a fk_soc reference to the supplier Third Party. Duplicate vendor names (same legal entity appearing as both a customer and a supplier) are flagged during pre-flight for the customer to confirm whether they should be one Third Party with both types or two separate records.

iXERP Contact records (persons attached to Customer or Vendor records) map to Dolibarr socpeople. First name, last name, email, phone, job title, and default flag migrate. The fk_soc foreign key references the parent Third Party. We import all Third Parties before Contacts to satisfy the required reference. If iXERP stores multiple roles per person (e.g., a contact who is both an accounts payable contact and a purchasing contact), we import one socpeople record per role as Dolibarr allows multiple contacts per Third Party.

iXERP Items (stock SKUs, non-stock items, and services) map to Dolibarr Product. Item code becomes ref, description becomes label, cost price maps to cost_price, and selling price maps to price. Stock-on-hand quantity migrates to the stock table via a stock movement record if the product is a stocked item. Barcode fields, unit of measure, and weight/dimensions migrate as extended fields if present in iXERP. Service items (non-stocked) are set to product_type = Service in Dolibarr.

iXERP Purchase Orders map to Dolibarr CommandeFournisseur (Supplier Order). PO header fields (number, date, status, vendor reference) migrate directly. PO lines migrate to the orderline table with product reference, quantity, unit price, and discount percent. Status mapping: iXERP draft/approved/closed maps to Dolibarr draft/validated/closed. We resolve the fk_soc (supplier Third Party) before importing lines. Received-to-date quantities on partially-received POs are preserved as stock movement records in Dolibarr.

iXERP Sales Orders map to Dolibarr Commande (Customer Order). SO header (order number, order date, customer reference, status) migrates directly. Line items map to orderline with product ref, quantity, unit price, and discount. Fulfilled quantity flags (line items already shipped) are preserved as stock warehouse movements in Dolibarr. Order total and tax amount are recalculated at import time from line data rather than relying on the iXERP header total to catch any rounding discrepancies. Status mapping: iXERP open/invoiced/cancelled maps to Dolibarr draft/validated/closed/factured.

iXERP AR Invoices (Issues) map to Dolibarr Facture (Customer Invoice). Invoice header (number, date, due date, customer reference) migrates to facturation. Lines migrate to factored where ref, qty, pu_ht, and tva_tx carry across. Payment status migrates: iXERP paid/unpaid/partially maps to Dolibarr status values with payment date recorded if settled. Multi-currency iXERP invoices are flagged: Dolibarr's standard accounting module does not support native multi-currency, so we record the foreign-currency amount in a custom field and the base-currency equivalent at the prevailing exchange rate from the invoice date.

iXERP AP Invoices (Receipts) map to Dolibarr FactureFournisseur (Supplier Invoice). Supplier reference, invoice number, date, due date, and total migrate. Lines map to the factored table with the same field conventions as AR invoices. Payment status and date migrate. Any discount terms or early-payment conditions from iXERP are stored in custom fields on the Dolibarr invoice because the base module does not natively model early-payment discounts.

iXERP Projects map to Dolibarr Project. Project code, name, description, start date, end date, status, and budget amounts migrate to the projet and projet_task tables. Assigned resources (team members) map to the contact table with a fk_projet reference. Custom project fields from iXERP migrate to the extrafields table for project. Milestone dates migrate as project tasks with milestone flag where supported by the iXERP source data.

iXERP Tasks (children of Projects) map to Dolibarr projet_task with fk_projet pointing to the parent Project. Task name, description, assigned user, status, planned hours, and logged hours migrate. Time entries linked to tasks migrate as separate time records against the task. The task hierarchy (parent task, sub-tasks) is preserved via fk_task_parent. We import Projects before Tasks to satisfy the foreign-key constraint.

iXERP general-ledger account codes, names, and account types map to Dolibarr's accounting account table (accountingaccount). Account type classification (asset, liability, equity, income, expense) migrates to account_type. Tax codes from iXERP map to Dolibarr's TVA (tax) configuration where applicable. Opening balances for each account are entered as manual journal entries after the chart of accounts is loaded because Dolibarr models opening balances as first-period journal lines rather than account attributes.

iXERP bank and cash accounts map to Dolibarr Bank (compta_bank). Account name, account number, bank name, and current balance migrate. Historical bank statement lines migrate to the accounting bank transaction table (compta_bank_conciliation) where date ranges allow; we scope by a mutually agreed cutoff date to avoid loading multi-year transaction histories that exceed Dolibarr's reconciliation UI capacity. Any unreconciled entries at the cutoff are flagged as open items for manual reconciliation post-migration.

iXERP Employee records map to Dolibarr User records for users who will log in, and to Contact records for employees who are recorded for HR or project allocation purposes only. Personal details, job role, department, and effective-date fields migrate. Compensation fields migrate as extended fields on the User record. If Dolibarr HR module is not active, we default employees to User records without login access. Employee address records (multiple per employee) are stored as separate Contact records with a fk_soc pointing to a self-referencing Third Party representing the employee.

iXERP custom fields on any supported object (CRM contacts, projects, employees, items) are detected during the profiling phase and mapped to Dolibarr extrafields (custom properties) on the corresponding object. Where a matching field name and data type exists in Dolibarr, we map directly. Where no match exists, we create a new extrafield on the destination object with a name derived from the iXERP custom field label. Constrained custom fields (drop-downs pointing to other records) are mapped to Dolibarr constrained extrafields referencing the appropriate table rowid.

iXERP HelpDesk tickets map to Dolibarr Ticket (if the Ticket module is enabled in the destination). Ticket subject, description, status, priority, agent assignment, customer reference, and creation date migrate. Conversation history (ticket thread) migrates as separate note or message entries linked to the ticket. Custom ticket fields from iXERP migrate to the ticket extrafields table.