Migrate from Sage 300cloud to Dolibarr ERP

Sage 300cloud's hierarchical account structure with up to 10 segment codes flattens into Dolibarr's account list where each segment becomes part of a dot-delimited or concatenated account code string. We preserve account code, description, account type (Asset, Liability, Equity, Revenue, Expense), and active/ina status. Multi-segment accounts used for dimensional reporting become Dolibarr account codes with category tags for filtering; the customer reconciles whether full dimensional reporting requires a third-party add-on or a reporting export to a BI tool.

Sage 300cloud customer master records map to Dolibarr Third-Party objects with the Customer checkbox enabled. We transfer billing and shipping addresses, payment terms (Net 30, 2/10 Net 30), credit limits, and multi-currency settings as Dolibarr Extra fields. Open AR invoices carry invoice number, date, due date, line-item detail, and discount terms to Dolibarr Customer Invoice records. Customer ID from Sage 300cloud is preserved in the Third-Party ref_int field for traceability.

Sage 300cloud vendor master records map to Dolibarr Third-Party objects with the Supplier checkbox enabled. US installations include 1099 reporting flags migrated as Dolibarr Extra fields. Open AP invoices include discount terms and aging buckets mapped to Supplier Invoice records. Historical 1099 and 1096 data is extracted as a reference document and provided to the customer for manual year-end reconciliation in Dolibarr's accounting module.

Sage 300cloud inventory items with valuation method (FIFO, Average, Standard) and warehouse/bin assignments map to Dolibarr Product records with the Stated and Buy/Sell flags set. Valuation method assignment migrates as a Dolibarr Extra field; the actual cost calculation does not automatically carry forward because Dolibarr calculates on-hand value at migration time using the current stock valuation method selected. Warehouse and bin assignments migrate to Dolibarr warehouse locations with location-level stock counts seeded from Sage 300cloud's last inventory snapshot.

We extract Sage 300cloud's current AR aging summary and open invoice details to seed Dolibarr with accurate open balances. Each open item carries a unique document number, apply-to reference, and discount taken, all migrated as Dolibarr Customer Invoice records with status set to Open. The total open AR balance is reconciled against the Sage 300cloud trial balance before we mark the import complete. If the customer requests beginning balance only, we create opening entry journal lines rather than individual open invoices.

Current AP aging summaries and open invoice details from Sage 300cloud seed Dolibarr Supplier Invoice records with status Open. Discount terms and aging buckets map directly. The total open AP balance is reconciled against the Sage 300cloud trial balance before import sign-off. If beginning balance seeding is preferred over individual invoices, we create opening entry journal lines with the AP account as the offset.

GL journal entries, batch headers, and source module references export by fiscal period from Sage 300cloud. We map them to Dolibarr Accounting Record (AccountancyRecord) entries with debit/credit amounts, account references, and period assignment. Complex recurring entries and reversing journal templates do not migrate because the recurrence logic is not portable; we deliver a written list of recurring templates for the customer's admin to rebuild in Dolibarr. Historical entries beyond 24 months may be scoped as reference-only records at the customer's request to reduce import volume.

Sage 300cloud fixed asset registers include acquisition date, cost, depreciation method, accumulated depreciation, and current book value. We map to Dolibarr Asset records with acquisition date, acquisition value, and cumulative depreciation. The primary depreciation schedule migrates with method (straight-line, declining balance) and monthly depreciation amounts seeded as accounting entries. Subsequent depreciation entries are posted in Dolibarr from the migration date forward based on the configured schedule; no retroactive depreciation recalculation is performed during migration.

Sage 300cloud tax groups and tax codes carry jurisdiction-specific rates, tax type (sales vs. use), and posting accounts. We map each Sage 300cloud tax code to a corresponding Dolibarr VAT rate configuration with rate percentage and applicable product/service category. International tax configurations with multiple tax authorities per code require re-association in Dolibarr's tax management module because the multi-authority grouping logic differs between platforms. US sales tax configurations (state-level, nexus-based) migrate as Dolibarr local tax rules with the applicable tax collected zone.

Bank codes, account numbers, bank reconciliation formats, and current cleared balances migrate as Dolibarr Bank Account records. EFT payment processing settings are documented during scoping and provided as a configuration checklist for the customer's admin to re-enter in Dolibarr's bank account setup because EFT format mappings (ACH, wire, SEPA) are destination-specific and not portable between platforms.

Documents linked to Sage 300cloud transactions (invoices, purchase orders, receipts) are stored in a configurable file path on the host server. We document the attachment directory path, extract files matching transaction document references, and import them into Dolibarr's document management layer linked to the corresponding record. This step requires read access to the Sage 300cloud host file system or a backup of the attachment directory. Binary integrity is verified by comparing file checksums before and after import.

Sage 300cloud payroll registers, employee earnings, deductions, and employer tax contributions export by pay period. Year-to-date accumulators (gross wages, federal withholding, state withholding, FICA, benefits deductions) map to Dolibarr HR Employee records with salary entries and YTD fields as Extra fields. Custom deduction codes require re-association in Dolibarr's HR configuration because deduction type logic differs between platforms. Year-end tax form data (W-2, 941) is extracted as reference PDFs for the customer's records; Dolibarr's HR module does not generate US federal tax forms in the base version.