Migrate from Dolibarr ERP to Infor CloudSuite Corporate

Dolibarr stores contacts, companies, and suppliers in the same llx_societe (third party) and llx_socpeople (contact) tables with a typent_code field distinguishing customer, supplier, and prospect. We map typent_code to Infor's Business Partner Role (Customer, Supplier, or Prospect). Country, address, phone, email, and VAT number fields map directly. If the Infor destination is CloudSuite Distribution (SX.e) or M3, the Business Partner model uses different party-role tables; we configure the role assignment during schema discovery.

Dolibarr's llx_product table with type=0 for products and type=1 for services maps to Infor Item with Item Type distinguishing stocked product from non-stocked service. Pricing fields (price buy, price sell, VAT rate) migrate; stock levels in llx_product_stock map to Infor warehouse inventory quantities. Warehouse locations (llx_entrepot) become Infor Warehouse codes. SKUs migrate as Item Code; we flag any duplicate codes during pre-migration validation.

Dolibarr proposals map to Infor Quotation with status lifecycle mapping: draft (0), open (1,2), signed (4), refused (3). Proposal lines reference product IDs that we either resolve to Infor Item codes (if products migrated in the same job) or hold as pending references. Line quantity, unit price, discount, and VAT migrate directly. Expiry dates map to Infor Quotation expiration date fields.

Dolibarr customer orders map to Infor Sales Order. Order status codes (0=draft, 1=validated, 2=shipped, 3=delivered, 4=canceled) map to Infor Order Status values. Order lines with product references, quantities, and pricing migrate. Dolibarr's source/third-party order references become Infor Customer PO Number. If the destination is Infor LN (Baan-based), sales orders use a different document type structure; we configure the mapping during discovery.

Dolibarr invoices (llx_facture) include complex relationships: invoice lines, payments (llx_paiement), payment-to-invoice links (llx_paiement_facture), and bank transaction references (llx_bank). We preserve all relationships, including partial payment status. We record the source system's decimal precision settings (Setup > Limits and accuracy) and apply matching field-level formatting at Infor. Multi-currency invoices store currency code and exchange rate; we migrate these to Infor's multi-currency ledger configuration if enabled.

Dolibarr projects map to Infor Project with project type, dates, budget, and status. Tasks (llx_projet_task) with assignees and time budgets migrate as WBS elements. If the destination is Infor CloudSuite Industrial with Project Management module, tasks map to work order WBS; for CloudSuite Distribution, they map to Project Accounting structures. We resolve user assignees to Infor Business User references during migration.

Calendar events from llx_actioncomm export with date, owner, linked third parties, and linked projects. Recurring event rules and third-party associations are preserved. Infor Calendar stores events under Infor OS or the industry-specific calendar module. fullcal integration metadata from Dolibarr's web interface is not migratable. We map event type codes to Infor Activity Category values.

Dolibarr bank accounts (llx_bank) migrate with reconciliation state preserved as reference fields. Payment records linked to invoices via llx_paiement_facture carry forward the payment-to-invoice linkage so that Infor's accounts receivable can reconcile open items. If Infor's General Ledger is enabled, bank transactions map to GL journal entries with bank account as the source account.

Dolibarr user accounts (llx_user) migrate as Infor Business Users with login, name, email, and active status. Password hashes (salted bcrypt) are not migratable; users reset passwords at Infor. Permission profiles (llx_rights_def) do not map directly to Infor's role-based security model; we deliver a written role mapping inventory for the customer's admin to configure Infor security roles post-migration.

Dolibarr's extrafields system serializes custom field definitions and values as JSON inside an extraoptions column on the parent table. We parse each object's extraoptions JSON at migration time, flatten the key-value pairs, and write them as Infor-native custom properties. Field-type mismatches (e.g., file paths stored as text, date formats, multi-select values) are flagged during discovery. We pre-create the Infor extended property schema before data import so that all custom fields exist at destination before any parent records load.

Stock movement history in llx_stock_mouvement migrates alongside product and warehouse records. Movement type (entry/exit), quantity, date, and warehouse mapping preserve the audit trail. We run a separate export profile for movement history after the base stock levels are validated at destination, ensuring that opening balances match before movement history applies.

HR modules including leave requests (llx_holiday) and expense reports (llx_deplacement) migrate with effective-dated rows and approval status flags if Infor CloudSuite HCM or a compatible HCM module is in the destination scope. If no HCM is deployed, these records are excluded from the ERP migration scope and noted in the handoff inventory. Infor's HCM data model differs significantly from Dolibarr's flat HR module; a separate HR migration engagement is recommended if HCM is required.