Migrate from Deskera ERP to Dolibarr ERP

Deskera's COA with account codes, names, and standard types (Asset, Liability, Equity, Revenue, Expense) maps directly to Dolibarr's accounting module Chart of Accounts. Deskera's Class/Location/Department dimensions migrate to Dolibarr's analytical accounting (comptabilite analytique) via the extras module if activated; otherwise we flatten dimensions into account sub-names and flag for post-migration configuration. Multi-currency account settings map to Dolibarr's currency-per-account configuration.

Deskera Customer records (via /v1/account with type filter) map to Dolibarr Third Parties with the Customer check box enabled. Billing address, shipping address, phone, email, tax ID, payment terms, and credit limit migrate directly. We separate Customers from Vendors during extraction and set the correct Third Party type flag during Dolibarr import to avoid needing post-migration type corrections.

Deskera Vendor records map to Dolibarr Third Parties with the Supplier check box enabled. Supplier-specific fields (bank details, default payment terms for purchases, default warehouse receipt location) migrate to Dolibarr's Supplier tab on the Third Party. We run the Customer and Vendor extracts as separate passes and validate zero cross-contamination before loading into Dolibarr.

Historical journal entries from Deskera (account reference, debit/credit amount, date, narration, optional dimension tags) map to Dolibarr Accounting Entry records. We transform Deskera's debit/credit journal line format into Dolibarr's expected row format with debits as positive and credits as negative. Given Deskera's undocumented API rate limits, we batch journal exports in chunks of 500 entries and throttle at 10 requests per second, monitoring for 429 responses before resuming.

Deskera items (SKU, name, description, unit of measure, cost price, sell price, on-hand quantity) map to Dolibarr Products. Deskera's batch/lot and serial tracking maps to Dolibarr's lot/serial number fields if the Stock module is activated. Warehouse quantities migrate to Dolibarr's stock by warehouse entries, linking each item to the correct warehouse record. Deskera's product type (goods vs service) maps to Dolibarr's Product vs Service classification.

Deskera multi-level BOMs (parent assembly with component items and quantities per level) require flat-mapping into Dolibarr's BOM module, which supports single-level BOM structures. We extract the full BOM hierarchy from Deskera MRP and create a flat list of parent-to-component associations with quantities, then load each as a Dolibarr BOM line against the parent product. Multi-level routing logic (sequence of operations, work centers, cycle times) has no Dolibarr equivalent and is flagged in the migration inventory for manual rebuild in Dolibarr's production planning module if the customer activates it.

Open Deskera Sales Orders map to Dolibarr Customer Orders linked to the Third Party (customer) and line items resolved to Products. Order date, delivery address, payment terms, and line-item pricing (including discount percentages) migrate. Closed historical orders may be migrated selectively based on the customer's accounting cutoff requirements; we scope the date window during discovery.

Open Deskera Purchase Orders map to Dolibarr Supplier Orders linked to the Third Party (vendor). Expected receipt dates and line-item quantities migrate. We resolve the supplier Third Party before importing orders to satisfy Dolibarr's foreign key requirement. Closed historical POs follow the same selective date-window scoping as Sales Orders.

Deskera People employee records (name, job title, department, hire date, salary, leave balances) map to Dolibarr'shrm_employee table if the HR module is activated. Compensation effective-dated history requires additional mapping to Dolibarr's salary/contract structure. We migrate core employee fields and flag that detailed payroll history mapping is a separate scope requiring the HR module's salary configuration to be set up first.

Deskera CRM Contacts linked to accounts map to Dolibarr Contacts linked to the corresponding Third Party. Contact-specific fields (phone, email, role, tags) migrate directly. Custom contact lifecycle stages from Deskera migrate as custom extra fields on Dolibarr Contacts since Dolibarr's standard lifecycle model is simpler.

Deskera custom field definitions and their values per record require pre-creation of matching Dolibarr extra fields before data import. We export the custom field schema from Deskera, map Deskera field types (text, number, date, select, multi-select) to Dolibarr's extra field types, and create the destination extra field definitions in Dolibarr before importing the corresponding values. This step runs before any object data import to ensure the target fields exist.

Deskera Owner records (x-access-token user context) map to Dolibarr User accounts. We resolve Deskera owners by email match and create Dolibarr users with the matching email address. Any Deskera owner without a matching Dolibarr user is held in a reconciliation queue for the customer's admin to provision before record import continues, since Dolibarr requires a valid user reference for created-by and assigned-to fields.