Migrate from Acumatica to Odoo ERP

Acumatica Business Accounts map directly to Odoo res.partner records. Business Account class (Customer, Prospect, Vendor) maps to Odoo partner_category and the customer_rank/supplier_rank flags in Odoo 16+. Address fields (AddressLine1, AddressLine2, City, State, PostalCode, Country) map to partner address fields. Primary Contact is extracted from the Business Account contact relationships and linked as a child res.partner with type=contact attached to the parent partner.

Acumatica Vendor records map to res.partner with supplier_rank set. AP settings, payment terms, and tax ID fields migrate to corresponding Odoo partner fields (property_supplier_payment_term_id, property_account_position_id). Vendor-specific attributes stored as Acumatica UDFs require custom field mapping against Odoo's custom fields created in Studio before migration.

Acumatica Inventory Items map to Odoo product.product records. Stock status (StockItem, Non-Stock Item, Service) maps to Odoo's type field (product, consumable, service). Item categories map to Odoo product.category. Warehouse-specific quantity and availability data (AvailabilityQty) is derived in Acumatica and migrates as initial stock quant records in Odoo via stock.quant. Units of measure and stock item attributes (KvExt extension fields) map to Odoo's uom_id and attribute lines.

Acumatica GL Accounts map to Odoo account.account records. Account class (Asset, Liability, Equity, Revenue, Expense), account type, and subaccount mask migrate. Subaccount segmentation in Acumatica (defined by subaccount mask) maps to Odoo's account group structure for reporting consolidation. Active/inactive status is preserved; inactive accounts are created as archived records in Odoo for audit trail.

Acumatica Projects map to Odoo project.project records. Project budgets, tasks, employee assignments, and change orders are extracted as separate Odoo records. Acumatica project attributes stored as KvExt extension fields map to custom fields on project.project created in Odoo Studio before migration. Task hierarchy and time-tracking data migrate to Odoo project.task and account.analytic.line.

Acumatica Sales Orders map to Odoo sale.order with line items. Document status (Quote, Open, Completed, Cancelled) maps to Odoo state. Tax calculation depends on customer and item tax settings; we preserve the original tax jurisdiction and flag manual tax review in Odoo because Odoo's tax engine may compute differently from Acumatica's tax zone rules. Invoice links migrate as Odoo account.move references.

Acumatica Purchase Orders map to Odoo purchase.order. Vendor reference, line items, receipts, and amendments migrate as related records. Receipt and amendment lifecycle states map to Odoo's picking and backorder records via stock.picking. Document status preserves the PO state machine for reactivation in Odoo.

Acumatica AR and AP Invoices map to Odoo account.move records (type=out_invoice for AR, in_invoice for AP). Payment schedules, terms, and aging data are preserved as Odoo invoice lines and payment term references. Historical invoices that reference balance tables are migrated with their GL impact recorded against the mapped account.account records. Open invoices migrate first; historical closed invoices migrate on a deferred timeline pending customer confirmation of cutoff date.

Acumatica Note and NoteDoc records do not map to a single Odoo equivalent. Note text migrates as ir.attachment records with res_model set to the target model (res.partner, product.product, etc.) and res_id set to the migrated record's Odoo ID. Binary files from NoteDoc are uploaded as ir.attachment binary fields. We extract NoteID, EntityID, EntityType, NoteText, and NoteDoc binaries during the extraction phase and reconstruct the attachment tree in Odoo by resolving the migrated entity IDs.

Acumatica UDFs stored in extension DACs and exposed under the 'custom' namespace in the REST API require explicit field discovery before mapping. We query the entity schema endpoint for each migrating entity to enumerate all CustomStringField, CustomDateField, and CustomNumberField definitions. Each UDF maps to an Odoo custom field created in Studio (ir.model.fields) with the matching type. We flag any UDFs that cannot be represented as native Odoo field types and document them for the customer's admin to resolve post-migration.

Acumatica Warehouses map to Odoo stock.warehouse records with bin structures preserved as Odoo stock.location hierarchy. Multi-warehouse configurations are mapped to separate Odoo warehouses with location-specific stock rules. Warehouse assignments on inventory items are preserved as Odoo stock.quant location references.

Acumatica Employee records map to Odoo hr.employee. Compensation history, department assignments, and timecard data are preserved as Odoo hr.employee custom fields and related records. Effective-dated rows in Acumatica migrate as separate hr.employee records or date-range records depending on the customer's Odoo HR configuration.