Migrate from Sage Business Cloud X3 to Dolibarr ERP

Sage X3 Business Partners (BPCUSTOMER and BPSUPPLIER types) map directly to Dolibarr Third-Party (Societe) records. The BP category field (customer, supplier, or both) maps to Dolibarr's Client and Fournisseur flags. Address, payment terms, currency, and credit limit fields migrate to Dolibarr's standard third-party fields. We resolve the X3 BP type code (BPR type) against Dolibarr's Tiers type to ensure the correct Client/Fournisseur flag is set at import time. Custom fields on Business Partners in X3 (stored as extended columns) migrate to Dolibarr extrafields.

Sage X3 Sales Orders (exported via ZSOH template) map to Dolibarr Customer Order (Commande Client). X3 order header fields (order number, order date, customer reference, payment terms) map to Dolibarr Commande Client fields; X3 order lines map to Dolibarr lignes commandes with product reference, quantity, unit price, and VAT rate preserved. If the X3 order is still in draft or confirmed status, it becomes a Dolibarr Proposal (propal) first and is converted to Order on confirmation. Closed or invoiced orders are migrated as Order records with the invoice reference stored in a custom field.

Sage X3 Purchase Orders map to Dolibarr Supplier Order. The X3 supplier reference, order date, payment terms, and line items (product, quantity, cost price, delivery date) migrate to Dolibarr lignes commandes fournisseur. Purchase order approval workflows in X3 are not migrated; open POs in approved or pending-receipt status are migrated as open orders for the Dolibarr purchasing team to manage. PO commitments in X3 that have not yet posted are recorded in Dolibarr's project module as commitments against a budget if the project module is active.

Sage X3's hierarchical chart of accounts (with segment codes, cost centres, and dimensions) maps to Dolibarr's accounting module plan comptable. X3 account numbers map directly to Dolibarr account codes; account descriptions map to the label field. If X3 uses analytical dimensions (up to 9 per ledger), we create Dolibarr extrafields for dimension tags rather than a separate analytical accounting module unless the Dolibarr accounting module is licensed. Multi-ledger X3 setups require separate Dolibarr accounting configurations per ledger if the ledgers have different charts of accounts.

Open AP and AR invoices in Sage X3 (with due dates, outstanding amounts, payment terms, and aging data exported via templates) map to Dolibarr Facture Client and Facture Fournisseur records. We preserve the original invoice number, invoice date, due date, and open amount. Closed invoices (fully paid) are migrated as paid invoice records with a flag in extrafields marking them as historical. Credit notes and debit notes in X3 map to Dolibarr avoir records linked to the original invoice. The X3 payment terms code maps to Dolibarr's condition_reglement field.

Sage X3 Fixed Assets (acquisition cost, depreciation schedules, asset register entries) map to Dolibarr's Asset module. X3 depreciation methods (linear, declining, sum-of-years) map to Dolibarr's equivalent amortization method fields. Each X3 depreciation book (GAAP, tax, statutory) becomes a separate Dolibarr asset record with its own amortization schedule, or a single asset with multiple amortization lines if the Dolibarr asset module version supports parallel books. Disposal records in X3 migrate as Dolibarr asset closure entries with disposal date and proceeds.

X3's parallel depreciation books per asset (e.g., GAAP vs. tax book) migrate to Dolibarr as separate amortization line sets against a single asset record if the Dolibarr asset module supports this, or as multiple asset records with a custom field linking them if the module does not support parallel books natively. The X3 depreciation convention (half-year, mid-month) maps to Dolibarr's date debut amortissement and mode calcul. Each book's accumulated depreciation at migration date is entered as the opening accumulated amortization amount.

Sage X3 Products (with Bills of Materials, lot/serial tracking, expiry dates, and multi-location stock) map to Dolibarr Product records. X3 product type (stockable, service, kit) maps to Dolibarr's product type. Stock levels per X3 site/location migrate to Dolibarr warehouse stock entries. Lot and serial numbers migrate to Dolibarr extrafields if the lot/serial module is active. BOMs in X3 do not migrate to Dolibarr manufacturing module (see gotcha); we export BOM data to a separate structured CSV for manual rebuild in Dolibarr or a third-party manufacturing module.

Sage X3 Production Orders (linked to BOMs, routings, work centres, and consumption tracking) have no equivalent in the standard Dolibarr manufacturing module. We export work order headers, operations, and component consumption to a structured CSV and document the mapping so that the customer's admin can rebuild in Dolibarr's project module with a manufacturing extension or a third-party tool. Work order status and operation completion percentages are not natively supported in standard Dolibarr and require extrafields configuration or a community manufacturing module.

Sage X3 Budgets and Commitments (tying purchase orders and contracts to GL postings across periods and scenarios) map to Dolibarr Project budget lines if the project module is active, or to a custom accounting import mapping against a budget control account in the chart of accounts. Commitments representing open purchase orders are linked to the migrated Supplier Order records. Budget versus actual reporting in X3 is documented in a separate Excel workbook for the customer's admin to replicate in Dolibarr reporting or a BI extension.

Sage X3 Users (named-user model, not email-based in older deployments) map to Dolibarr User records. We resolve X3 user IDs to Dolibarr user accounts by email if available, or by matching the X3 user login to a newly provisioned Dolibarr user with the same identifier. Role-based access control in X3 (function-level permissions per site and company) maps to Dolibarr permission sets per module. Passwords and active/inactive status do not migrate; all migrated users receive a password reset link. Orphaned permissions from X3 are flagged in the handoff document for manual Dolibarr permission assignment.

X3 custom fields on all migrated objects (stored as extended table columns) migrate to Dolibarr extrafields with equivalent data types. String fields map to varchar extrafields; numeric fields map to int or float; date fields map to date. Multi-select or tag-style custom fields in X3 map to Dolibarr select or checkbox extrafields with the same option list. We detect all X3 custom fields during discovery and pre-create the corresponding Dolibarr extrafields before any data load begins, so that data import does not skip or truncate custom field values.