Migrate from BusinessCloud to Dolibarr ERP

BusinessCloud Contact and Company records map to Dolibarr's llx_societe table as ThirdParty records. We determine customer versus supplier status using BusinessCloud's account type property. If BusinessCloud separates contacts from companies, we import the parent Company first (satisfying the fk_societe_perm reference for contacts), then import contacts with fk_societe_perm pointing to the parent ThirdParty. Email, phone, address, and website fields map directly. Any BusinessCloud custom fields on contact or company records become Dolibarr Extrafields entries on llx_societe.

BusinessCloud product and service records map to Dolibarr's llx_product table. The product_type field distinguishes inventory-tracked goods (type 0) from services (type 1). The ref field carries the BusinessCloud product code or SKU; label maps to product label. If BusinessCloud tracks cost price, recommended price, or barcode, these map to buy_price, price_ttc, and barcode fields respectively. Stock quantities map to pmp (average purchase price) and stock_reel if the Dolibarr Stock module is active.

BusinessCloud project records map to Dolibarr's llx_projet table. Project name, description, start date, and end date transfer directly. If BusinessCloud tracks project status as a custom field, we map it to the fk_statut field in Dolibarr. Project budgets and cost tracking fields map to budget and budget_ht if those Dolibarr fields are available; otherwise they are flagged as Extrafields candidates for the customer's admin to configure post-migration.

If BusinessCloud manufacturing or production modules include BOM data, these map to Dolibarr's llx_bom and llx_bomline tables, which require the BOM module to be enabled in the destination Dolibarr instance. We create the BOM record first, then populate llx_bomline with component products, quantities, and unit-of-measure references. This mapping only applies when the Manufacturing module is active on both source and destination; BOM is not in Dolibarr's core and must be installed as a separate module.

BusinessCloud sales orders and purchase orders map to Dolibarr's llx_commande table with the sourcetype field set to Kund (customer order) or Supplier (supplier order). Order date, reference number, status, and total amounts transfer directly. Line items map to llx_commandedet with fk_product resolved against the Product mapping. Any BusinessCloud custom fields on order headers become Extrafields on llx_commandedet.

BusinessCloud invoices map to Dolibarr's llx_facture table with type区分 customer invoice (type 0), replacement invoice (type 2), or credit note (type 3). The invoice reference, date, due date, and status transfer directly. Line items map to llx_facturedet with fk_product resolved. Payments recorded in BusinessCloud map to llx_paiement and llx_paiement_facture, linking the invoice to the payment record. PDF attachments from BusinessCloud migrate as ContentDocument files attached via llx_document_model.

BusinessCloud recurring contracts or subscription records map to Dolibarr's llx_contrat table. Contract start date, end date, and status transfer directly. If BusinessCloud tracks contract line items (services included per period), these map to llx_contratdet with service start and end dates per line. The fk_contrat links to llx_contrat and fk_product links to the mapped Product record.

BusinessCloud bank account or financial account records map to Dolibarr's llx_bank table. Account number, bank name, and IBAN transfer to label, numero, and iban fields respectively. Any current balance recorded at time of export maps to solde. The Dolibarr Bank module must be enabled for this object to import.

BusinessCloud categories or tags attached to products, third parties, or projects map to Dolibarr's llx_categories table. We import the category label and type (0 for products, 1 for contacts, 2 for customers, 3 for suppliers, 11 for projects). Category assignments from BusinessCloud become records in llx_categorie_entity with the appropriate fk_categorie and fk_object references for the tagged entity.

BusinessCloud payment records map to Dolibarr's llx_paiement table with payment type, date, and amount. The corresponding llx_paiement_facture record links the payment to the migrated invoice by matching the BusinessCloud invoice reference to the Dolibarr facnumber. If BusinessCloud tracks partial payments, each partial payment becomes a separate llx_paiement record with a corresponding llx_paiement_facture row.

BusinessCloud user and employee records map to Dolibarr's llx_user table. We match by email address as the dedupe key. Active status, login, and lastname transfer directly. Dolibarr stores passwords as hashed values and does not accept plaintext password imports, so the customer's admin must reset passwords or send account-setup emails post-migration. Owner assignments on migrated records reference llx_user rowid values resolved after the User table is populated.

Any custom objects or custom fields present in BusinessCloud that do not map to a standard Dolibarr table become Dolibarr Extrafields entries. We create the Extrafield definition in Dolibarr's llx_extrafields with the correct fk_object (pointing to the target table like llx_societe, llx_product, or llx_projet), field label, and data type. The custom field values migrate as Extrafield data in the target table. This step requires the customer's admin to define the field semantics and any associated picklists or validation rules in Dolibarr before migration.