Migrate from daftra to Dolibarr ERP

Daftra Client records map to Dolibarr ThirdParty (societe) with the individual/company flag set from Daftra's client type. Contact records attached to a Daftra Client migrate to Dolibarr Contact records linked via fk_soc. Membership points, insurance records, and sales commission references from Daftra store as custom fields on the Dolibarr ThirdParty. Client follow-up activity logs migrate as Note records linked to the ThirdParty.

Daftra Products and Services map to Dolibarr Product with the type field set to product or service. SKU, pricing tiers, stock levels, and supplier links transfer directly. Custom fields on Daftra products (user-defined per the field builder) require enumeration during discovery and map to Dolibarr extrafields.

Daftra Invoices map to Dolibarr Facture. Line items map to FactureLigne with product reference, quantity, and UnitPrice. Taxes, installment schedules, and sales commission assignments on the Daftra invoice transfer as invoice-level custom fields. The invoice balance and payment status reconstruct from Daftra's installment tracking and payment history. Custom fields on Daftra invoices (per-object field builder) are enumerated during discovery and mapped to Dolibarr extrafields on Facture.

Daftra Expenses map to Dolibarr ExpenseReport when the HRM module is active. Expense category, amount, date, and attachment references transfer. Recurring expense patterns from Daftra store as a flag on the expense record for admin to reconfigure in Dolibarr. Daftra Expense records are linked against the Chart of Accounts during migration so that the account code references are valid at Dolibarr import time.

Daftra's flat Chart of Accounts export requires recursive tree reconstruction during discovery to establish parent-child hierarchy. We load accounts in Daftra account code order to respect posting sequence, then configure Dolibarr's Accounting module (plan comptable) accordingly. Sub-account parent references reconstruct from Daftra's account code prefixes. Each account type (asset, liability, revenue, expense) maps to the corresponding Dolibarr compte type in the accounting module. This is a prerequisite phase — no transactional records load until the chart of accounts is validated.

Daftra Cost Centers (used for expense attribution across departments or projects) have no direct Dolibarr equivalent. We recommend mapping Cost Centers to Dolibarr Projects when the Project module is active, or to Product categories for expense reporting. The linking between Cost Centers and individual Daftra transactions requires field-level extraction and a join during the transform phase. We document the Cost Center logic and configure the chosen Dolibarr equivalent before migration.

Daftra Employee records include organizational structure placement, contracts, attendance, and payroll time-series. We extract each payroll period as a separate record and map Employees to Dolibarr User accounts (for system access) plus HRM module records for contract and payroll data. Daftra's compensation history (time-series) stores as Note records or custom fields on the Dolibarr User for audit trail. Attendance records migrate as Note entries on the User or, if the HRM module attendance sub-module is active, to attendance records.

Daftra Fixed Assets map to Dolibarr Asset (Immobilization module). Asset depreciation schedules are extracted separately from the asset master record and configured as depreciation entries in Dolibarr. Custom fields on Daftra assets (added per-asset via the field builder) require enumeration during discovery and map to Dolibarr extrafields on the Asset object. Asset custom fields are a known gap if not enumerated before migration — values are silently dropped without a pre-migration field audit.

Daftra Work Orders link Clients, Employees, and Products and carry a full workflow stage history. Each Work Order maps to a Dolibarr Project, with the stage history preserved as Note records. Line items and employee assignments map to Dolibarr Task records attached to the Project. Any attached files or notes migrate as ContentDocument records linked to the Project via ContentDocumentLink.

Daftra Reservation Files (PNR-style booking management with status tracking and appointment scheduling) have no native Dolibarr equivalent. We recommend mapping Reservations to Dolibarr Projects with status fields and appointment scheduling implemented via the Project's task calendar. Alternatively, if the customer licenses a third-party Dolibarr booking module from the Dolibarr marketplace, we configure and map accordingly. We flag this as a configuration decision to make during scoping and document the chosen approach before migration.

Daftra's cheque cycle (issue, deposit, return stages) tied to the Chart of Accounts has no direct Dolibarr equivalent. We recommend mapping cheque records to Dolibarr Bank Account entries (Comptes bancaires) with payment type set to cheque, and the stage transitions recorded as Note entries on the bank account record. The reconciliation between cheque cycle stages and Dolibarr payment statuses requires a custom configuration documented during scoping.

Daftra supports custom fields independently on Invoices, Assets, and Workflows. There is no single schema export for all custom fields. We enumerate each object's custom field definitions via Daftra's UI during discovery, reading field type, required flag, and options list. We then configure corresponding Dolibarr extrafields before migration and map values during the data phase. Skipping enumeration results in custom field values being silently dropped — this is one of the highest-risk migration gaps for Daftra customers with heavily customized installations.