Migrate from Kafinea to Dolibarr ERP

Kafinea Customers map to Dolibarr ThirdParty (llx_societe) records. The primary contact details, billing address, and payment terms transfer as the ThirdParty header; additional contact persons map to Dolibarr contact sub-records (llx_socpeople) linked via fk_soc. Customer category assignments (prospect, customer, supplier) map to Dolibarr's标签 system. We resolve the ThirdParty ID before any dependent object import to satisfy the foreign key constraint.

Kafinea CRM Contacts (separate from Companies in Kafinea's schema) map to Dolibarr Contact sub-records. Kafinea's lifecycle stage and custom contact properties map to Dolibarr extrafields. If the customer used Kafinea's Contact-Company link extensively, we resolve the link into Dolibarr's fk_soc reference on each contact. Contacts without a parent ThirdParty are held in a reconciliation queue for the customer to assign a company before import.

Kafinea Companies map directly to Dolibarr ThirdParty records, with the domain stored in the website field as a reference. If both Company and Customer records exist for the same entity in Kafinea (which is common), we merge them into a single Dolibarr ThirdParty with the customer flag set. Supplier-flagged Companies map to Dolibarr ThirdParty with the supplier status enabled.

Kafinea invoices map to Dolibarr Invoice (llx_facture) records. Invoice type (classic, replacement, credit note) maps from Kafinea's type field. Payment status and the invoice-to-payment link transfer as Dolibarr payment records (llx_paiement_facture) linked to the invoice. VAT treatment that differs between systems is flagged for manual confirmation before the invoice is set to validated status in Dolibarr. Recurring invoices are migrated as template invoices with their frequency metadata preserved in extrafields.

Kafinea credit notes map to Dolibarr Invoice records with type = Credit Note (Avoir). The link back to the original invoice is preserved as a Dolibarr fk_facture_source reference where available. If Kafinea does not expose this link in its export, we capture it in a companion mapping file and advise the customer to link manually post-import.

Kafinea journal entries with multi-line debits and credits map to Dolibarr accounting entries (llx_ecm_files and llx_accounting_bookkeeping). Entries are sequenced by posting date to preserve the chronological ledger order. Each line's account code is mapped to the corresponding Dolibarr chart of accounts code. If Kafinea account codes use a non-standard numbering scheme, we flag these for the customer to align with their chosen Dolibarr chart of accounts template before import.

Kafinea chart of accounts records map to Dolibarr accounting account codes. We require the customer to confirm their chosen Dolibarr chart of accounts template (France PCG, Belgium PCMN, or custom) before mapping. Account type (asset, liability, equity, income, expense), currency, and cost center assignment transfer as account properties. Non-standard or custom account codes that do not map to the chosen template are flagged with the customer and can be added to the template before import.

Kafinea Sales Orders map to Dolibarr Customer Order records. Line items with product references and pricing rules transfer to Dolibarr commandelines. Order status (draft, validated, shipped, closed) maps to Dolibarr order status. Kafinea's tiered price book rules applied at order time are resolved as static prices in the order line rather than as dynamic rule references, because Dolibarr's price application is resolved at order creation.

Kafinea tiered quantity-based pricing tiers map to Dolibarr product price entries per customer or customer category. Each quantity break from Kafinea creates a corresponding Dolibarr price level entry. If Kafinea's price book applies customer-specific overrides, these map to Dolibarr customer-specific price entries. We require the customer to confirm the target Dolibarr price type (selling price, minimum price, wholesale price) before mapping.

Kafinea Service Contracts define recurring billing terms and SLA levels that map to Dolibarr Contract records. The contract start date, duration, renewal terms, and linked service items transfer. SLA terms that Kafinea stores as custom properties map to Dolibarr extrafields since Dolibarr's base contract object does not have a native SLA field.

Kafinea Interventions (time or task records logged against service contracts) map to Dolibarr Intervention records linked to the corresponding Contract. Duration, description, and the user who logged the intervention transfer. If the destination Dolibarr instance does not have the Interventions module activated, we flag this before migration and advise on module activation, as interventions without the module appear as generic project tasks.

Kafinea Timesheets map to Dolibarr Project records with individual time entries as Project Tasks (llx_projet_task). Effective-dated absence records require sequential import to preserve accrual balance calculations. If Kafinea timesheets are linked to specific projects or contracts, we resolve the Dolibarr project reference at migration time before inserting the task records.

Kafinea custom fields across all objects map to Dolibarr extrafields (llx_extrafields). We handle type casting: picklist values from Kafinea map to Dolibarr select extrafields; date fields map to Dolibarr date extrafields; numeric fields map to Dolibarr double or integer extrafields. Multi-select picklists map to Dolibarr's checkbox extrafield type. Before migration, we pre-create every extrafield definition in Dolibarr so that incoming records are validated against the target schema.

Kafinea EDM documents export as file references or direct downloads. We preserve the folder structure and attach documents to the corresponding Dolibarr records using Dolibarr's document management system. Files without a clear parent record are collected into a migration-attachments folder for manual categorization post-import. Document size and format compatibility are validated before upload.