Migrate from Axelor CRM to monday CRM

Axelor Leads are first-class CRM objects tracked through a pipeline with close and convert actions. We map them to Monday.com as Contact-type items on the CRM board with a Lead status column. The conversion history from Axelor (when a Lead was converted to a Third Party) is preserved as a custom date field. If the customer used Axelor's Lead status workflow, we replicate it as Monday Status column values.

Axelor Third Parties represent the core Contact and Company entity with type-based classification (customer vs prospect). We map Third Parties with type=customer to Monday.com Account items. Third Parties with type=prospect map to Contact items with a Prospect tag. The agency association field on Third Parties becomes a Tag on the Monday item. Third Party notes migrate to the Monday item's description column.

Contacts in Axelor are distinct child records linked to a parent Third Party. We maintain the parent-child relationship by creating the parent Account in Monday first, then creating Contact items linked via an Account column. Email, phone, and address fields map directly to corresponding Monday text and location columns. If no parent Third Party exists, the Contact is created as a standalone Contact item.

Axelor Opportunities track potential sales with stages, expected amounts, and optional recurrent revenue fields. We map them to Monday.com as items on a Deals board with Status columns representing the Opportunity stage. Expected amount maps to a Numbers column, and close date maps to a Date column. The lead-to-agency routing on the parent Lead is carried forward as Tags on the Opportunity item.

Axelor's lead-to-agency assignment is a many-to-many relationship stored in a junction table. We resolve this by exporting the Lead-to-Agency junction, then applying the agency names as Tags on the corresponding Lead or Contact items in Monday. If agency names conflict with existing tags, we prefix them with 'Agency-' to distinguish them from other tag categories.

Agencies are a distinct routing and segmentation concept in Axelor CRM with no native equivalent in Monday.com. We create a dedicated tag group called 'Agencies' in Monday's tag management and populate it with the agency names from Axelor. This keeps agency routing visible without requiring a separate board or custom object.

The recurrent revenue amount and recurring period fields on Opportunities are present only when the 'Manage recurrent revenue on opportunities' checkbox is activated in Axelor CRM settings. We detect their presence during scoping by inspecting the Opportunity XML schema for the recurring revenue fields, and include them in migration scope only when present. They map to custom Numbers and Date columns on the corresponding Opportunity item in Monday.

Axelor Studio custom objects are defined in XML and compiled to JPA models. We inspect the XML schema during scoping, infer field names and data types, and create a corresponding Monday board with columns typed to match (text, number, date, person, file, etc.). Lookup relationships between custom objects are recreated as Connect boards columns or as text-based reference fields.

Axelor user records include identity data used to map record ownership. We extract owner references from Third Parties, Contacts, and Opportunities and match by email against Monday.com workspace members. Any owner without a matching Monday user is flagged in the reconciliation report for the customer to provision before migration resumes. Role and permission schemas are not migrated.

Axelor supports PDF catalogue storage linked to Third Parties for sales staff reference. We extract catalogue metadata (filename, link, description) from the Axelor export and map it to File or Link columns on the corresponding Account item in Monday. Binary file transfer is handled separately from the data migration scope.