Migrate from Axelor CRM to HubSpot

Axelor third parties flagged as persons map to HubSpot contacts. The Axelor name field splits into HubSpot firstname and lastname — if Axelor stores a single full-name field, FlitStack parses by space and flags unmappable cases for review before migration commits.

Axelor third parties flagged as companies — or those with no person-type flag but with a company name — map directly to HubSpot companies. The primary address on the Axelor third party becomes the HubSpot company address. Corporate parent links map to HubSpot's parent company field when present.

When an Axelor third party has no type indicator, FlitStack applies a heuristic: records with an email address and no company name route to HubSpot contacts; records with a company name and no personal email route to HubSpot companies. Your team confirms the split rule before the test migration runs.

Axelor lead status values (New, Qualified, In Progress, Lost, Won) map to HubSpot lifecycle stage and sales-ready status. We preserve the original Axelor status value in a custom property and apply a default HubSpot lifecycle stage mapping — typically 'Lead' for New and In Progress, 'Customer' for Won, and a null or archived state for Lost.

Axelor opportunities map 1:1 to HubSpot deals. The opportunity name becomes the deal name, the expected revenue amount maps to deal amount, the close date maps to close date, and the assigned user maps by email match to a HubSpot owner. Pipeline stage values map value-by-value to HubSpot deal pipeline stages.

Axelor pipeline configurations — each with named stages — create corresponding HubSpot deal pipelines and stages. Stage names map value-by-value; stage probability is applied from HubSpot's defaults unless your team provides custom probability mappings per stage. Multiple Axelor pipelines create multiple HubSpot pipelines or a single pipeline with multiple stage sets.

Axelor's 'Manage recurrent revenue on opportunities' setting stores expected recurring amount and period on the opportunity. HubSpot has no native recurring revenue field on deals — we create a custom number field (Recurring_Amount__c) and a custom text field (Recurring_Period_Months__c) to preserve this data.

Axelor activities with type Call map to HubSpot calls, type Meeting to HubSpot meetings, and type Task to HubSpot tasks. Subject, description, due date, completed date, and assigned user (resolved by email) all transfer. Original creation timestamps are preserved as custom datetime fields since HubSpot's CreatedDate reflects the import date.

Axelor notes attach to third parties and opportunities with text content and timestamps. They map directly to HubSpot notes, preserving the body text and associating to the correct contact, company, or deal record. Rich-text formatting in Axelor notes is simplified to plain text during migration.

Axelor file attachments on third parties and opportunities are downloaded and re-uploaded to HubSpot Files. File name and description are preserved. Files attach to the corresponding HubSpot record by association. HubSpot's 25MB per-file limit applies — files over this threshold are flagged for manual handling.

Axelor user records match to HubSpot users by email address. Unmatched users are flagged before migration — your team either creates HubSpot accounts for them first or assigns their records to a fallback owner. The Axelor user ID is stored as a custom field on the HubSpot user record for traceability.

Axelor catalogue items — PDFs and product descriptions stored for sales reference — map to HubSpot products when Sales Hub Enterprise is active. Without Sales Hub, catalogue data migrates as notes on the associated opportunity. We surface this gap in the pre-migration assessment.

Axelor custom objects defined in XML model files map to HubSpot custom objects when the destination portal has Enterprise-tier access. Custom object associations that use Axelor's N:N model need HubSpot junction objects — we identify these in the migration plan and generate the schema before data loads.

Axelor agency management links associate third parties with agency records. We map these to HubSpot companies when agencies are stored as company-type third parties, or to HubSpot Teams when the agency concept represents an internal sales team structure. Your team chooses the mapping in the pre-migration plan.