Migrate from Axelor CRM to Freshsales

Axelor Leads map directly to Freshsales Leads with the original lead source, status, and assigned owner preserved. The Axelor Lead record is the entry point in both systems' pipeline models. Lead creation dates and last modified timestamps transfer to Freshsales' created_at and updated_at fields. If the customer used the 'Manage recurrent revenue on opportunities' setting, that configuration is evaluated at the Opportunity level rather than Lead.

Axelor Third Parties with type 'person' map to Freshsales Contact. We resolve the parent-child Contact-to-Third-Party relationship during migration by matching the Contact's email address or full name against the Third Party record, then create the Contact with the parent Third Party's organization data as the Contact's Account field in Freshsales.

Axelor Third Parties with type 'company' or 'organization' map to Freshsales Account. Company name, website, address fields, and industry classification migrate directly. The Account record is created before any Contact import so that the Contact-Account lookup relationship is satisfied at the moment of Contact insert.

Axelor Contacts are distinct from Third Parties and link to a parent Third Party. We preserve the parent-child relationship by resolving the parent Third Party to its Freshsales Account equivalent at migration time, then writing the Contact record with the AccountId populated. If the parent Third Party is a person-type record, we create the Account first from the parent organization name before inserting the Contact.

Axelor Opportunities map to Freshsales Deals. The Opportunity name, amount, stage, expected close date, and probability migrate directly. Axelor's stage sequence maps to Freshsales Deal stages, and we configure the Freshsales pipeline stages during schema setup before migration. If the 'Manage recurrent revenue on opportunities' setting is active, we detect the recurring amount and period fields during scoping and create matching custom fields on the Deal object.

Axelor's Lead-to-Agency routing is a many-to-many relationship between Leads and Agencies. Freshsales has no native Agency object, so we create a Tag for each unique Agency record, then apply those Tags to the corresponding Lead records in Freshsales. The junction export (Lead ID to Agency ID mapping) is generated during the Axelor data extract and applied as Tag assignments during migration. Agencies that represent a team or territory map conceptually to Freshsales' Sales Team or Territory fields if the customer licenses the Enterprise tier.

Axelor Agency records represent routing units or partner organizations. We export all Agencies as Tags with a naming prefix (e.g., 'Agency: [name]') so they are visually distinguishable from other tags in Freshsales. If the customer used Agencies to segment their partner or reseller network, the Tag preserves that segmentation for reporting and assignment rules in Freshsales.

Axelor PDF catalogues are linked metadata records attached to Third Parties. We extract catalogue metadata (title, description, file reference) and create Freshsales Note records on the corresponding Account or Contact. The actual binary PDF files require separate file-transfer handling outside the API migration scope; we provide guidance on the file storage location and a recommended file transfer method for the customer's IT team.

Axelor Studio creates entirely new objects defined in XML and compiled to JPA models. We inspect the XML model definitions during the scoping phase to infer field names, data types, and relationships. The destination Freshsales custom object is pre-created before migration with matching field names and types. Custom object relationships (lookups to standard objects) are configured as Freshsales lookup fields. If the custom object references other custom objects, we resolve the creation order to satisfy foreign key constraints during import.

The recurring revenue fields on Axelor Opportunities (expected recurring amount and default recurring period) are only present when the 'Manage recurrent revenue on opportunities' checkbox is activated in Axelor CRM settings. We detect this configuration during scoping by inspecting the Opportunity XML schema for the recurring revenue fields. If present, we create matching custom fields in Freshsales Deals (recurring_amount__c, recurring_period__c) before migration and transfer the values.

Axelor BPM workflows store automation logic as application configuration in the Studio and J2EE deployment layer. The AppLoader can package DMN models as XML for deployment, but this is application deployment, not data migration. We do not migrate BPM workflows. We inspect the Axelor application configuration during scoping, document every identified workflow trigger, condition, and action as a written specification, and deliver that document to the customer for rebuild in Freshsales' workflow automation builder.

Axelor DMS stores documents linked to CRM records (Leads, Third Parties, Opportunities). Binary attachments export separately from data records. We extract document metadata (filename, DMS reference, linked record type and ID) and include it in the migration scope as Freshsales Attachment records linked to the migrated record via the Freshsales API. The actual binary files require separate file-transfer handling outside the standard migration scope.