Migrate from Sage 100cloud to Dolibarr ERP

Sage 100cloud stores the chart of accounts as a flat list of account codes with optional Type, Division, and Department segments in the GL_Account master table. Dolibarr uses a plan comptable with up to 8 segment positions (configurable under Home > Setup > Chart of Accounts). We parse the Sage account code structure, split segments based on the customer's account mask (e.g., 4-2-2-4), and write each segment into the corresponding Dolibarr account_code_devise and account_parent fields. Account type (A for Asset, L for Liability, R for Revenue, E for Expense) maps directly to Dolibarr's account_type field. Account descriptions and active/inactive status migrate as-is.

Sage AR_Customer records include billing/shipping addresses, payment terms, credit limits, salesperson assignments, and 1099 settings. We map these to Dolibarr's societe table with a thirdparty_type of 'Customer' and populate address fields via the societe_address table. Payment terms reference the Sage terms_code mapped to Dolibarr's condicionesreglement table. Credit limit and salesperson assignment become custom extrafields or native Dolibarr fields depending on whether the customer enables the corresponding module. Email, phone, and website from Sage map to Dolibarr's phone, fax, mail, and url fields.

Sage AP_Vendor records mirror the customer schema with the addition of 1099 settings and W-9 status flags. We map to Dolibarr's societe table with thirdparty_type = 'Supplier'. The 1099 flag from Sage maps to a Dolibarr extrafield since standard Dolibarr does not include 1099-specific fields. Vendor address and payment terms migrate identically to the customer path. We flag any vendor with an outstanding W-9 status of Pending or Expired in a sidecar CSV for the customer's admin to resolve in Dolibarr's document management module.

Sage IC_Item stores SKU, description, unit of measure, cost method (FIFO, Average, Standard), minimum stock levels, and warehouse/bin assignments. Multi-warehouse and multi-bin records in IC_BinDetail map to Dolibarr's stock warehouses and product_stock tables. Lot/serial tracking data from IC_Lot and IC_Serial map to Dolibarr's batch_number and serie_number fields if the Lot/Serial module is enabled. Bill of Materials from IC_BOM and IC_BOMDetail migrate as Dolibarr product-bom entries with the Manufacturing / MPR module. We preserve the Sage cost_method as a Dolibarr extrafield since Dolibarr's default costing is average cost.

Open accounts receivable are exported as Dolibarr Facture records with type = 'Invoice' and status = 'Unpaid'. Sage invoice header fields (invoice number, invoice date, due date, amount, balance) map directly. Invoice line items map to Dolibarr's facturedet table with product reference, description, quantity, unit price, and VAT code resolved from the Sage tax table. Sage invoice-level discounts and freight charges become separate Dolibarr invoice line entries. We preserve the original Sage invoice number in Dolibarr's ref_supplier field for audit traceability. Invoices with a status of Paid are migrated as Facture with status = 'Paid' and payment date set from AR_Payment.

Open accounts payable records from Sage AP_Invoice and AP_Payment tables migrate as Dolibarr Facture (type = 'SupplierInvoice') linked to the vendor Third Party record. Invoice date, due date, vendor invoice number, and amount remaining map to the corresponding Dolibarr fields. We also export Sage payment records to create Dolibarr PaiementFournisseur entries with the payment amount and date. Historical AP checks that have been issued but not cleared are migrated as open AP with a payment status flag, and the customer reconciles the payment method in Dolibarr's bank reconciliation module post-migration.

Sage FA_Asset records include acquisition date, acquisition cost, depreciation method (straight-line, declining balance, sum-of-years), accumulated depreciation, net book value, useful life, and asset category. We map these to Dolibarr's Asset module if the Immobilisation module is enabled. Sage depreciation methods are translated to Dolibarr's amortization_type and amortization_rate fields. FA_Asset category codes map to Dolibarr's asset_type classification. Depreciation schedules are reconstructed as Dolibarr amortization lines with the original Sage journal entry dates. If the Dolibarr Immobilisation module is not active at migration time, we deliver the asset register as a structured CSV with a mapping guide for manual entry.

Sage open sales orders migrate to Dolibarr's Commande table with status = 'Draft' or 'Validated' depending on whether fulfillment has begun. The sales order number maps to Dolibarr's ref field. Line items map to Dolibarr's commandedet table with product reference, quantity ordered, unit price, and warehouse assignment. Sage order total, tax amount, and discount percentage recalculate against the Dolibarr line entries during the transform step to ensure totals match. Orders that are fully shipped in Sage map to Dolibarr shipments ( Expedition ) rather than Orders.

Sage PO records migrate to Dolibarr's CommandeFournisseur table. We flag partially-received POs during discovery because Sage inventory receipts may have already been applied in IC_InventoryReceipt without closing the PO. The customer decides whether to migrate the PO as an open order with remaining receipts pending or to close the PO and enter receipts as separate Dolibarr incoming shipment records. PO line items map to Dolibarr's commandedetfourn with product reference, quantity ordered, quantity received, and unit cost. Unit cost from Sage becomes Dolibarr's purchase_price field.

Sage JC_Job tables hold project structures with phases, cost codes, and budget vs. actual tracking at the JC_Transaction level. Dolibarr has no native cost-code structure — we map each Sage JC_Job to a Dolibarr Project with Phase mapped to a Task at the top level, and Sage cost codes mapped to Task notes or custom extrafields. Budget vs. actual amounts migrate as Task-level custom extrafields (budget_amount, actual_amount, variance). The customer activates Dolibarr's Project module before migration. We note that Sage job costing workflows (approval routing, cost-code validation) have no Dolibarr equivalent and document the rebuild scope in the automation inventory deliverable.

Sage payroll tables (PR_Payroll and PR_Employee) contain employee records with year-to-date earnings, tax withholdings, and benefit deductions. We map active employees to Dolibarr's llx_societe_per_user table and payroll registers to llx_salary. Garnishment setups and deduction codes require manual mapping to Dolibarr's salary withholding configuration. If the customer has enabled the HR module, we also map employee addresses, emergency contacts, and employment status. Note that Sage payroll configurations (tax table setups, deduction rules, garnishment logic) are not migratable to Dolibarr and require manual reconfiguration by the customer's HR administrator.

Sage 100cloud stores user-defined fields in module-specific extension tables (IC_Item_UDF, AR_Customer_UDF, etc.) whose schema varies by company database. There is no standardized export path for these. We identify every UDF column during discovery by querying the SQL schema for non-standard columns per module, export them to a sidecar CSV named per module (e.g., customer_udfs.csv, vendor_udfs.csv, item_udfs.csv), and deliver a mapping guide showing each UDF column name, data type, and the corresponding Dolibarr extrafields module field creation steps. The customer's admin creates the extrafields in Dolibarr and imports the sidecar CSV manually after migration. This is a customer-visible step that must be planned and budgeted separately.