ERPNext CRM to HubSpot
CRM module inside the open-source ERPNext suite, with Lead, Opportunity, Quotation and Customer flow, plus Prospect and CRM Note records.
ERPNext CRM data can move into HubSpot, landing mainly in Sales Hub. 2 of 8 mapped objects move directly (Lead and Opportunity); 4 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for ERPNext 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
<10k records
CSV export of Leads, Opportunities and Customers.
Mid migration
10k-100k records
API extraction of activities plus automation rebuild.
Large migration
>100k records
Custom DocTypes, multi-company setups and ERP coexistence.
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 ERPNext CRM: what you need to get in, what lands in HubSpot, and what will not.
REST API (Frappe Framework, DocType-based)
API key/secret for a user with read permission on the CRM DocTypes, or Desk login for Data Export.
System Manager or equivalent role to export all DocTypes.
Choose your route
How will you move the data?
No native connector was found.
- You need: API key/secret for a user with read permission on the CRM DocTypes, or Desk login for Data Export.
- Permission: System Manager or equivalent role to export all DocTypes.
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.
- Data Export DocType to CSV or Excel with field selection and filters
- REST API list/get on DocTypes
- Self-hosted database backup
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 ERPNext CRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Lead | Contacts | yes | Lead is the first-stage record. Decide whether each lead becomes a Contact or a Company, and map status to lifecycle stage. |
| Customer / Prospect / Contact | Companies | partial | Prospect and Customer map to Companies. Contact links are DocType links, so export them separately and rebuild associations in HubSpot. |
| Opportunity | Deals | yes | Opportunity stage maps to a HubSpot pipeline stage. Deal-to-contact and deal-to-company associations need a shared key column. |
| Quotation / Sales Order items | Quotes | manual | Quotations belong to the ERPNext selling module. Export them as reference data or as Line items on deals. |
| ToDo / Event | Tasks | partial | Exportable as DocTypes through Data Export or the API. Links to parent records are by reference, so rebuild them. |
| Comment / CRM Note | Notes | partial | The generic import cannot carry activity and reference history without custom work. |
| Communication (email) | Emails | manual | Email history needs API extraction and the HubSpot engagements API. |
| Lead Owner / Sales Person | Contacts | partial | Map users to HubSpot owners by email. The Sales Person tree has no HubSpot equivalent. |
What to expect
No direct HubSpot equivalent; the structure continues into downstream ERPNext documents.
Configuration, not data; rebuild as HubSpot workflows and SLAs.
Next CRM docs list assignment rules and SLAs as ERPNext features.
The Desk report builder and sales funnel pages are not exportable.
ERPNext role permissions do not carry over.
ERPNext uses status and stage masters per DocType.
Pull Communication, Comment and ToDo through the REST API and import them as engagements.
Keep the ERPNext name as a custom property and use it as the unique key.
Audit Customize Form and custom fields before mapping.
Take the export snapshot on a frozen version.
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 routes (Data Export, REST API) and HubSpot import are documented. Rate limits, auth details, residency and certifications were not verified, and the activity and association mapping rests on category-level knowledge of Frappe DocTypes.
Sources
Related migrations
Frequently asked questions
How do I migrate ERPNext CRM to HubSpot?
1. Inventory Lead, Opportunity, Prospect, Customer, Contact, Address, ToDo, Comment, Communication and custom DocTypes. 2. Generate an API key and secret for a read-only integration user. 3. List custom fields via Customize Form and map them to HubSpot properties. 4. Decide how Lead, Customer and Prospect map to Contacts and Companies.
What data can move from ERPNext CRM to HubSpot?
These objects move directly: Lead and Opportunity. Check the mapping table for partial and manual items.
What does not move from ERPNext CRM to HubSpot?
Sales Person tree and Sales Team commission logic and Assignment rules, SLAs and server scripts. Plan to rebuild or retire these.
How long does a ERPNext 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 ERPNext CRM?
API key/secret for a user with read permission on the CRM DocTypes, or Desk login for Data Export. System Manager or equivalent role to export all DocTypes.
Is there a native HubSpot connector for ERPNext CRM?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving ERPNext CRM data?
Check: Possible financial data in Quotations or invoices if the ERP stays connected and Health or minors data depends on the customer's industry. Agree consent, retention and access rules before exporting.
Moving ERPNext 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