Migrate from Axelor CRM to Zoho CRM

Axelor Leads map directly to Zoho CRM Leads. We preserve lead source, lead status, the conversion history flag (whether the Lead was converted to a Third Party in Axelor), and any lead-score custom fields. Axelor stores agency assignments on Leads as a many-to-many relationship that we reconstruct using a junction lookup module in Zoho.

Axelor Third Parties are the core contact-company entity and map to Zoho CRM Accounts. Third Party type (customer versus prospect) maps to the Account Type picklist. The agency association stored on Third Parties is reconstructed in Zoho via Tags (applied to the Account) and a custom linking module if the customer requires a formal agency-account relationship with attributes.

Axelor Contacts are distinct child records linked to a parent Third Party. We resolve the parent Third Party to a Zoho Account during import and set the Contact.AccountId lookup. Email, phone, job title, and address fields map directly. Any Contact-specific agency assignments are resolved against the Agency linking module.

Axelor Opportunities map to Zoho CRM Deals. The pipeline stage sequence from Axelor is preserved and mapped to Zoho Stage names, with probability percentages migrated to the Zoho Stage configuration. Expected close date and amount fields migrate directly. If the 'Manage recurrent revenue on opportunities' setting is active in the source Axelor instance, we detect the recurring revenue fields during schema inspection and create corresponding custom fields on the Zoho Deal module.

Agencies are a distinct routing and segmentation concept in Axelor CRM with no native equivalent in Zoho CRM. We map each Axelor Agency to a Zoho Tag on the associated Lead and Account records, preserving the agency name and routing classification. If the customer requires a formal Agency object with attributes (agency type, region, assigned territory), we create a custom Agency module in Zoho and a junction table to reconstruct the many-to-many Lead-Agency relationship.

The Axelor Lead-to-Agency assignment is a many-to-many junction. We export this as a separate junction file during scoping, resolve each Agency reference to a Zoho Tag or Agency custom module record, and apply the tags to the migrated Lead in Zoho. This preserves the lead routing and segmentation logic that was managed through agency assignments in Axelor.

Axelor Studio custom objects are defined in XML and compiled to JPA models. During scoping we inspect the XML schema definitions to infer field structure, data types, and lookup relationships. We pre-create the corresponding custom modules in Zoho via Setup > Modules and Fields, including all custom fields and lookup fields, before any data import. Field names are normalized from Java camelCase to Zoho's field naming conventions. Studio objects with no data are included in the schema scope for post-migration configuration.

Axelor user records include roles, organizational structure, and access permissions. We extract user identity data (name, email, role) for mapping record ownership in Zoho. We match by email against the Zoho destination User table. Any Axelor Owner without a matching Zoho User is held in a reconciliation queue; the customer's Zoho admin provisions the User before record import resumes. Role and permission schemas are not migrated as they are platform-specific.

Axelor DMS stores documents linked to CRM records. We export document metadata (filename, document type, linked record type, linked record ID, upload timestamp) separately from the data record export. Binary files are handled via a file transfer protocol with guidance provided to the customer on folder mapping and linking to Zoho record IDs after import. Actual file transfer is scoped as a separate task from the data migration.

The recurring revenue amount and default recurring period fields on Axelor Opportunities appear only when the 'Manage recurrent revenue on opportunities' CRM setting is active. We detect their presence during schema inspection by reading the Opportunity XML model for the recurring revenue fields. When present, we create corresponding custom fields in Zoho Deals (Recurring_Amount__c, Recurring_Period__c) before the Opportunity import phase.