Migrate from Sage 100cloud to Odoo ERP

Sage AR_Customer master records map to Odoo res.partner with partner_type = 'contact'. Billing address, shipping address, payment terms, credit limit, and salesperson assignment transfer to the corresponding Odoo fields. Sage customer IDs are preserved in a custom reference field for audit. Dedup matching uses Sage CustomerCode as external ID.

Sage AP_Vendor records map to Odoo res.partner with partner_type = 'supplier'. 1099 settings, W-9 status, and tax ID transfer to Odoo's fiscal country settings and partner fields. Vendor payment terms and 1099 flag values must be mapped explicitly since Odoo stores tax reporting configuration in fiscal positions rather than on the partner record.

Sage GL account codes map to Odoo account.account with corresponding account_type (asset, liability, equity, income, expense). Sage account segments (Division, Department) can be modeled as Odoo account.group or analytic.account tags, depending on whether the customer needs separate reporting dimensions. We preserve the full account code structure in the account.account code field.

Sage IC_Item records map to Odoo product.product linked to product.template. Unit of measure, cost method (standard, average, FIFO), and item type (stockable, consumable, service) transfer directly. Sage's multi-warehouse flag maps to Odoo's stock.warehouse active status. Lot/serial tracking settings from Sage transfer to Odoo's traceability configuration on the product template.

Multi-level Sage BOM structures from IC_BOM and IC_BOMComponent tables reconstruct as Odoo mrp.bom records with recursive mrp.bom.line entries. Sage BOM routing (work centers, labor rates) maps to Odoo mrp.routing/workcenter. Single-level BOMs where all components are raw materials map cleanly; multi-level assemblies with subassemblies require a topological sort during ETL to ensure parent records insert before child records. If the customer uses Sage's job-costing BOMs tied to JC_Job, those BOMs are handled in the project migration step.

Sage IC_Bin records map to Odoo stock.location entries structured under the corresponding stock.warehouse's view locations. Sage multi-bin per warehouse maps to Odoo's location hierarchy (WH/Stock/Zone/Shelf/Bin). Bin capacity constraints from Sage do not transfer; Odoo does not enforce bin-level capacity by default, so the customer decides whether to configure this as a post-migration Odoo setting.

Open accounts receivable invoices from AR_Invoice and AR_Payment transfer to Odoo account.move with type 'out_invoice' and state 'posted'. Invoice line items (product, quantity, unit price, tax) map to account.move.line. Payment terms and aging buckets from Sage transfer as corresponding Odoo invoice terms and payment registration records. Fully paid invoices can be migrated as posted moves; partially paid invoices record the payment against the invoice in Odoo's reconciliation module.

Open accounts payable invoices from AP_Invoice and AP_Payment map to Odoo account.move with type 'in_invoice'. Vendor references, invoice dates, due dates, and amounts transfer to the corresponding Odoo fields. Historical checks already cleared in Sage are not migrated unless the customer requires a full payment history for audit purposes, which is a scoping decision.

Open Sage sales orders and invoices migrate to Odoo sale.order (for unfulfilled orders) and account.move (for posted invoices). Header-level custom fields from Sage are flagged for manual re-entry since the custom field export path requires separate schema extraction from module-specific extension tables. We map order status from Sage (open, partially shipped, closed) to Odoo sale.order state.

Open Sage purchase orders migrate to Odoo purchase.order. We flag partially-received POs during scoping so the customer can decide whether to carry forward the partial receipt history. Sage PO line-item detail (product, quantity ordered, quantity received, unit cost) maps to Odoo POLine. If Sage stores receipts as separate IC_Receipt records, we apply those against the PO during migration to reflect the correct received-but-not-invoiced quantity.

Sage JC_Job records with phases, cost codes, budget vs. actual, and transaction history (labor, materials, subcontractor) translate to Odoo project.project with nested project.task entries. Sage cost codes map to analytic account tags or cost-center accounts in Odoo. We preserve budget amounts and actuals as Odoo project milestones and task costs where Odoo's project budget module is available (Enterprise or installed from OCA). Historical job transactions migrate as project.task records with time and cost entries.

Sage FA_Asset records (acquisition cost, depreciation method, book value, useful life, accumulated depreciation) map to Odoo account.asset.asset with the corresponding depreciation table entries. Depreciation schedules reconstruct from Sage FA_Depreciation records. Sage asset categories map to Odoo asset profile, which controls the depreciation method and journal.