Migrate from Dolibarr ERP to Acumatica

Dolibarr's single third-party record carries both customer and supplier data. The migration splits this into separate Acumatica Customer and Vendor records keyed by CustomerClassID and VendorClassID. Classification records must exist in Acumatica before the import runs; any Dolibarr third-party without a type flag creates a Customer record only by default.

Dolibarr contacts map to CustomerContact in Acumatica, linked via CustomerID. Multiple addresses per third-party in Dolibarr become separate Address records in Acumatica with individual AddressID values. The primary contact flag maps to the IsPrimaryContact checkbox. Secondary contacts attach with IsPrimaryContact cleared. Email and phone fields transfer directly; job title maps to the Title field on the contact record.

Dolibarr's single products table routes to different Acumatica item types based on the product_type field: 'product' with stock tracking becomes StockItem (with StockItemMaint and Bill of Materials if applicable), 'service' becomes ServiceItem, and products without stock management become NonStockItem. ItemClassID mapping requires pre-created item classes in Acumatica.

Dolibarr warehouse stock records map to Acumatica warehouse sites (INSite) and bin locations (INLocation). The physical quantity and reserved quantity fields transfer as OnHandQty and AvailableQty respectively. Multi-warehouse Dolibarr setups require corresponding site creation in Acumatica before stock loads. Bin-level transfers in Dolibarr map to INLocation records linked to the target warehouse site.

Dolibarr distinguishes customer orders from supplier orders by the order's sjointype field. Customer orders map to SalesOrder (with SOOrderType and status routing); supplier orders map to POOrder. The doc_date field maps to OrderDate and must fall within an open FinPeriod for the order to be saved. Order total maps to CuryLineTotal with tax handled separately.

Dolibarr customer invoices map to ARInvoice (with DocType=INV); supplier invoices map to APInvoice (DocType=INV). The invoice_date and due_date fields map to DocDate and DueDate respectively, both requiring an open FinPeriod. Line items carry ProductID, CuryUnitCost, and Qty, with DiscPct handling early-payment discounts. DocNumber preserves the Dolibarr ref as ReferenceNbr for traceability.

Dolibarr commercial proposals migrate to SalesQuote in Acumatica. The status lifecycle (draft, validated, signed, notsigned, closed) maps to Acumatica's SalesQuote status workflow. Quote lines carry the same product, quantity, and pricing structure as order lines. Expiration dates transfer as ExpirationDate on the quote header.

Dolibarr projects map to PMProject with ProjectID, Description, CustomerID (lookup to Customer record), status, and date fields. Tasks map to PMTask under each project. Time entries and expenses become EPEmployeeTime entries linked to the project task. Project cost budget tracking uses PMBudget, which requires Acumatica's Project Accounting license tier.

Support tickets in Dolibarr map to CRCase in Acumatica's CRM module. The ticket subject, description, and creation date transfer as CaseCD, Subject, Description, and CreatedDateTime respectively. Resolution notes map to the case's internal notes field. Priority maps to CaseClassID and Severity field in Acumatica's case management.

Dolibarr interventions map to FSServiceOrder in Acumatica's Field Service module (if licensed). The intervention date, duration, description, and linked third-party and contact transfer to service order fields. Billable flag maps to Billable and CuryUnitPrice; non-billable interventions carry zero price. Without the Field Service license, interventions migrate as Case records with a custom intervention flag.

Dolibarr users map to Acumatica Employee records with the same login email. The employee record is created first, then the Acumatica user account is linked with the EmployeeID. Active/inactive status maps from Dolibarr's user active flag. Branch assignments in Acumatica require HR structure setup before users can be assigned to locations.

Dolibarr product and third-party categories map to Acumatica's Category entity linked by entity class. Multi-level Dolibarr categories (parent/child) preserve the hierarchy in Acumatica's CategoryTree structure. Contact categories transfer as Tags on the CustomerContact record for filtering in CRM screens. The CategoryTree ensures parent-child relationships display correctly in Acumatica's reporting and filtering interfaces.