Migrate from Sage 500 to Odoo ERP

GL Account codes, account types, and segment hierarchies from the Sage 500 GL00100 and GL00105 tables map directly to Odoo Accounting > Chart of Accounts. Sage 500's multi-segment chart of accounts (up to 9 segments) maps to Odoo's account code structure and optionally to Analytic Account dimensions for cost-center reporting. We preserve account type (Asset, Liability, Equity, Revenue, Expense), active/inactive status, and the retains-earnings account reference. Post-migration, Odoo's accountant reconciles the opening balance via an opening entries journal.

Sage 500 Customer master records from the AR_Customer table map to Odoo Contacts with the customer flag enabled. We map billing address, shipping address, payment terms, 1099 configuration, and credit limit. Sage 500's customer-specific discounts and price lists require mapping to Odoo Pricelist records. If Sage 500 stores separate billing and shipping contacts per customer, we split them into individual Odoo contacts with the correct address type and a shared parent company contact if Odoo's company-sharing model is used.

Sage 500 Vendor master records from the AP_Vendor table map to Odoo Contacts with the vendor flag enabled. Tax ID (EIN/VAT), 1099 configuration, payment terms, and default expense accounts transfer. Sage 500 vendor-specific discounts and approval thresholds require manual configuration in Odoo Purchase settings after migration. Vendor bank details for ACH/wire transfers migrate to Odoo's vendor bank account fields and should be validated against the source documents post-import.

Sage 500 open receivables from the AR_OpenInvoice and AR_Invoice tables map to Odoo Account Move records with type 'out_invoice' and state 'posted'. We preserve invoice number, invoice date, due date, aging bucket amounts, and the customer-linked contact. The destination's aging period configuration must match Sage 500's aging buckets (typically 0-30, 31-60, 61-90, 90+) to avoid mis-stated aging reports immediately after go-live. Reconciliation is done manually or via Odoo's supplier statement matching after import.

Sage 500 open payables from the AP_OpenInvoice and AP_Invoice tables map to Odoo Account Move records with type 'in_invoice' and state 'posted'. Vendor reference, invoice date, due date, and aging bucket amounts transfer. Odoo's AP aging report is driven by the due date and payment terms on each bill; the customer configures matching aging periods in Odoo Accounting settings before migration to ensure the first aging report matches the Sage 500 source.

Open and historical Sales Orders from the OE_OrderMaster and OE_OrderDetail tables map to Odoo Sale Orders. We preserve order number, order date, requested ship date, customer reference, line items with quantities and unit prices, warehouse assignment, and order status (Open, Closed, Cancelled). Fulfillment dates and backorder flags transfer as custom fields or notes. Fully shipped and invoiced orders migrate as closed records for historical reference; open orders migrate with their full line detail for continued fulfillment in Odoo.

Open and historical Purchase Orders from the PO_OrderMaster and PO_OrderDetail tables map to Odoo Purchase Orders. We preserve PO number, vendor, order date, expected delivery date, line items with quantities and costs, and line-level status. Odoo automatically computes landed costs if the Sage 500 PO includes freight and miscellaneous charges. Blanket Orders and Contracts from Sage 500 map to Odoo Blanket Orders; we flag these with a custom field for admin visibility.

Inventory master records from IM_Item and IM_ItemWarehouse map to Odoo Products with type 'storable'. We transfer item number, description, SKU (hs_sku equivalent), costing method, item weight and dimensions, default warehouse, and current on-hand quantities. Multi-warehouse setups in Sage 500 require mapping each site-specific item location to an Odoo warehouse. FIFO vs. LIFO cost layers require explicit confirmation of the destination's costing engine before we commit to a cost-carry-over strategy; standard cost extracts cleanly into Odoo's standard price field. UOM (unit of measure) and UOM category mapping is required before inventory quantities can import accurately.

Sage 500 BOMs from the IC_BOMHeader and IC_BOMDetail tables map to Odoo Manufacturing > Bill of Materials. We preserve BOM code, product variant assignment, component lines with quantities, bom type (kit vs manufacture), and routing assignment. If Sage 500 uses phantom BOMs for kits, we map these to Odoo's 'kit' type. Engineering BOM versions migrate as separate Odoo BOM revisions with an effective date. This mapping requires Odoo Manufacturing module installed; Community or Enterprise edition both support BOM migration.

Sage 500 routing and work-center definitions from the IC_Routing and IC_WorkCenter tables map to Odoo Work Center definitions and optionally to Operations (mrp.routing.workcenter) records. We preserve work center code, description, capacity, and default labor and overhead rates. Step sequence, operation times, and inter-operation dependencies transfer as Odoo work order operations. The customer must configure Odoo Manufacturing module before this object migrates; without it, routing records are delivered as a configuration reference document.

Fixed Asset records from the FA_Asset and FA_Depreciation tables map to Odoo Accounting > Assets. We transfer asset code, description, asset class, acquisition date, acquisition cost, depreciation method (straight-line, declining balance, sum-of-years), useful life, and accumulated depreciation to date. Odoo's asset engine recalculates future depreciation from the acquisition date and method; the opening accumulated depreciation is set as the initial depreciated value so the asset balance sheet value matches Sage 500 on day one. Customer-specific depreciation conventions (half-year, mid-month) require manual configuration in Odoo after import.

General Ledger journal entries from the GL_Transaction and GL_Distribution tables map to Odoo Account Move records. We preserve journal, batch number, posting date, source module (AP, AR, Inventory, Manufacturing), full debit/credit line detail, and the originating document reference. Historical journal entries import as posted moves for balance verification. If Sage 500 uses reversing entries, both the original and reversing entries migrate so the net effect in Odoo matches Sage 500's year-end trial balance. Locking periods in Odoo (fiscal lock dates) must be set before journal import begins.