Migrate from Sage 200cloud to Dolibarr ERP

Sage 200cloud Departments are used as a dimensional layer on Nominal Accounts and have no direct Dolibarr equivalent because Dolibarr uses a flatter account structure. We either map Departments to Dolibarr Projects (if the customer uses project costing) or absorb the department dimension into the nominal account code itself (e.g., prefixing account codes with a department identifier). The customer chooses the strategy during scoping, and we document it in the chart-of-accounts migration spec.

Sage 200cloud Cost Centres are secondary dimensional references on Nominal Accounts and transactions. Dolibarr does not have a native cost-centre concept. We map Cost Centres to Dolibarr Tags on Third Parties (for customer/supplier cost-centre attribution) or to Projects with a cost-centre naming convention. We flag any transaction-level Cost Centre assignments that require manual re-assignment or a custom field in Dolibarr.

Sage 200cloud Nominal Accounts map to Dolibarr Accounting Account records (the account code and name). We export via the Sage 200 Nominal Account CSV report and import into Dolibarr's llx_accounting_account table. Sage's Department and Cost Centre dimension on each account is handled as a configuration step (either embedded in the account code or linked to a Project). Account type (Asset, Liability, Income, Expense) maps from Sage's account classification field to Dolibarr's pcg_type and pcg_subtype fields.

Sage 200cloud Customer records map to Dolibarr Third Party records with the Third Party Type set to Customer. We export via the Customer Record CSV report, map address fields, payment terms, and nominal credit control codes. We flag the 215-character Customer Email address limit (Known Issue 8225) and surface any records exceeding the cap as a pre-migration action item for truncation or customer notification.

Sage 200cloud Supplier records map to Dolibarr Third Party records with the Third Party Type set to Supplier. Payment terms, bank details (IBAN, BIC), and nominal code assignments migrate faithfully. Supplier statements export via the Supplier Reporting CSV and are made available as PDF attachments or reference data in Dolibarr's supplier record notes.

Sage 200cloud SOP documents (headers, line items, allocation quantities, and ready-for-invoice status) map to Dolibarr Customer Order records. SOP line allocation and dispatch status requires mapping to Dolibarr's shipment and stock movement modules, which the customer must enable in Dolibarr before import. Order headers must import after the linked Customer Third Party is present in Dolibarr.

Sage 200cloud POP records map to Dolibarr Supplier Order. Confirm Goods Received status from Sage carries into Dolibarr as the Receipt status field. Known Issue 8159 (extra blank columns in the POP form) may introduce trailing empty fields in the CSV export; we strip blank columns before mapping to avoid field-offset errors in the Dolibarr import.

Sage 200cloud Product Groups map directly to Dolibarr Categories with Category Type set to Product. This mapping must complete before Stock Items import because Dolibarr allows category assignment during product creation. We extract the full product group hierarchy and reconstruct it as a nested Dolibarr category tree.

Sage 200cloud Stock Items map to Dolibarr Product records. We extract via the Stock Item CSV report and map unit of measure, cost price, sales price, and stock warehouse levels. Sage's multi-warehouse configuration maps to Dolibarr's warehouse module, which the customer must enable. Variant tracking (batch, serial) from Sage maps to Dolibarr's lot/serial number module.

Sage 200cloud stock opening balances must be imported after Product Groups and Stock Items are present in Dolibarr. We extract the opening balance quantity and value from the Sage stock opening balance report and create Dolibarr stock movement records of type 'Import' to set initial stock levels without triggering nominal postings.

Sage 200cloud bank accounts stored as nominal records with type flags map to Dolibarr Bank Account records. Opening balance, currency, and IBAN details migrate directly. We verify that the corresponding nominal account code exists in Dolibarr before creating the bank account record to satisfy Dolibarr's internal accounting reference.

Sage 200cloud Fixed Assets tied to Nominal Accounts with acquisition date, depreciation method, and net book value map to Dolibarr Asset records. Depreciation schedules require value-mapping: Sage's depreciation method codes translate to Dolibarr's asset amortization type (linear, degressive). Any partial-year depreciation from Sage is calculated and carried into Dolibarr's first-period adjustment.

Historical posted invoices and credit notes export from Sage 200cloud via the reporting engine. We map invoice headers, line items, and tax rates to Dolibarr Invoice records. Document references must match exactly or Dolibarr creates duplicate entries. We flag any invoices with document references that are non-unique or missing as a pre-migration remediation task. Posted invoices are imported as 'Validated' (locked) status in Dolibarr to preserve accounting history.

Sage 200cloud Nominal Budget records map to Dolibarr budget lines if the customer has enabled the Budget module. We extract budget amounts by Nominal Account and period and import into Dolibarr's budget structure. If the Budget module is not enabled, we deliver the budget data as a CSV reference sheet for the customer's admin to configure post-migration.

Sage 200cloud user-seat assignments tied to licensing tiers map to Dolibarr User records. We extract users by email and map to Dolibarr's User table with appropriate permission sets. Any record-level ownership (Customer Owner, Supplier Owner) resolves by matching the Sage owner email to the migrated Dolibarr user.