Migrate from Kafinea to Odoo ERP

Kafinea Customers export as Contact records in Odoo with the company_name field populated from Kafinea's Company object. We preserve addresses, payment terms, and the customer/supplier flag. Kafinea's separate Contact and Company objects map to a single res.partner record with is_company=True for companies and is_company=False for individual contacts, merging the two-source relationships into Odoo's unified partner model.

We export Kafinea's full account list with account codes, types (asset, liability, equity, income, expense), currency, and cost center flags. Accounts are imported into Odoo's French accounting localization chart (Plan Comptable Général), and non-standard or custom account codes are flagged for the customer's accountant to assign the correct Odoo account type before journal entry migration begins. Multi-currency accounts are flagged with the corresponding currency_id on the res.partner and account.account records.

Kafinea Classic, Progress, and Recurring invoices map to Odoo account.move records with move_type out_invoice and out_refund. Invoice lines map to account.move.line with the account_id resolved from the Chart of Accounts mapping. Payment state reconciles to Odoo's reconciliation model using the payment reference. VAT treatment is flagged per line where Kafinea's tax code does not map directly to an Odoo tax template; the customer's accountant assigns Odoo tax IDs during configuration.

Real-time accounting journal entries from Kafinea export with multi-line debits and credits sequenced by posting date. We import them as Odoo account.move records with move_type entry, preserving the journal reference, date, line descriptions, and account mapping. Entries are imported in strict date order to maintain the accounting ledger sequence. Entries without a mapped account code are held in a reconciliation queue.

Kafinea Sales Orders map to Odoo sale.order with sale.order.line for line items. Pricing rules from Kafinea Price Books are translated to Odoo pricelist rules applied on the sale.order record. The partner_id on sale.order is resolved from the res.partner mapping created during the Customer phase. Product references are resolved to product.product records using the Kafinea SKU as the default_code.

Kafinea tiered Price Books (quantity-based pricing tiers) are configured as Odoo product.pricelist records with product.pricelist.item entries for each quantity break. The mapping preserves the break point, discount percentage, or fixed price per tier. We create one pricelist per Kafinea Price Book and assign it to the corresponding customer records or the sale.order during import.

Kafinea Service Contracts define recurring billing cycles and SLA terms; they map to Odoo's Maintenance module contract records if the Field Service app is installed, or to project.task records with a contract-type tag if the project-only configuration is chosen. Recurring billing lines are flagged for the customer to configure the Odoo recurring invoicing schedule post-migration. SLA duration and response time fields map to maintenance.contract custom fields.

Kafinea Interventions (time or task records logged against Service Contracts) map to Odoo maintenance.wo (work orders) if Field Service is installed, or to project.task records if the simpler project-only setup is used. We resolve the parent contract reference from the maintenance.contract mapping and preserve the intervention date, duration, assigned technician (mapped to res.user), and description. Billable flag and rate mapping are preserved for invoicing setup post-migration.

Kafinea timesheet entries map to Odoo account.analytic.line records linked to projects or standalone analytic accounts. Effective-dated absence records require the Odoo HR app; they map to hr.leave with the leave type resolved from Kafinea's absence category and accrual balances computed sequentially at import time. The employee_id is resolved from the res.partner mapped to a res.users record with hr.employee linkage.

Kafinea custom fields across Customers, Invoices, Sales Orders, and Service Contracts are created in Odoo as ir.model.fields before data import begins. We handle picklist values as ir.model.fields.selection entries, date fields as date or datetime types, and numeric fields with explicit decimal precision. Custom objects from Kafinea are replicated as Odoo models with their own menu and form structure, which requires custom module development outside standard migration scope; we scope the development requirement and the customer implements it or engages an Odoo partner.