Migrate from Axelor CRM to Pipedrive

Axelor Lead records map 1:1 to Pipedrive Lead. We preserve Lead status, source, assigned agency, and any conversion date. Axelor Lead conversion creates a Third Party; we capture this conversion timestamp and carry it as a custom field on the Pipedrive Lead before conversion. If the Axelor Lead was converted pre-migration, we create both the Pipedrive Lead (with converted_at timestamp) and the corresponding Organization and Person in the same migration pass.

Axelor Third Party records (representing companies and organizational entities) map directly to Pipedrive Organization. We map the Third Party type (customer vs prospect) to a custom Organization field or to the Pipedrive Organization's address and industry fields where applicable. The Third Party name becomes the Organization name; the website field maps from Axelor's webSite field. Third Parties are the parent of Axelor Contacts, so we create all Organizations before importing Persons to satisfy the Organization-Person link.

Axelor Contact records map 1:1 to Pipedrive Person. Each Contact has a parent Third Party; we resolve the parent Organization ID during import and link the Person to it. Name, email, phone, job title, and address fields map directly. Any Contact-level custom fields migrate as Person custom fields. Notes attached to the Contact migrate as Pipedrive Activity notes linked to the Person.

Axelor Opportunity maps to Pipedrive Deal. The Opportunity stage maps to a Pipedrive Pipeline stage. Expected revenue and close date migrate directly. Owner assignment resolves via email match to Pipedrive User. If the Axelor Opportunity has a linked Third Party (the primary company associated with the deal), we link the Pipedrive Deal to the Organization created from that Third Party. Stage probabilities from Axelor are applied to the corresponding Pipedrive Pipeline stage weights.

Each Axelor Opportunity stage becomes a Pipedrive Pipeline stage. We configure the Pipedrive Pipeline in the destination account before migration, matching the stage sequence and probability percentages from Axelor. Open Won and Open Lost stages from Axelor map to the equivalent Pipedrive stage status. If Axelor uses multiple sales processes with different stage sequences, we create multiple Pipedrive Pipelines with corresponding stage sets.

Axelor Agency records represent a routing and segmentation concept with no native Pipedrive equivalent. We create a Tag for each unique Axelor Agency name and apply it to the associated Leads and Third Parties (Organizations) during migration. The customer chooses whether Agencies map to a single tag field or to a dedicated custom field during scoping. Agency metadata (contact info, description) is preserved in a custom Organization or Person field if the customer requires it.

Axelor allows a Lead to be assigned to multiple Agencies simultaneously via a junction table. We export this junction during scoping, producing a Lead-ID-to-Agency-ID mapping table. During migration, we apply the corresponding Tags to each Lead record in Pipedrive. If the customer also wants Agency assignment visible on the Organization, we apply the same Tags to the Organization after resolving the Lead-to-Organization relationship from the conversion.

The recurrent revenue amount and default recurring period on Axelor Opportunities appear only when the 'Manage recurrent revenue on opportunities' setting is activated in CRM settings. We detect the presence of these fields during XML schema inspection in the scoping phase. When present, we create corresponding custom fields on Pipedrive Deals (recurring_amount and recurring_period) and migrate values. If the setting is inactive, we skip these fields entirely and document their absence.

Axelor Studio custom objects are defined in XML and compiled to JPA models. We perform a schema inspection step during scoping that reads the XML model definitions, infers field names and data types, and generates a mapping plan before extraction. Custom objects that reference a standard object (Lead, Third Party, Opportunity) become custom fields on that object in Pipedrive. Standalone custom objects map to Pipedrive custom object records via Pipedrive's Data Customization feature if the plan supports it. Multi-level custom object hierarchies require a pre-migration schema design review with the customer.

Axelor user records include identity data (name, email, role) needed for mapping record ownership. We extract users by email and match against Pipedrive Users in the destination account. Any Axelor user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before the Owner mapping phase runs. Role and permission schemas do not migrate because Pipedrive's role model is separate and must be reconfigured by the admin.

Axelor notes attached to Third Parties, Contacts, or Opportunities migrate as Pipedrive Note Activities linked to the corresponding Person, Organization, or Deal. We preserve the note body, author (resolved by email to Pipedrive User), and creation timestamp. Notes are imported after the parent records exist to satisfy the lookup relationship.

Axelor DMS stores binary documents linked to CRM records. We extract document metadata (filename, DMS path, linked record) during the export phase. The actual binary files require separate file-transfer handling outside the data migration scope. We provide a documented file manifest and guidance on DMS-to-Pipedrive file attachment migration (either direct upload or external reference links in a custom field). The binary file migration is a separate workstream unless explicitly included in the engagement scope.