Migrate from Axelor ERP to Infor CloudSuite Corporate

Axelor Partner is a unified object covering customers, suppliers, and prospects with addresses, bank details, and contact persons in a one-to-many relationship. We split Axelor Partners into Infor CloudSuite Customer and Supplier records based on the Axelor partnerType field, with individual Contact persons mapped to Infor Contact records. Partner addresses migrate as address lines against the Customer or Supplier entity. Bank details map to Infor payment terms and bank account configuration fields. Multi-company Partner assignments resolve to the corresponding Infor entity.

Axelor Products cover stocked items and services with BOM support. We map stocked products to Infor Item Master with unit of measure, cost, and stock-control flags preserved. Service products map to Infor Service-type items. Axelor product variants, units of measure, and supplier info (sourcing rules) map to Infor Item Purchasing and Inventory configuration records. Multi-UoM conversions are preserved in Infor UoM conversion tables.

Axelor Sale Orders carry line items, taxes, discounts, and status workflows. Order-to-invoice linking is preserved via the originId reference. We map order status to Infor Sales Order status codes, preserving confirmed, partially fulfilled, and cancelled historical records separately so that only open orders require active Infor workflow processing. Line items resolve Product references against the Item Master migrated in the prior step.

Axelor Purchase Orders map directly to Infor Purchase Orders with supplier reference resolved via the Partner-to-Supplier mapping. Order line items, quantities, and pricing terms migrate. Open versus closed purchase order status determines whether the order enters an active Infor procurement workflow or is archived as a historical record.

Axelor invoices are multi-currency and multi-company aware. We separate open invoices from historical records; open invoices migrate with active payment term and overdue flag status, while historical invoices migrate as closed records for financial reporting continuity. Multi-currency amounts map to Infor's currency and exchange rate configuration. Invoice lines, tax computation, and payment terms are preserved in the mapping.

Axelor Projects contain Tasks, Milestones, Time Entries, and Invoicing Plans in a nested hierarchy. We extract the full project hierarchy including subtask nesting, assigned users, and billing rates. Project status and custom fields migrate to Infor Project Management. Infor Work Orders link to Projects for manufacturing-scope deployments. If Infor Project Management module is not included in the destination subscription, we map to Infor Work Order as the nearest equivalent.

Axelor Tasks belong to Projects and carry status, priority, assignees, and custom fields. Subtask inheritance varies by Axelor version; we flatten the hierarchy where Infor does not support nested tasks. Task assignees resolve via Owner email matching against Infor Users. Status and priority map to Infor Activity status and priority fields.

Axelor Stock Moves track internal transfers, receipts, and shipments with real-time inventory impact. We extract move lines, warehouse references, and lot or serial numbers. Open Stock Moves at migration time are flagged so the customer can complete or void them in the source system before cutover to avoid partial transaction migration. Closed moves migrate as historical inventory transaction records for audit continuity.

Axelor Chart of Accounts, Journals, and Journal Entries with debit and credit lines and analytic accounts map to Infor GL. Multi-company journal entries require inter-company relationship resolution; we split Axelor inter-company entries into separate standard journal entries per entity and flag the relationship via a custom reference field so the customer can manually reconcile counterpart entries post-migration. Axelor analytic accounts map to Infor cost centre or analysis dimension fields.

Axelor BOMs define product component lists and routing steps for manufacturing with version history. We map the active BOM to Infor Item BOM and carry alternate BOM references as version alternatives. Routing steps migrate to Infor Routing records linked to the BOM. BOM component quantities and scrap percentages map directly to Infor BOM line structure fields.

Axelor Employee records include contact info, job title, department, and employment dates. We map to Infor Employee or Person objects depending on the destination edition's schema. Reporting-line structure (manager relationships) migrates where supported. Employee bank details and compensation fields migrate only if the destination Infor edition includes HR modules; otherwise they are flagged for manual entry.

Axelor Studio allows creation of entirely custom domain objects stored in the same database with XML model files compiled at build time. We enumerate all non-standard Axelor domain models at scoping by inspecting the application's XML domain files or requesting a full schema dump. Each custom object gets mapped to an Infor Mongoose custom table with equivalent field types. Custom object relationships to standard Axelor objects (Partners, Products, Orders) resolve via lookup fields that we replicate as Infor relationship fields. Any custom object without a clear Infor equivalent is flagged for customer decision on whether to create a new custom table or restructure the data into standard objects.