Migrate from daftra to Odoo ERP

Daftra Client records map to Odoo res.partner with partner_type set to 'contact' for individuals and 'company' for corporate clients. Client follow-up activity logs migrate as Odoo mail.message records linked to the Partner for activity timeline preservation. Membership points, insurance references, and sales commission data transfer to custom fields on res.partner (membership_points__c, insurance_ref__c, commission_group__c). We deduplicate by client email during import. Arabic character normalization to UTF-8 applies to all name and address fields.

Daftra product catalog maps to Odoo product.product records. Product type (goods vs service) maps to Odoo's type field (product vs service). SKU, stock levels, and pricing tiers migrate to product_code, qty_on_hand, and pricelist entries respectively. Supplier links from Daftra map to Odoo seller_ids on the product record. Custom fields on products are enumerated during discovery and created in Odoo via Studio or direct ir.model.fields before import.

Daftra sales invoices map to Odoo account.move with move_type='out_invoice'. Each invoice line maps to Odoo account.move.line with matched product references via product_id. Installment schedules from Daftra become Odoo payment terms (account.payment.term) applied to the invoice. Sales commission assignments on invoices map to custom fields on account.move.line. Custom invoice fields enumerated during discovery create Odoo custom fields before import. Invoice balance and payment status migrate as move_state and amount_residual.

Daftra expense records map to Odoo vendor bills (account.move with move_type='in_invoice'). Amount, category, and date migrate directly. Attachment references from Daftra map to Odoo ir.attachment records linked to the account.move. Recurring expense patterns from Daftra transfer as a flag on the Odoo expense record (is_recurring__c) so the customer's admin can rebuild recurrence in Odoo if needed. Expense-to-Chart of Accounts mapping resolves during the account load phase.

Daftra's Chart of Accounts migrates to Odoo account.account records in account code order to preserve posting sequence. Daftra's flat UI export requires us to build a recursive account tree during discovery by parsing account codes for parent-child relationships. Account type mapping (asset, liability, revenue, expense) maps to Odoo's accountType field. This object loads first, before any transactional records, so that all Expense, Invoice, and Cheque records have valid account references at import time.

Daftra Cost Centers map to Odoo analytic accounts used for expense attribution across departments or projects. Daftra's export links Cost Centers to individual transactions via a separate field extraction query, not the main expense export. We build a mapping table during discovery linking each Daftra cost_center_id to an Odoo analytic account, then apply this during transaction import. If the destination Odoo instance does not activate the Accounting analytic features, Cost Centers transfer as tags on the account.move.line for post-migration activation.

Daftra Employee records map to Odoo hr.employee with org chart placement via parent_id. Contracts migrate as hr.contract records linked to the employee. Attendance and payroll history from Daftra requires time-series extraction per employee; payroll compensation history maps to hr.contract wage and related fields. Daftra's organizational structure (departments, reporting lines) transfers to hr.department records and parent-child relationships on hr.employee. If the destination Odoo instance does not activate the Payroll app, salary history maps to custom fields on hr.contract for admin reference.

Daftra fixed asset records map to Odoo account.asset with custom fields from Daftra enumerated during discovery and pre-created in Odoo via Studio. Asset depreciation schedules require separate extraction from the Daftra asset master record and map to Odoo's depreciation lines (account.asset.depreciation.line). Depreciation method (straight-line, declining balance) maps from Daftra's depreciation configuration. Asset category in Daftra maps to account.asset.category for shared depreciation rules.

Daftra Work Orders link Clients, Employees, and Products. For manufacturing-oriented work orders, we map to Odoo mrp.production with bom_id and workcenter routing. For service-oriented work orders, we map to project.project with task breakdown. Workflow stage history migrates as project.task records with status sequencing. Attached files and notes migrate as ir.attachment and mail.message records linked to the project or manufacturing order.

Daftra Booking files (PNR-style reservations) migrate as Odoo calendar.event records for appointment scheduling, linked to the res.partner booking the reservation. Reservation file status tracking becomes project.task records with stage sequencing. Activity logs from the booking file migrate as mail.message records on the calendar.event for full timeline preservation. If the destination Odoo instance uses the Helpdesk or Field Service app, booking records can alternatively map to ticket records with custom status stages.

Daftra's Cheque Cycle tracks cheques through issue, deposit, and return stages tied to both the Chart of Accounts and specific invoice/payment records. We split this into Odoo account.payment records (for the instrument and bank account) and account.move records (for the accounting entries at each stage: issue, deposit, return). Cheque status in Daftra maps to payment.state in Odoo. Full cycle history links to the related invoice account.move via reconciliation records.

Daftra supports custom fields independently on Invoices, Assets, and Workflows with no single schema export. We enumerate each object's custom field definitions via the Daftra UI during discovery, reading field type, required flag, and options list for picklist fields. We then pre-create equivalent fields in Odoo via Studio or direct ir.model.fields insertion before any data import. Skipping this step silently drops custom field values during migration.