Migrate your Axelor ERP data

Partner is Axelor's unified object for customers, suppliers, and prospects. Supports addresses, bank details, and contact persons with full one-to-many relationships. Schema is stable across versions; we extract via the Partner API endpoint or direct DB query and map to Account/Company objects in the destination.

Products cover both stocked items and services with BOM support for manufacturing. Product variants, units of measure, and supplier info are stored as related records. We handle multi-UoM by normalising to the primary unit at migration time.

Orders carry line items, taxes, discounts, and status workflows. Order-to-invoice linking is preserved via the originId field. We extract order history including confirmed, partially fulfilled, and cancelled states as separate record flags.

Axelor invoices are multi-currency and multi-company aware. We preserve invoice lines, tax computation, payment terms, and overdue flags. Open invoices vs historical records are separated so that only confirmed invoices are ported as financial data.

Projects contain Tasks, Milestones, Time Entries, and Invoicing plans. We extract the full project hierarchy including subtask nesting, assigned users, and billing rates. Project status and custom fields from Studio are mapped as custom properties in the destination.

Tasks belong to Projects and carry status, priority, assignees, and custom fields. Subtask inheritance varies by Axelor version; we flatten the hierarchy where the destination does not support nested tasks and carry the parent-task reference as a text field.

Stock Moves track internal transfers, receipts, and shipments with real-time inventory impact. We extract move lines, warehouses, and lot/serial numbers. Open moves at migration time are flagged so the destination opens with accurate on-hand quantities.

The Chart of Accounts, Journals, and Journal Entries form the accounting core. Axelor stores journal entries with debit/credit lines and analytic accounts. Multi-company journals require inter-company reconciliation mapping; we extract all historical posted entries and carry account codes as the primary identifier.

Employee records include contact info, job title, department, and employment dates. We map to Employee or Person objects in the destination and preserve the reporting-line structure where supported.

Axelor stores file attachments against any record via its document management module. We export file metadata (filename, size, record association) but file binaries require separate storage handling; we flag this explicitly during scoping.

BOMs define product component lists and routing steps for manufacturing. Axelor's BOM versioning must be preserved; we map the active BOM to the destination product and carry alternate BOM references as custom properties.

Axelor user records carry email, role, and team membership. Role-to-permission mappings vary significantly between versions; we extract user identity and role names but recommend manual permission review post-migration.

Axelor Studio allows creation of entirely custom domain objects stored in the same database. Each custom object has its own XML model file. We enumerate all non-standard models at scoping time and handle each as a mapping case with customer-reviewed field-level transforms.