Migrate from Axelor CRM to Nutshell

Axelor Leads map directly to Nutshell Leads with the original Lead status, source, and rating preserved. The Axelor lead-to-agency assignment (many-to-many) is resolved separately via junction export and reconstructed as Nutshell Tags on the Lead record. Any lead score or qualification fields migrate as custom fields on the Nutshell Lead.

Axelor Third Parties with type Customer or Prospect map to Nutshell Companies. The Third Party name becomes the Company name, the primary address migrates as the Company address, and the type classification (customer vs prospect) maps to a custom Company field or a Nutshell Tag. Third Party notes and agency associations migrate as Company notes and Tags respectively.

Axelor Contacts are distinct child records linked to a parent Third Party. We resolve the parent Third Party to its Nutshell Company counterpart, then import the Contact as a Nutshell Person linked to that Company. The Contact email, phone, title, and role fields map directly. If a Contact has no parent Third Party in the source, we create a standalone Person record without a Company link and flag it for reconciliation.

Axelor Opportunities map to Nutshell Deals. The Opportunity stage maps to the Nutshell Deal status (Lost, Won, or the active pipeline stage name), the expected amount maps to Deal value, and the close date maps to the expected close date. We configure the Nutshell pipeline stages before migration so that stage names align with the Axelor stage sequence.

The lead-to-agency assignment in Axelor is a many-to-many junction relationship. We extract a junction table mapping each Lead ID to its associated Agency IDs, then create Tags in Nutshell using the Agency names (e.g., Tag: 'Agency - Northeast'). We apply these Tags to the corresponding migrated Leads and Third Parties. If the destination team prefers a custom Agency field instead of Tags, we configure that field during the schema design step.

The recurrent revenue amount and default recurring period on Axelor Opportunities are only present when the 'Manage recurrent revenue on opportunities' checkbox is activated in the CRM settings. We detect this configuration during scoping by inspecting the Opportunity XML schema. If present, we create custom fields in Nutshell (e.g., Recurring Amount, Recurring Period) and map the values across. If the setting is inactive, these fields are omitted from the migration scope.

Axelor Studio custom objects are defined in XML and compiled to JPA models at deployment. There is no standard export format for these objects. During scoping, we perform a schema inspection step that reads the XML model definitions, infers the field structure and data types, and generates a field map before extraction. Custom objects migrate to Nutshell as either standard objects with custom fields or as Nutshell custom objects, depending on complexity and lookup relationships.

Axelor User records include roles, organizational structure, and access permissions. We extract user identity data (name, email, organizational unit) for mapping record ownership in Nutshell. We match Axelor Owner references on Leads, Third Parties, and Opportunities to Nutshell Users by email. Owners without a matching Nutshell User are held in a reconciliation queue for the customer's admin to provision before record import resumes.

Axelor DMS stores documents linked to CRM records. We extract document metadata (filename, linked record, upload date) and include it in the migration scope. Binary file transfers require separate file-transfer handling outside the data migration. We provide guidance on DMS file relocation and document the Nutshell Files structure so that the customer's admin can re-link files post-migration if needed.