Migrate from Sage Intacct to Odoo ERP

Sage Intacct GL accounts map 1:1 to Odoo Account records. Account number, name, type (asset, liability, equity, revenue, expense), and active status migrate directly. Account hierarchy (parent/child relationships) maps to Odoo's parent_id on Account and controls account groupings in Odoo's financial reports. We preserve the Sage Intacct account type mapping to ensure Odoo's debit/credit balance logic is correct after import.

Sage Intacct's five dimensions (department, class, location, customer, project) are a persistent analytical tagging layer that must be mapped to Odoo's Analytic Accounts and Tags. We create one Analytic Account per unique combination of Sage Intacct dimension values used in the transaction history, and map the five dimension types to Odoo's analytic plan structure. Dimension values that are rarely used as filters are mapped to Odoo Tags instead to keep the analytic plan lean. This is the most design-intensive mapping step in any Sage Intacct-to-Odoo migration.

Historical journal entries migrate into Odoo Account Move records with dimensional tags applied as analytic line items. Sage Intacct entries with all five dimensions set receive full Odoo Analytic Account assignments; entries with partial dimension coverage are imported with available dimensions mapped and the rest flagged as unmapped in the reconciliation report. Entries in a non-posted or draft state are flagged so the customer's admin can post before migration or handle approvals post-import in Odoo.

Open Sage Intacct AP bills, vendor payments, and vendor associations migrate to Odoo Vendor Bills and their associated payment records. Vendor links are resolved using the customer/vendor master mapping (order 5). Any AP bills in pending approval state in Sage Intacct are flagged because Odoo's vendor bill workflow requires explicit invoice posting or approval routing before the account is affected.

Open AR invoices, customer payments, and customer records migrate to Odoo Customer Invoices and payments. We map the Sage Intacct customer balance-forward vs open-item setting to Odoo's invoice posting method so that collection history and aging reports are accurate after cutover. Multi-currency invoices preserve exchange rates from Sage Intacct at the time of original posting.

Sage Intacct Customer records map to Odoo Contact records with the is_company flag set, or to a parent Contact record with individual Contact records for primary/secondary contacts. Address fields, payment terms, default GL accounts, and tax ID numbers migrate directly. Custom fields on Customer use the ! prefix in Sage Intacct's REST API and require schema discovery before mapping to Odoo's custom field infrastructure.

Sage Intacct Vendor records map to Odoo Contacts with the supplier flag enabled. Remit-to addresses, payment terms, default expense accounts, and 1099 settings migrate where applicable. Custom fields on Vendor follow the same ! prefix discovery process as Customer custom fields. We verify that Odoo's vendor-specific fields (supply lead times, minimal order amounts) are populated where source data supports them.

Sage Intacct Item records migrate to Odoo Product Templates with pricing, description, unit of measure, and cost mapped. Bundle and matrix items with parent-child relationships are handled as Odoo product variants linked to a parent Product Template. GL account assignments on items (sales account, expense account, asset account) map to Odoo's accounting properties on the product. Inventory valuation methods from Sage Intacct (standard, average, FIFO) map to Odoo's inventory valuation configuration.

Sage Intacct Project headers and task hierarchies migrate to Odoo Project records and Project Tasks. Project status, billing type, customer association, and billable/non-billable flags are preserved. Sage Intacct's task-level billing granularity maps to Odoo's Timesheet product and billing rules. For projects using Sage Intacct's project dimension for GL tagging, we create Odoo Analytic Accounts linked to the Project record so that timesheet entries automatically carry the correct analytic dimension.

Fixed asset records migrate to Odoo Asset records with acquisition cost, acquisition date, asset category, and journal. Sage Intacct depreciation schedules do not transfer directly because Odoo recalculates depreciation using its own fiscal calendar and jurisdiction-specific conventions. We preserve the original acquisition cost, accumulated depreciation to date, and net book value as initial entries so that Odoo's depreciation schedule starts from the correct carrying amount. The customer validates the depreciation method (straight-line, declining balance) in Odoo Asset settings before the first depreciation run.

Sage Intacct custom objects use the nsp:: namespace prefix in the REST API (e.g., nsp::unbilled). We discover all custom object schemas via Sage Intacct's /objects/platform-apps endpoint, map relationships (one-to-one, one-to-many, many-to-one, many-to-many) to Odoo's ir.model and ir.model.fields infrastructure, and create the destination model in Odoo before any records import. Relationship traversal in Sage Intacct is limited to one hop; Odoo's relational model is similarly constrained in its default ORM, so we document any multi-hop relationship dependencies that require denormalization during migration.

Sage Intacct entity definitions, inter-company transaction rules, and consolidation mappings migrate to Odoo's Multi-Company configuration with inter-company rules and consolidated chart of accounts. Each Sage Intacct entity becomes a separate Odoo company within the same database, with cross-entity GL entries handled through Odoo's inter-company journal. If the customer uses Sage Intacct's Global Consolidations module for external financial reporting, we map the consolidation structure to Odoo's Consolidation app as a separate configuration pass after the base data migration.