Migrate from Sage 500 to Dolibarr ERP

Sage 500 GL Account codes and segment structures map to Dolibarr's accounting module (comptabilité). We extract account codes, account types (Asset, Liability, Equity, Revenue, Expense), and the segment structure from the GL_Account table and map them to Dolibarr's llx_accounting_account table. Multi-segment accounts in Sage 500 (e.g., DEPT-PRODUCT-REGION) are flattened or preserved as sub-account hierarchies depending on the destination chart configuration. The customer selects or provides a compatible French plan comptable or a custom chart before migration begins.

Sage 500 IM_Customer and AP_Vendor tables map to Dolibarr llx_societe with the client and fournisseur flags set independently. We extract billing address, shipping address, payment terms, 1099 configuration, credit limits, and tax registration numbers. Sage 500's separate customer and vendor records become two entries in llx_societe with the appropriate type flags. Customer email, phone, and website map to Dolibarr's contact and address fields. Any Sage 500 customer-to-vendor relationship (a vendor that is also a customer) is preserved as two linked ThirdParty records.

Sage 500's open receivables and historical customer invoices map to Dolibarr llx_facture with type = Facture (customer). We extract invoice header fields (invoice number, date, due date, total, status) and line items (description, quantity, unit price, tax rate, discount) from the RM_InvoiceHeader and RM_InvoiceDetail tables. The Sage 500 aging bucket configuration maps to Dolibarr's payment terms and overdue handling. Paid invoices are imported with their payment status and date; open invoices are imported as open and reconciled against cash receipts during the AP/AR reconciliation phase.

Sage 500's open payables and historical vendor invoices map to Dolibarr llx_facture_fourn with type = Facture fournisseur. We extract vendor invoice number, invoice date, due date, amount, and line items from the AP_InvoiceHeader and AP_InvoiceDetail tables. The payment terms from the vendor master propagate to each invoice record. Vendor invoice status (open, paid, partially paid) is preserved so that the customer's AP team can continue the payment lifecycle in Dolibarr without re-keying.

Sage 500 SO_OrderHeader and SO_OrderDetail tables map to Dolibarr llx_commande with origin = Order. We assemble the order by JOINing header, detail, and warehouse assignment tables to produce complete records. Order status (open, shipped, invoiced, cancelled), fulfillment dates, backorder flags, and line-level pricing migrate. An order that has already been invoiced in Sage 500 is linked to the migrated invoice record via Dolibarr's order-to-invoice relationship field.

Sage 500 PO_OrderHeader and PO_OrderDetail tables map to Dolibarr llx_commande_fournisseur. We preserve PO number, vendor reference, order date, expected delivery date, and line items with quantities and pricing. Status migration covers entered, approved, received, invoiced, and closed. Line items that have been partially received are flagged with received quantities so that the receiving team in Dolibarr can close the remainder against actual receipts.

Sage 500 IM_ItemMaster and IM_ItemWarehouse tables map to Dolibarr llx_product with the produittype field set to Product (stockable). We extract item code, description, costing method (standard, average, FIFO, LIFO), on-hand quantities by warehouse, reorder point, and unit of measure. Multi-warehouse setups require us to create one Dolibarr warehouse per Sage 500 site and link item locations accordingly. If Sage 500 uses LIFO or FIFO layers, we confirm the destination Dolibarr installation's costing engine configuration before committing to a cost-carryover strategy; standard cost environments extract cleanly.

Sage 500 FA_Asset records include acquisition date, cost, depreciation schedule, accumulated depreciation, book value, and asset class. We extract the full depreciation history. Dolibarr's Asset module (activated separately in newer versions) handles asset tracking with acquisition cost, amortization types (linear, declining), and disposal records. If the destination Dolibarr instance does not have the Asset module enabled, we map Fixed Assets to Products with the type set to Asset and preserve depreciation fields in custom ExtraFields. The customer must confirm the asset module version before migration scope is finalized.

Sage 500 GL_Batch and GL_Distributions tables map to Dolibarr llx_accountingbookkeeping (or llx_acc_mouvement depending on version). We extract batch number, posting date, source module (AP, AR, Inventory, Manufacturing), and all distribution lines with account code, debit amount, and credit amount. The journal entry must be posted to a named journal (Ventes, Achats, Banque, etc.) in Dolibarr's accounting module. Sage 500's FEC-compatible export informs how we structure the debit/credit mapping for French regulatory compliance if the destination is a French entity.

Sage 500 bank module records map to Dolibarr llx_bank and llx_bank_account. We extract bank account codes, bank names, GL account linkages (each bank account reconciles to a GL account in llx_accounting_account), and any existing bank reconciliation records. The reconciliation state (reconciled date and batch) is preserved so that the customer's accounting team can continue bank reconciliation from the last reconciled point in Sage 500.

Sage 500 tax codes (TX_TaxCode, TX_TaxRate) are jurisdiction-specific configurations that map to Dolibarr's llx_c_tva table. We extract the tax code mappings and rate assignments from the tax configuration tables, but customer-specific tax exemptions and nexus-specific rules are configuration items that the customer's accountant must set up in Dolibarr's tax regime configuration before invoices are generated. We deliver a tax code mapping table as part of the migration handoff document.

Sage 500 UDFs are configured per company at the document level (SO, PO, Invoice, Item) and stored in extended columns on the base table or in separate UDF tables. We inventory all active UDFs during scoping, map their data types to Dolibarr ExtraField types (varchar, int, float, datetime, select, checkbox), and create the ExtraField definitions in Dolibarr's llx_extrafields table before the relevant objects are imported. UDF values are loaded in the same import batch as the parent record.

Sage 500 segment values (departments, cost centers, projects) used as GL dimensions map to Dolibarr's llx_projet table for project-level tracking or to auxiliary accounting accounts (comptes analytiques) if the customer uses Dolibarr's analytical accounting module. We extract all active segment values and map them to the chosen destination. If the destination uses a different segment structure or no analytical accounting at all, we document the gap and flag it for the customer's finance team to resolve before go-live.