Axelor CRM to HubSpot
Axelor CRM is a module of the Axelor open-source platform (ERP/BPM). Its data is exposed through a generic model-based REST API.
Axelor CRM data can move into HubSpot, landing mainly in Sales Hub. 0 of 7 mapped objects move directly; 3 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Axelor CRM
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<20k records
Standard CRM models only.
Mid migration
20k-250k records
Custom fields and activities included.
Large migration
>250k records
Multi-module ERP data, heavy customisation and rebuilt automation.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Axelor CRM: what you need to get in, what lands in HubSpot, and what will not.
REST (generic per-model endpoints, JSON)
An Axelor user login (username and password) on the instance URL. Newer versions may require the /callback login path and an X-CSRF-Token header.
Not verified. An admin or a user with read access to the CRM models is likely needed.
Choose your route
How will you move the data?
No native connector was found.
- You need: An Axelor user login (username and password) on the instance URL. Newer versions may require the /callback login path and an X-CSRF-Token header.
- Permission: Not verified. An admin or a user with read access to the CRM models is likely needed.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- REST API per model, e.g. GET /ws/rest/:model/:id and POST /ws/rest/:model/search with field lists and limits
- In-app grid CSV export (category-level knowledge, not verified in the sources)
- Direct database extract for self-hosted instances (category-level knowledge)
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Axelor CRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Partner (contacts and companies, distinguished by an isContact flag, which is an assumption) | Contacts / Companies | partial | The API model com.axelor.apps.base.db.Partner is confirmed. The contact/company split needs mapping rules. |
| Opportunity | Deals | partial | The model is assumed to be in the CRM module and was not confirmed. Pipeline stages must be recreated in HubSpot. |
| Leads | Contacts | partial | Not confirmed in the sources. Map to Contacts with lead status. |
| Events, calls, tasks and meetings | Calls / Meetings / Tasks / Notes | partial | Activities need their own import files with associations to the related records. |
| Helpdesk tickets | Tickets | partial | The Ticket model com.axelor.apps.helpdesk.db.Ticket is exposed via REST. |
| Users | Owners (HubSpot users) | manual | Create users in HubSpot first, then map owners by email. |
| Products | Products | partial | The Product model is reachable via REST. HubSpot imports products in a single-object import only. |
What to expect
They are configuration, not data. No import path into HubSpot workflows.
HubSpot permission sets must be rebuilt.
They must be rebuilt in HubSpot reporting.
Custom Axelor Studio fields and statuses need HubSpot properties first.
The HubSpot import links records through a shared column or record IDs.
The API search must be run per model with pagination. Related-record coverage was not verified.
Export activities with the source record's Axelor ID and import with associations.
Test authentication on the target version first.
Inventory the models and custom fields via the metadata before scoping.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
The REST API pattern and login flow are supported only by Axelor docs and forum posts, and the HubSpot import path is documented. The Axelor CRM object and field model, export UI, rate limits and certifications were not verified. Those sections rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Axelor CRM to HubSpot?
1. Confirm the Axelor version and the base URL, including the webapp path. 2. Create an API user with read access to the Partner, Opportunity, Lead, Event and Ticket models. 3. Inventory custom Studio fields and statuses, then create matching HubSpot properties. 4. Create a custom property for the Axelor ID to keep a legacy key.
What does not move from Axelor CRM to HubSpot?
Automations, Studio workflows and BPM processes, Permissions and roles and Reports and dashboards. Plan to rebuild or retire these.
How long does a Axelor CRM to HubSpot migration take?
Small (<20k records): 2-4 weeks. Mid (20k-250k records): 4-8 weeks. Large (>250k records): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Axelor CRM?
An Axelor user login (username and password) on the instance URL. Newer versions may require the /callback login path and an X-CSRF-Token header. Not verified. An admin or a user with read access to the CRM models is likely needed.
Is there a native HubSpot connector for Axelor CRM?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Axelor CRM data?
Check: The platform is cross-industry. Check for financial data when it is used alongside ERP/accounting. and Check for health or minors' data depending on the customer.. Agree consent, retention and access rules before exporting.
Moving Axelor CRM into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner