Dolibarr CRM to HubSpot
Open-source ERP/CRM that covers third parties, contacts, proposals, orders, invoices, projects, tasks and tickets, and can be self-hosted.
Dolibarr CRM data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (Third parties (customers/prospects), Contacts (llx_socpeople) and Products and services); 4 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 Dolibarr CRM
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 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
<10k records
CSV export of the core objects.
Mid migration
10k-100k records
API extraction of activities and associations.
Large migration
>100k records
SQL extraction, custom deal model, heavy rebuild.
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 Dolibarr CRM: what you need to get in, what lands in HubSpot, and what will not.
REST (JSON, Restler framework)
A user API key with permissions on the relevant modules, plus the instance URL (/api/index.php).
Admin is needed to enable the Export/Import modules and the API module. The API applies the same permissions as the UI.
Choose your route
How will you move the data?
No native connector was found.
- You need: A user API key with permissions on the relevant modules, plus the instance URL (/api/index.php).
- Permission: Admin is needed to enable the Export/Import modules and the API module. The API applies the same permissions as the UI.
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.
- Export module (Tools > New Export): predefined datasets, selectable fields and filters, saved profiles, CSV/TSV/XLSX output
- REST API endpoints: thirdparties, contacts, projects, tasks, tickets, proposals, orders, invoices, users
- Direct SQL on the database (llx_ tables) for gaps such as project-contact links
- Marketplace export modules (e.g. Export/Import List V2)
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 Dolibarr CRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Third parties (customers/prospects) | Companies | yes | Export via the Export module or API. Third parties can also be individuals or suppliers, so filter by type. |
| Contacts (llx_socpeople) | Contacts | yes | Keep the third-party ID as a key to associate contacts with companies. |
| Opportunities/leads (projects with opportunity status) and proposals | Deals | partial | Dolibarr has no dedicated deal object. Opportunities sit on projects and proposals, so a mapping decision is needed. Pipeline stages are a fixed opportunity status list. |
| Agenda events (calls, meetings, emails) | Calls, Meetings, Emails, Notes | partial | Coverage in the Export module and API is not confirmed. Audit it and fall back to SQL if needed. |
| Project tasks | Tasks | partial | Tasks have an API endpoint. Association to HubSpot records needs rebuilding. |
| Tickets | Tickets | partial | The ticket API class exists. Field and status mapping is manual. |
| Products and services | Products | yes | Available through the API and exports. |
| Users | Owners (Users) | manual | Owners are not imported. Create HubSpot users and map them to a source user ID or email. |
What to expect
Not exported as portable definitions. They must be rebuilt in HubSpot.
Rights models differ. Rebuild them with HubSpot teams, roles and permission sets.
Rebuild them in HubSpot reporting.
Dolibarr has no native deal object.
The built-in project export is limited, and some links need SQL.
Extrafields are instance-specific.
Stages and users must be recreated in HubSpot first.
Audit coverage per dataset early and use the API or SQL for gaps.
Use a stable key such as email or external ref and dedupe before import.
Test the volume of calls and use batch exports where possible.
Check the CSV settings and encoding before handoff.
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.
Export module and REST API are backed by Dolibarr wiki and secondary guides. HubSpot-side mapping, rate limits, activity export coverage and governance are not sourced, so they rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Dolibarr CRM to HubSpot?
1. Confirm the Dolibarr version and enable the Export module (admin). 2. Enable the API module and create a read-only API user with the DOLAPIKEY. 3. Inventory the modules in use: third parties, contacts, projects/opportunities, proposals, agenda, tickets. 4. List extrafields and custom statuses to become HubSpot properties.
What data can move from Dolibarr CRM to HubSpot?
These objects move directly: Third parties (customers/prospects), Contacts (llx_socpeople) and Products and services. Check the mapping table for partial and manual items.
What does not move from Dolibarr CRM to HubSpot?
Automation, workflows and triggers, User permissions and groups and Reports and dashboards. Plan to rebuild or retire these.
How long does a Dolibarr CRM to HubSpot migration take?
Small (<10k records): 2-4 weeks. Mid (10k-100k records): 4-8 weeks. Large (>100k records): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Dolibarr CRM?
A user API key with permissions on the relevant modules, plus the instance URL (/api/index.php). Admin is needed to enable the Export/Import modules and the API module. The API applies the same permissions as the UI.
What compliance issues apply when moving Dolibarr CRM data?
Check: Financial (invoices and payments are held in the ERP) and Possible health or minors data depending on the user, so check for it. Agree consent, retention and access rules before exporting.
Moving Dolibarr 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