Migrate from Kentro ERP & 3PL to Dolibarr ERP

Kentro Products with variants, SKU-level tracking, and pricing tiers migrate to Dolibarr Products. HubSpot SKU (hs_sku) becomes Dolibarr's ref (reference code). Variant relationships in Kentro map to Dolibarr's product combination system if the Combinations module is enabled. We preserve product categories, description, and pricing rules. Any attribute sets in Kentro map to Dolibarr extra fields or the Categories module.

Kentro's real-time inventory positions across multiple warehouse locations map to Dolibarr's multi-warehouse stock module. We transfer current stock snapshots per location plus any available movement history as Dolibarr Stock Movement records. FIFO/FEFO tracking logic in Kentro is noted as a configuration preference; Dolibarr does not enforce a specific costing method natively, so we document the original costing method and recommend a community module or custom configuration for FIFO tracking if required post-migration.

Kentro Orders across their full lifecycle (from channel receipt through fulfillment and returns) map to Dolibarr Customer Order. The originating sales channel linkage is preserved as an Order reference or extra field so that historical orders retain their source. Return and refund records link back to the original order. Order status transitions in Kentro map to Dolibarr Order status values; any custom status workflows are flagged for manual configuration in Dolibarr's order status module.

Kentro's distinct B2C customer and B2B company account records map to Dolibarr's Third Party (societe) as companies and to Contact records as individuals linked to those third parties. Address associations and account-level pricing terms migrate as Third Party extra fields. The customer type flag (B2C/B2B) in Kentro sets the Third Party type in Dolibarr (Customer or Prospect and Customer).

Kentro Supplier records with contact details, lead times, and default purchase terms map directly to Dolibarr Third Party records with type set to Supplier. Purchase contact information migrates as Dolibarr Contacts linked to the supplier Third Party.

Kentro supplier-facing purchase orders and receiving records map to Dolibarr Supplier Order (Commande Fournisseur). Standard PO fields (supplier reference, line items, quantities, expected dates) migrate directly. Any custom approval chains in Kentro are flagged as workflow items requiring rebuild in Dolibarr, as Dolibarr's approval workflow for supplier orders is module-dependent and community-assisted rather than a native enterprise-grade engine.

Kentro marketplace connections and online store configurations are preserved as Order reference data or extra fields on Dolibarr orders rather than as native channel objects. The channel-to-order linkage is critical for reporting; we create a Dolibarr dictionary entry for each Kentro channel so that historical orders can be filtered by originating source post-migration.

Kentro's multi-client 3PL architecture with separate inventory pools, billing records, and seller portals per client requires careful isolation. We extract each client's records as a separate export batch and map them into Dolibarr as individual Third Parties with type Customer or Prospect. If the customer operates separate legal entities, we recommend distinct Dolibarr instances or the Multi-Company module to maintain data isolation. Billing records and client-specific inventory are noted as requiring post-migration configuration in Dolibarr.

Kentro inter-warehouse transfer orders and their completion records map to Dolibarr Stock Movement records linked between source and destination warehouses. Transfer status at migration time is recorded; any in-transit transfers are flagged as open movements requiring resolution before the destination inventory is treated as authoritative.

Kentro fulfillment events and carrier tracking data linked to orders migrate as shipping method and tracking number fields on Dolibarr Orders. Carrier-specific metadata (e.g., exact shipping service level codes) may require supplementary export from Kentro as Dolibarr extra fields; Dolibarr does not have a native comprehensive carrier integration layer beyond basic shipping method labels.

Kentro EDI compliance documents (ASN feeds, retailer-specific order mappings, EDI invoices) have no native equivalent in Dolibarr's schema. We export these as flat-file snapshots (CSV, XML, or EDI format depending on the retailer's transaction set) alongside structured order data so the customer's team can feed them into a dedicated EDI compliance tool post-migration. EDI document snapshots are not imported into Dolibarr's native document management as flat files lack the structured field mapping Dolibarr expects.

Kentro IQ analytics reports and their underlying datasets are exported as data extracts where accessible via API. The report definitions themselves (visualizations, filters, scheduling) do not migrate as executable objects in Dolibarr. We deliver a written inventory of every Kentro IQ report with its data sources, metrics, and filters so that the customer's team or a Dolibarr consultant can rebuild equivalent reports using Dolibarr's built-in reporting module or a third-party BI connector.

Documents attached to orders, products, or customers in Kentro migrate as Dolibarr Files linked to the corresponding record via the document management module. We preserve attachment URLs and re-link them post-migration where Dolibarr's document storage (home dolibarr_main_data_root) supports the same file types. Large document archives may require separate bulk transfer via SFTP or direct file copy rather than API-based migration.