Migrate from Sage 300cloud to Odoo ERP

Sage 300cloud's hierarchical account structure with up to 10 segment codes maps to Odoo's account.account records with a corresponding Analytic Accounting plan for multi-dimensional reporting. We parse Sage's segment structure during discovery, determine which segments carry account-type information versus reporting-only dimensions, and create Odoo accounts with the appropriate account codes and types (receivable, payable, liquidity, revenue, expense). Segments used purely for reporting become Analytic Accounts in the Analytic Accounting module rather than separate account records. This is the most consequential mapping in the migration because Sage segment codes often encode cost center, department, and project dimensions that Odoo separates across account type and analytic plan.

Sage 300cloud customer master records with billing address, payment terms, credit limit, and multi-currency settings map to Odoo res.partner records with the customer flag set. We preserve the Sage customer code as the partner's ref field, which serves as the external ID for reconciliation. Payment terms map to Odoo's account.payment.term table, and multi-currency settings map to Odoo's res.currency configuration. Shipping addresses on the customer record migrate as res.partner records of address_type=delivery linked to the customer partner.

Sage 300cloud vendor master records mirror the customer structure and map to Odoo res.partner records with the supplier flag. US-based vendors carry 1099 reporting flags that map to Odoo's l10n_us_hr_payroll and 1099 reporting fields if Odoo is configured for US localization. Vendor payment terms and EFT settings are documented for manual configuration in Odoo's Accounting settings. The vendor code from Sage becomes the partner ref for dedupe and reconciliation.

Open AR invoices from Sage 300cloud migrate as Odoo account.move records of type='out_invoice' with state='draft' for unreconciled items. Each Sage invoice line maps to account.move.line with matched account_id, partner_id, and analytic_account_id from the Chart of Accounts mapping. We preserve invoice number, invoice date, due date, and discount terms. After account.move records are created, we run an Odoo reconciliation (account.reconcile.model) to match open AR against the corresponding customer receivable account balance, carrying forward the open aging as it stood in Sage at the cutover date. Historical paid invoices do not migrate; only open items carry forward as beginning balances.

Open AP invoices from Sage 300cloud migrate as Odoo account.move records of type='in_invoice' with state='draft'. Each Sage AP line maps to account.move.line with matched account_id from the vendor account mapping. Discount terms and aging buckets are preserved in custom fields on the account.move.line. We run vendor reconciliation against the vendor payable account so that Odoo's vendor aging report matches Sage's pre-migration AP aging. Historical paid AP invoices do not migrate; only open items carry forward as beginning balances.

Sage 300cloud inventory items with valuation method (FIFO, Average, Standard), warehouse assignments, and bin locations map to Odoo product.template with the applicable costing method set. Sage's valuation method selection maps to Odoo's product costing configuration (FIFO, Average, or Standard). Multi-warehouse setups in Sage become Odoo's warehouse records under Inventory > Configuration > Warehouses. Bin locations map to Odoo's location records within each warehouse. Products without a defined SKU in Sage receive a generated internal reference for Odoo compatibility. Odoo's product variants handle any size, color, or attribute-based product splits that were managed as separate Sage inventory items.

Sage 300cloud fixed asset records with acquisition date, cost, depreciation method, accumulated depreciation, and book value map to Odoo's account.asset records. The depreciation method from Sage (straight-line, declining balance, sum-of-years digits) maps to the corresponding Odoo depreciation profile. Accumulated depreciation in Sage becomes the opening accumulated depreciation value on the Odoo asset record before the first depreciation run post-migration. Assets under Sage's active depreciation schedule carry forward with their remaining useful life recalculated in Odoo. Sage supports multiple depreciation schedules per asset; we map the primary schedule and document secondary schedules for manual setup in Odoo Asset Management.

Sage 300cloud tax codes with jurisdiction-specific rates, tax type (sales vs use), and posting accounts map to Odoo account.tax records. Sage tax groups map to Odoo's tax group configuration with the corresponding tax authority account. Multi-jurisdiction tax configurations where one Sage tax code references multiple tax authorities require Odoo's structure tax model with children taxes. US sales and use tax, Canadian GST/HST, and UK VAT configurations are all supported via Odoo's localization modules, which we configure as part of the Odoo setup before importing the tax code mappings. Tax codes that have been inactive or zero-rated in Sage are migrated with their active=False flag set.

Sage 300cloud bank codes, account numbers, and current cleared balances map to Odoo account.journal records of type='bank' or 'cash'. The Sage bank reconciliation format (BAI, OFX, QIF) is documented as a configuration requirement for Odoo's bank statement import settings. Current cleared balances migrate as the opening bank balance in the corresponding Odoo journal. Bank reconciliation open items (cleared in Sage but pending confirmation in Odoo) are documented as a reconciliation worksheet for the customer's finance team to complete post-go-live.

Sage 300cloud payroll registers, employee earnings, deductions, employer tax contributions, and year-to-date accumulators migrate to Odoo's payroll module if the customer licenses it as part of the Odoo deployment. We extract payroll by pay period and map employee records to hr.employee, deduction codes to hr.salary.rule, and YTD accumulators to the corresponding salary rule categories. Custom deduction codes that exist in Sage but not in Odoo's default payroll configuration require manual rule creation in Odoo before the YTD data can post correctly. If the customer's Odoo deployment does not include the payroll module, we migrate YTD totals as account.move entries against the appropriate payroll expense accounts and deliver a deduction code inventory for the customer's payroll administrator.

Sage 300cloud organizational segments used for allocation and reporting map to Odoo's account.analytic.account records. Sage segment codes that carry cost center or department semantics are the primary driver of this mapping. We create an Analytic Accounting plan in Odoo specifically for cost center reporting, map each Sage segment value to an analytic account record, and preserve the segment label and hierarchy as the analytic account's name and parent_id structure. Inter-segment elimination rules documented in Sage are recreated as Odoo analytic plan rules or as manual journal entries post-go-live. This mapping is tightly coupled with the Chart of Accounts mapping because Sage often uses segments to represent dimensions that Odoo handles through the analytic accounting module.